Health inspectors should open a SaaS GIS after they sign in to Intelligent Hub, without a second prompt when policy allows. Which identity concept is that?
Select an answer to reveal the explanation.
Short Explanation
One Hub login that opens GIS is the same idea as a civic badge that opens more than one door. That is single sign-on through federation, not wiping the tablet. Instant clones and drive maps do not log the inspector in.
Full Explanation
Opening SaaS GIS after Intelligent Hub sign-in without a second prompt (when policy allows) is single sign-on through federation—not an MDM wipe of the tablet. 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: An instant-clone refresh clearing a GIS cookie is desktop lifecycle, not identity SSO. Distractor concept: An App Volumes package injecting a GIS password is credential stuffing, not federation. Distractor concept: A DEM drive mapping does not substitute for authentication. Exam caveat: One Hub login opening another app = SSO/federation; wipe, clones, packages, and drive maps are wrong concepts. Operational check: Validate Access federation for GIS after Hub auth, confirm no unexpected second prompt under policy, and document the IdP trust. 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.