Question 80
A call center requires centrally administered access removal even if some employees do not revisit Salesforce immediately. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Establish an authoritative joiner-mover-leaver flow and independent deprovisioning controls beyond sign-in. Verification: Compare HR events, directory account changes, Salesforce active status and delayed sync recovery. Boundary: Success at initial provisioning does not prove timely privilege removal after employment ends” addresses the access-design responsibilities in a call center requires centrally administered access removal even if some employees do not revisit Salesforce immediately Test against compare HR events, directory account changes, Salesforce active status and delayed sync recovery; success at initial provisioning does not prove timely privilege removal after employment ends.
Incorrect Answers
“Action: Decouple trusted authentication from tenant-specific authorization and enforce scoped privileges after account matching. Verification: Test first login, required attributes, inactive status, license assignment and onboarding delay. Boundary: Success at initial provisioning does not prove timely privilege removal after employment ends” may apply to a related identity task, but it does not establish compare HR events, directory account changes, Salesforce active status and delayed sync recovery for a call center requires centrally administered access removal even if some employees do not revisit Salesforce immediately The controlling boundary is: Success at initial provisioning does not prove timely privilege removal after employment ends.
“Action: Define trusted issuer, certificate or signing-key verification, audience and endpoint registration before enabling federation. Verification: Compare HR events, directory account changes, Salesforce active status and delayed sync recovery. Boundary: Delegated authentication and SAML federation are not identical authentication mechanisms or migration tasks” may apply to a related identity task, but it does not establish compare HR events, directory account changes, Salesforce active status and delayed sync recovery for a call center requires centrally administered access removal even if some employees do not revisit Salesforce immediately The controlling boundary is: Success at initial provisioning does not prove timely privilege removal after employment ends.
“Action: Establish an authoritative joiner-mover-leaver flow and independent deprovisioning controls beyond sign-in. Verification: Inspect signed metadata, certificate rotation plan, assertion audience and ACS URL. Boundary: A protocol supported by the identity provider is insufficient if the relying application cannot validate it” may apply to a related identity task, but it does not establish compare HR events, directory account changes, Salesforce active status and delayed sync recovery for a call center requires centrally administered access removal even if some employees do not revisit Salesforce immediately The controlling boundary is: Success at initial provisioning does not prove timely privilege removal after employment ends.