Question 230
After implementing the design, the architecture team must validate: A contractor must authenticate through an IdP but a firewall uses a local static user list that drifts from the directory. What observed evidence best establishes the intended state?
Explanation
Correct Answer
Offboarded contractors fail new authentication while current employees remain authorized. It validates the recommended action: Use supported identity federation/authentication integration with Cloud Identity Engine or CAS as appropriate. The design principle is: Static local lists become stale when the authoritative identity provider changes.
Incorrect Answers
A controlled login validates the trusted issuer and user-role claims while invalid signatures fail. That observation supports a DIFFERENT situation: An SSO rollout changes issuer signing certificates and all security portal logins begin failing. Here the selected design is: Use supported identity federation/authentication integration with Cloud Identity Engine or CAS as appropriate.
A permitted administrator accesses configuration while a normal SSO user cannot. That observation supports a DIFFERENT situation: An administrator wants privileged web-console access but basic SAML login does not distinguish admin roles. Here the selected design is: Use supported identity federation/authentication integration with Cloud Identity Engine or CAS as appropriate.
Directory groups populate as expected without granting unnecessary account modification rights. That observation supports a DIFFERENT situation: A cloud directory connector requests unrestricted tenant directory write access to support read-only identity mapping. Here the selected design is: Use supported identity federation/authentication integration with Cloud Identity Engine or CAS as appropriate.