Question 200
A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself” addresses the access-design responsibilities in a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists Test against correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; just-in-Time account creation is not a timely offboarding mechanism by itself.
Incorrect Answers
“Action: Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping. Verification: Compare the actual assertion issuer, destination, audience, NameID format and signature chain. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.
“Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Test new and modified user assignments, permission sets, claims validation and denied-access cases. Boundary: Skipping signature verification to restore access would remove an essential federation security control” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.
“Action: Plan a supported cutover from delegated authentication to federation with rollback and account mapping tests. Verification: Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions. Boundary: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.