An emergency-management office wants fundamentals-level awareness of Microsoft Entra ID for a city that still has some on-premises identities. Which capability framing is correct?
Select an answer to reveal the explanation.
Short Explanation
Plenty of cities still have one foot on-prem and one in the cloud—Entra ID is how those worlds talk identity. You do not need a deep hybrid lab for AB-900, just the awareness that Entra covers cloud identity including hybrid scenarios. It's not where you'll handle Group Policy enforcement for devices.
Full Explanation
Microsoft Entra ID provides cloud identity capabilities for Microsoft 365, and fundamentals coverage includes awareness that hybrid identity scenarios exist when a city still has on-premises directories. An emergency-management office should frame Entra ID as the cloud identity platform while recognizing hybrid topics at describe depth—not as awareness of Group Policy enforcement for devices and not as awareness of Connect Sync for cloud-only accounts or federation for cloud-only accounts. That conceptual framing matches AB-900 expectations for cities with mixed estates.
Framing Entra ID as including awareness of Group Policy enforcement for devices at fundamentals depth fails by concept because Entra ID's primary role is identity and access for users and apps, while Group Policy enforcement remains an on-premises Active Directory Domain Services capability. Claiming Entra ID provides cloud identity capabilities, including awareness of Connect Sync for cloud-only accounts at fundamentals depth fails because Connect Sync creates synchronized hybrid-origin identities, while cloud-only accounts are created directly in Entra ID without sync. Describing Entra ID as including awareness of federation for cloud-only accounts at fundamentals depth fails because federation applies to hybrid scenarios with on-premises directories, while cloud-only accounts authenticate directly in Entra ID without federation.
Exam caveat: Deep hybrid implementation (federation design, sync troubleshooting) belongs to higher-level admin exams. AB-900 stops at recognizing cloud identity plus hybrid awareness. Emergency-management stakeholders still need the correct conceptual model when some identities originate on-premises.
Operational check: Inventory whether emergency-management identities are cloud-only or hybrid-origin, confirm staff sign into Microsoft 365 via Entra ID, and record hybrid awareness in the fundamentals architecture brief without attempting advanced sync redesign under an AB-900 task. Validate that Group Policy enforcement for devices and Connect Sync or federation for cloud-only accounts are not mistaken for the cloud identity provider.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.