Your network contains an Active Directory forest named contoso.local. You have a Microsoft 365 subscription. You plan to implement a directory synchronization solution that will use password hash…

Question

Options

• AFrom the Microsoft 365 admin center, verify the contoso.local domain name.
• BFrom the public DNS zone of contoso.com, add a new mail exchanger (MX) record.
• CFrom Active Directory Domains and Trusts, add contoso.com as a UPN suffix.
• DFrom Active Directory Users and Computers, modify the UPN suffix for all users.

• A
  7% (2)
• B
  4% (1)
• C
  85% (23)
• D
  4% (1)

Explanation

The on-premises Active Directory forest uses a non-routable suffix (contoso.local), which cannot be used as a UPN in Azure AD/Microsoft 365. For directory synchronization to work, users need UPN suffixes that match a verified domain in Microsoft 365 (contoso.com). The correct order is: first add contoso.com as an alternative UPN suffix in Active Directory Domains and Trusts (C), then update individual user UPN suffixes in Active Directory Users and Computers (D). Since the question asks what to do first, C must precede D. You cannot update user UPN suffixes to contoso.com until that suffix exists in Active Directory.

No community discussion yet for this question.