Question 30
A proposed fix must be validated: After verifying a new domain, an acquired division wants new employees to sign in using @contoso.com rather than the onmicrosoft.com tenant domain. How should the team validate that its change solved the stated problem?
Explanation
Correct Answer
The user signs in with the new UPN and retains the intended account object and mailbox access. The case concerns change a user's default sign-in suffix: After verifying a new domain, an acquired division wants new employees to sign in using @contoso.com rather than the onmicrosoft.com tenant domain. The UPN sign-in identifier is configured on the user object and is not automatically switched by DNS verification. This answers the acceptance evidence for this change because it addresses the explicit constraint. The action being validated is: set the relevant user's primary UPN to the approved custom suffix and communicate the changed identifier. The check must use the affected users, data, or devices.
Incorrect Answers
DKIM binds a message signature to a signing domain, complementing SPF and DMARC. The reason this does not settle the present case is the actual condition: A verified custom domain can be selected as the UPN suffix for suitable cloud identities.
Microsoft 365 verifies a custom domain through a requested DNS record before it can be used by tenant users. The records needed for this specific case concern: Compare the user's current UPN, approved verified domain list, and sign-in requirements.
DNS authority is determined by delegation, not by which portal displays a convenient record editor. The current corrective requirement is: Set the relevant user's primary UPN to the approved custom suffix and communicate the changed identifier.