When a public-works employee is terminated in Active Directory, Horizon entitlements and the Intelligent Hub catalog should stop. What identity design does that describe?
Select an answer to reveal the explanation.
Short Explanation
Turning off the badge in Active Directory should lock the VDI door and the Hub catalog together. Directory is the civic source of truth for joiners, movers, and leavers. A leftover local UEM account or an NSX tag is not that lifecycle design.
Full Explanation
When AD termination should stop Horizon entitlements and Intelligent Hub catalog access, directory identity is the source of truth for joiner/mover/leaver so EUC follows the AD account. In municipal EUC terms, treat the endpoint as a window into city systems when the architecture says so, not as the system of record for the files or apps in the stem. Distractor concept: A local UEM-only account that outlives AD disable breaks leaver automation. Distractor concept: A fat-client local Windows account is not the system of record for VDI access in the municipal design. Distractor concept: An NSX DFW tag alone is not the identity lifecycle design for revoking Horizon and Hub. Exam caveat: Leaver questions map to directory as SoT for EUC entitlements—not leftover local accounts or firewall tags as identity. Operational check: Disable a test AD account and verify Horizon entitlement and Hub catalog access stop without relying on a lingering local UEM login. Record the chosen control and the rejected failure modes in the civic change ticket or runbook so on-call staff and auditors share the same rationale after the next maintenance window. Re-validate after personnel or image changes that the same control still meets the city's continuity, security, and support expectations for this service.