During MS-900 study, a city analyst must explain hybrid identity without configuring sync tools. Which statement stays at the correct fundamentals depth?
Select an answer to reveal the explanation.
Short Explanation
Know the idea: local directory plus Entra ID, connected. Do not dive into sync-tool troubleshooting—that is deeper admin territory. MS-900 wants the concept, not the wrench.
Full Explanation
Hybrid identity links on-premises directories with Microsoft Entra ID so both can be used together, which is the fundamentals-depth explanation a city analyst should give during MS-900 study without diving into sync-tool configuration. The exam wants the conceptual bridge—on-premises and cloud directories connected for coexistence—not deep engineering of Graph delta queries. Municipal analysts briefing managers should stay at that describe level unless an implementation project explicitly requires tooling detail.
Hybrid identity does not mean writing custom Microsoft Graph delta-query sync engines as the MS-900 skill. It is not only the name of a Conditional Access JSON template administrators must author on the exam. It is not identical to purchasing Windows 365 frontline licenses.
An exam caveat is that real deployments use Entra Connect or cloud sync, but naming those tools is secondary to understanding why hybrid identity exists: support mixed estates. Operationally, for study and stakeholder briefings, define hybrid identity as the link between on-premises directories and Entra ID, give one municipal example such as AD DS file servers plus Exchange Online, and reserve sync-tool workshops for implementation teams after the conceptual decision is clear.