An administrator needs to see the platform as a particular user sees it, in order to confirm what that user can open, and cannot ask that user for their password. Which TWO statements describe how the platform's impersonation feature behaves? Select TWO.
- AImpersonation lets an administrator work with the roles of the selected user without knowing that user's password. Correct
- BImpersonation adds the selected user's roles to the administrator's own, so the session holds the sum of both role sets.
- CWork carried out while impersonating is attributed to the selected user, and the platform records that an impersonation took place. Correct
- DImpersonation requires the selected user to be signed out first, and their next sign in ends the administrator's impersonated session.
- EImpersonation is set for the instance as a whole, so every administrator signed in at that moment sees the selected user's view.
Why A is correct: Correct. Impersonation switches the session to the selected user's identity and role set, which is why it is the supported way to reproduce what a user can and cannot see.
Why B is wrong: Tempting because the administrator starts the session and can end it at will, which suggests their own access is retained. It is wrong because impersonation replaces the effective roles rather than adding to them, and a combined role set would defeat the purpose of testing another user's view.
Why C is correct: Correct. Records touched during the session carry the impersonated user as the actor, and the platform keeps its own trace of the impersonation so the real administrator remains accountable.
Why D is wrong: Tempting because it sounds like a sensible safeguard against two sessions for one identity. It is wrong because impersonation is independent of whether the selected user is signed in, and their activity does not terminate the administrator's session.
Why E is wrong: Tempting because instance level configuration does change what everyone sees. It is wrong because impersonation is scoped to the single session that started it and has no effect on any other signed in user.