The answer is a synchronization issue with on-premises Active Directory, specifically that the user's MFA registration is being reset due to Azure AD Connect sync. When Azure AD Connect synchronizes a user object from on-premises AD, it can overwrite the cloud MFA registration state if the on-premises attribute, such as StrongAuthenticationMethods or StrongAuthenticationTime, is not set or is reset. This causes the cloud to treat the user as unregistered, prompting MFA registration again despite a previous successful registration. On the MD-102 exam, this scenario tests your understanding of how hybrid identity synchronization can disrupt cloud-only security policies, often appearing as a trap where candidates blame the Identity Protection policy rather than the sync process. Remember the key tip: if a user registers MFA successfully but is prompted again after a sync cycle, the culprit is almost always an on-premises attribute overwrite—think "sync strips the stamp."
MD-102 Manage identity and compliance Practice Question
This MD-102 practice question tests your understanding of manage identity and compliance. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Refer to the exhibit. The JSON snippet shows the Azure AD Identity Protection MFA registration policy configuration for the Contoso tenant. A new user, Jane, joins the company and is assigned a license. Jane attempts to access the Azure portal and is prompted to register for MFA. She registers successfully. However, the next day, she is again prompted to register for MFA. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The user's MFA registration is being reset due to a synchronization issue with on-premises Active Directory.
The most likely cause is that the user's MFA registration is being reset due to a synchronization issue with on-premises Active Directory. When Azure AD Connect synchronizes a user object from on-premises AD, it can overwrite the cloud MFA registration state if the on-premises attribute (such as 'StrongAuthenticationMethods' or 'StrongAuthenticationTime') is not set or is reset. This causes the user to be treated as unregistered, prompting MFA registration again despite a previous successful registration.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The MFA registration policy is disabled.
Why it's wrong here
The policy state is enabled.
✓
The user's MFA registration is being reset due to a synchronization issue with on-premises Active Directory.
Why this is correct
If the user is synced from on-premises, changes in on-premises can reset the MFA registration state.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The policy is not including all users.
Why it's wrong here
The policy includes allUsers.
✗
The policy excludes the user Jane.
Why it's wrong here
The policy excludes only admin@contoso.com.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume the issue is with the policy configuration (enabled, scope, or exclusions) rather than recognizing that a synchronization reset of the MFA registration state is the root cause in a hybrid environment.
Detailed technical explanation
How to think about this question
Azure AD Identity Protection MFA registration policy relies on the user's registration state stored in Azure AD. When Azure AD Connect synchronizes from on-premises AD, it can reset the 'StrongAuthenticationMethods' attribute if the on-premises attribute is null or not configured, effectively clearing the cloud registration. This is a common issue in hybrid environments where the on-premises schema does not include the necessary MFA attributes, causing repeated registration prompts after each sync cycle.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this MD-102 question in full detail.
Manage identity and compliance — This question tests Manage identity and compliance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The user's MFA registration is being reset due to a synchronization issue with on-premises Active Directory. — The most likely cause is that the user's MFA registration is being reset due to a synchronization issue with on-premises Active Directory. When Azure AD Connect synchronizes a user object from on-premises AD, it can overwrite the cloud MFA registration state if the on-premises attribute (such as 'StrongAuthenticationMethods' or 'StrongAuthenticationTime') is not set or is reset. This causes the user to be treated as unregistered, prompting MFA registration again despite a previous successful registration.
What should I do if I get this MD-102 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This MD-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MD-102 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.