You have a hybrid deployment that contains a Microsoft Exchange Online tenant and an on-premises Exchange Server 2019 server named Server1. All users use an email address suffix of @contoso.com.
You migrate 200 mailboxes from Server1 to Exchange Online by using Exchange PowerShell cmdlets. Users hosted on Server1 can send email messages to the migrated mailboxes.
In Microsoft 365, you create a new mailbox that uses an email address of user1@contoso.com.
When email is sent from the mailboxes hosted on Server1 to user1@contoso.com, the senders receive a non-delivery report (NDR) that contains the following text:
"550 5.1.10 RESOLVER.ADR.RecipientNotFound;
Recipient not found by SMTP address lookup."
You verify that Microsoft 365 mailboxes can send email to user1@contoso.com successfully.
You delete the user account and mailbox of User1.
You need to ensure that when new mailboxes are created, all the users at your company can exchange email successfully
Which two actions should you perform? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
A . From Azure AD Connect, modify the synchronization settings
B. From Server1, run the New-RemoteMailbox cmdlet
C. From Server1, run the Enable-Mailbox cmdlet
D. From the on-premises network, create new mailboxes, and then migrate the mailboxes
to Microsoft 365
E. From the Exchange admin center, modify the properties of the Outbound connector
Answer: B,D
Explanation:
The problem happens because the on-premise Exchange server is not aware of the existence of the mailbox created in Exchange Online. To prevent this happening, new mailboxes need to be created from the on-premise Exchange server.
You can create on Exchange Online mailbox from the on-premise server by running New-RemoteMailbox cmdlet. Alternatively, you can create a local mailbox on the on-premise server and then migrate the mailbox to Exchange Online.
Latest MS-203 Dumps Valid Version with 203 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund