- A
Assign to 'All users', condition: 'Device state (preview) is not compliant', grant: 'Require MFA', exclude: 'BreakGlass group'
This configuration correctly uses the device state condition to target non-compliant devices, requires MFA, and excludes the break-glass accounts. The policy applies when a non-compliant device tries to access the Azure Management portal.
- B
Assign to 'All users', condition: 'Sign-in risk is medium or higher', grant: 'Require MFA', exclude: 'BreakGlass group'
Why wrong: Sign-in risk condition is based on the likelihood of the sign-in being compromised, not on device compliance. This does not meet the requirement for non-compliant devices.
- C
Assign to 'All users', condition: 'Client apps: Browser and Mobile apps', grant: 'Block access', exclude: 'BreakGlass group'
Why wrong: Blocking access for browser and mobile apps is too broad and does not require MFA. The requirement is to require MFA on non-compliant devices, not block all access.
- D
Assign to 'All users', condition: 'Device platform: Android, iOS, Windows, macOS', grant: 'Require MFA', exclude: 'BreakGlass group'
Why wrong: Device platform condition targets specific OS types, not compliance status. It would require MFA on all devices of those platforms, regardless of compliance, which is not the requirement.
Quick Answer
The correct answer is to assign the Conditional Access policy to 'All users', set the condition 'Device state (preview) is not compliant', grant 'Require MFA', and exclude the 'BreakGlass' group. This configuration directly maps to the requirement because the device state condition targets only non-compliant devices, while the grant control enforces MFA specifically for the Azure Management portal, selected under Cloud apps. On the MS-102 exam, this scenario tests your understanding of how Conditional Access policies combine assignments, conditions, and grants to enforce granular access controls, with a common trap being the mistaken use of the 'All devices' condition instead of the device state filter. Remember that excluding the BreakGlass group is critical for emergency access, and the policy must be scoped to 'All users' to cover every non-compliant device scenario. A helpful memory tip: "Non-compliant device + MFA grant = conditional access for risky portals, but always exclude your break-glass accounts."
MS-102 Practice Question: Implement and manage identity and access in Microsoft Entra ID
This MS-102 practice question tests your understanding of implement and manage identity and access in microsoft entra id. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. A key principle to apply: conditional Access policies require Microsoft Entra ID P1 or P2 licenses.. 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.
A company uses Microsoft Entra ID P2 licenses. They want to require multi-factor authentication (MFA) for all users when accessing the Azure Management portal, but only from devices that are not marked as compliant. Additionally, a group named 'BreakGlass' must be excluded from this requirement. Which Conditional Access policy configuration should be applied?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Assign to 'All users', condition: 'Device state (preview) is not compliant', grant: 'Require MFA', exclude: 'BreakGlass group'
Option A is correct because it directly maps the requirement: assign the policy to 'All users', use the 'Device state (preview) is not compliant' condition to target only non-compliant devices, grant 'Require MFA' for the Azure Management portal (selected via the 'Cloud apps' condition), and exclude the 'BreakGlass' group. This ensures MFA is enforced only when accessing the Azure Management portal from non-compliant devices, while break-glass accounts are exempt.
Key principle: Conditional Access policies require Microsoft Entra ID P1 or P2 licenses.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Assign to 'All users', condition: 'Device state (preview) is not compliant', grant: 'Require MFA', exclude: 'BreakGlass group'
Why this is correct
This configuration correctly uses the device state condition to target non-compliant devices, requires MFA, and excludes the break-glass accounts. The policy applies when a non-compliant device tries to access the Azure Management portal.
Related concept
Conditional Access policies require Microsoft Entra ID P1 or P2 licenses.
- ✗
Assign to 'All users', condition: 'Sign-in risk is medium or higher', grant: 'Require MFA', exclude: 'BreakGlass group'
Why it's wrong here
Sign-in risk condition is based on the likelihood of the sign-in being compromised, not on device compliance. This does not meet the requirement for non-compliant devices.
- ✗
Assign to 'All users', condition: 'Client apps: Browser and Mobile apps', grant: 'Block access', exclude: 'BreakGlass group'
Why it's wrong here
Blocking access for browser and mobile apps is too broad and does not require MFA. The requirement is to require MFA on non-compliant devices, not block all access.
- ✗
Assign to 'All users', condition: 'Device platform: Android, iOS, Windows, macOS', grant: 'Require MFA', exclude: 'BreakGlass group'
Why it's wrong here
Device platform condition targets specific OS types, not compliance status. It would require MFA on all devices of those platforms, regardless of compliance, which is not the requirement.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is confusing 'Device state (preview) is not compliant' with other conditions like 'Sign-in risk' or 'Device platform', leading candidates to pick options that target risk levels or OS types instead of the specific compliance status required.
Detailed technical explanation
How to think about this question
The 'Device state (preview)' condition in Conditional Access evaluates the device's compliance status reported by Microsoft Intune (or another MDM) via the device's registration with Azure AD. When a device is marked as non-compliant, the policy triggers MFA, but compliant devices bypass MFA for the Azure Management portal. The 'BreakGlass' exclusion ensures emergency access accounts are not locked out, as they typically have no MFA capability and must be excluded from all Conditional Access policies.
KKey Concepts to Remember
- Conditional Access policies require Microsoft Entra ID P1 or P2 licenses.
- 'Device state' condition evaluates if a device is marked compliant by Intune or integrated MDM.
- Exclusion groups are vital for break-glass accounts to prevent lockout.
- Conditional Access policies are applied at the time of sign-in to cloud apps.
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
Conditional Access policies require Microsoft Entra ID P1 or P2 licenses.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Review conditional Access policies require Microsoft Entra ID P1 or P2 licenses., then practise related MS-102 questions on the same topic to reinforce the concept.
- →
Implement and manage identity and access in Microsoft Entra ID — study guide chapter
Learn the concepts, then practise the questions
- →
Implement and manage identity and access in Microsoft Entra ID practice questions
Targeted practice on this topic area only
- →
All MS-102 questions
975 questions across all exam domains
- →
Microsoft 365 Administrator MS-102 study guide
Full concept coverage aligned to exam objectives
- →
MS-102 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related MS-102 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Deploy and manage a Microsoft 365 tenant practice questions
Practise MS-102 questions linked to Deploy and manage a Microsoft 365 tenant.
Implement and manage Microsoft Entra identity and access practice questions
Practise MS-102 questions linked to Implement and manage Microsoft Entra identity and access.
Manage security and threats by using Microsoft Defender XDR practice questions
Practise MS-102 questions linked to Manage security and threats by using Microsoft Defender XDR.
Manage compliance by using Microsoft Purview practice questions
Practise MS-102 questions linked to Manage compliance by using Microsoft Purview.
Manage users, groups, licensing, and support practice questions
Practise MS-102 questions linked to Manage users, groups, licensing, and support.
Implement and manage identity and access in Microsoft Entra ID practice questions
Practise MS-102 questions linked to Implement and manage identity and access in Microsoft Entra ID.
MS-102 fundamentals practice questions
Practise MS-102 questions linked to MS-102 fundamentals.
MS-102 scenario practice questions
Practise MS-102 questions linked to MS-102 scenario.
MS-102 troubleshooting practice questions
Practise MS-102 questions linked to MS-102 troubleshooting.
Practice this exam
Start a free MS-102 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this MS-102 question test?
Implement and manage identity and access in Microsoft Entra ID — This question tests Implement and manage identity and access in Microsoft Entra ID — Conditional Access policies require Microsoft Entra ID P1 or P2 licenses..
What is the correct answer to this question?
The correct answer is: Assign to 'All users', condition: 'Device state (preview) is not compliant', grant: 'Require MFA', exclude: 'BreakGlass group' — Option A is correct because it directly maps the requirement: assign the policy to 'All users', use the 'Device state (preview) is not compliant' condition to target only non-compliant devices, grant 'Require MFA' for the Azure Management portal (selected via the 'Cloud apps' condition), and exclude the 'BreakGlass' group. This ensures MFA is enforced only when accessing the Azure Management portal from non-compliant devices, while break-glass accounts are exempt.
What should I do if I get this MS-102 question wrong?
Review conditional Access policies require Microsoft Entra ID P1 or P2 licenses., then practise related MS-102 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Conditional Access policies require Microsoft Entra ID P1 or P2 licenses.
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 →
Last reviewed: Jun 11, 2026
This MS-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 MS-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.