Exam MS-203 All Questions

View all questions & answers for the MS-203 exam

Exam MS-203 topic 2 question 21 discussion

Actual exam question from Microsoft's MS-203

Question #: 21
Topic #: 2

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.
On Server1, you create a new mailbox that uses an email address of [email protected].
Users hosted in Exchange Online report that they receive a non-delivery report (NDR) when they attempt to send email messages to [email protected]. The
NDR contains the following text: `User1 wasn't found at contoso.com.`
You verify that the Exchange Online users can send email successfully to the other mailboxes hosted on Server1. Users hosted on Server1 can send email to [email protected] successfully.
You need to identify what causes the email delivery to fail.
What should you use?

A. the Exchange admin center
B. the on-premises Exchange admin center
C. Azure AD Connect Health
D. the Azure Active Directory admin center

Show Suggested Answer

Suggested Answer: C 🗳️

by Jejechu at Nov. 26, 2020, 10:58 p.m.

Comments

Submit Cancel

Jejechu

Highly Voted 3 years, 8 months ago

I think the answer is A. I would check first on EXO Admin Center if user1 appears as a Mail User. If not, I would check AD Connect and launch a delta sync if everything is correct with the synced OUs

upvoted 14 times

J4U

2 years, 10 months ago

If A is correct, D is also a feasible choice to verify whether the account is synced. IMO, the NDR saying user not found, means this user isn't available in cloud. The next step is to verify whether this account is synced or not in AAD Connect.

upvoted 2 times

...

FlyG6

3 years ago

I would agree with jejechu. The answer should be A, if you want to know the cause of the error.

upvoted 1 times

...

Abdou1604

2 years, 5 months ago

but users can exchange mails in server1 , so user health state and mailbox is good so it must be synchro issue ! so its D !

upvoted 1 times

...

Seph1981

Highly Voted 3 years, 2 months ago

In a real world scenario, both answers A and C would be viable. Is completely natural to search in the EAC first to see if the mail user is there, and if not, then move to check if there is any problem with the synchronization of the user. But we can only choose one, and the question states that "User1 was not found" from the NDR message. With this information it is redundant to check the EAC for the User1, because if a mail user exists in Exchange Online for User1 the NDR message should not be the one mentioned. So choosing just one, i would point directly to a sync for user1 as the cause of the error.

upvoted 11 times

...

Amir1909

Most Recent 8 months, 2 weeks ago

C is correct

upvoted 1 times

...

ServerBrain

10 months, 1 week ago

Selected Answer: C

Since it's a new mailbox that has just been created on On-Prem Server1, it's a synch issue!

upvoted 1 times

...

yaboo1617

11 months ago

Selected Answer: C

User doesn't exist in 365/Azure, gotta check the reason il AD Connect Health

upvoted 1 times

...

jonasrcampos

1 year, 3 months ago

Selected Answer: A

Its Correct

upvoted 1 times

...

DD2021

2 years, 4 months ago

04/16/2022 - on the exam

upvoted 1 times

...

XXXX

2 years, 4 months ago

I had this issue, where AD Connect was not synching after server was upgraded from Server 212 to Server 216, so I know for sure its caused by AD Connect health

upvoted 3 times

...

SkyGurl

2 years, 4 months ago

3/24/2022 - on the exam

upvoted 3 times

...

hubran

2 years, 6 months ago

Selected Answer: C

The description says: "On Server1, you create a new mailbox that uses an email address of [email protected]", so mailbox is already created on-prem and you need to check if it is synched to the cloud.

upvoted 3 times

...

Budakkan

2 years, 6 months ago

exam dated 26-jan-22

upvoted 3 times

...

learnerearner

2 years, 7 months ago

Selected Answer: C

since its on-premise mailbox, it needs to be sync with Azure before exchange online users can send the email to it. i would go with C

upvoted 2 times

...

emlch

2 years, 8 months ago

Selected Answer: C

of course checking if the user appears on exo admin center would be the first thing that most of people would do but they are looking for WHERE IS THE PROBLEM that it seems to be on ad connect.

upvoted 3 times

...

Exchangist

2 years, 10 months ago

Agreed its an ambiguous scenario question, but the clue is: - mail-flow is working for all other users - mailbox was recently created and the NDR is unique to this user - The NDR actually says the user can't be found which is typically a directory AD issue Best answer is C based on information provided.

upvoted 2 times

...

albie101

3 years, 2 months ago

Braindump2 says A

upvoted 1 times

...

mackypatio

3 years, 2 months ago

If a recipient is not found, i would say i would go to EAC first on exchange online and search for it. I dont know if that is the best way to do it, but that is what i do first all the time. That is the first thing that comes to my mind.

upvoted 1 times

...

casti

3 years, 6 months ago

A. It may be the case that the user does not have an assigned license. This error was not detected by azure ad connect. Going to the exchange administrator can give us clues since it does not have a license, it does not appear as a mailbox, although it is well synchronized with Azure AD

upvoted 1 times

casti

3 years, 6 months ago

Sorry. if the user can send from Exchange online, it is licensed. Even so I still think that the exchange administrator is the best tool, since it has been able to synchronize with the user domain / user1, or it can be a mailuser, both errors are verifiable in the Exchange online EAC

upvoted 1 times

scotths

3 years, 2 months ago

Users on prem don't need to be licensed. So not a licensing concern. If the mailbox exists and the object is synced it would get there. My gut is also C is correct and explanation is plausible - but to be honest I would probably look in EAC first and then scratch my head and move over and find the issue in azure ad connect health.

upvoted 2 times

...

Load full discussion...