Question 220
A company changes its employee email domain but wants Salesforce SAML account continuity. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Favor stable external identity subject mapping and plan controlled updates to mutable profile attributes. Verification: Test name or email changes against unchanged federation identifiers and audit links. Boundary: Renaming an identity must not silently provision a second account with more access” addresses the access-design responsibilities in a company changes its employee email domain but wants Salesforce SAML account continuity Test against test name or email changes against unchanged federation identifiers and audit links; renaming an identity must not silently provision a second account with more access.
Incorrect Answers
“Action: Favor stable external identity subject mapping and plan controlled updates to mutable profile attributes. Verification: Validate API principal scope, idempotent create/update, failure retries and deactivation latency. Boundary: A valid third-party social identity is not permission to create unrestricted Salesforce users” may apply to a related identity task, but it does not establish test name or email changes against unchanged federation identifiers and audit links for a company changes its employee email domain but wants Salesforce SAML account continuity The controlling boundary is: Renaming an identity must not silently provision a second account with more access.
“Action: Design My Domain login policies with an authorized SSO entry point and a controlled account recovery path. Verification: Inspect signature validation, certificate validity, issuer ID and Salesforce SSO error logs. Boundary: Renaming an identity must not silently provision a second account with more access” may apply to a related identity task, but it does not establish test name or email changes against unchanged federation identifiers and audit links for a company changes its employee email domain but wants Salesforce SAML account continuity The controlling boundary is: Renaming an identity must not silently provision a second account with more access.
“Action: Correct the registered service provider audience, recipient, ACS and active site endpoint rather than changing permissions. Verification: Test name or email changes against unchanged federation identifiers and audit links. Boundary: A signed SAML assertion from the correct issuer can still target the wrong service provider or Salesforce user” may apply to a related identity task, but it does not establish test name or email changes against unchanged federation identifiers and audit links for a company changes its employee email domain but wants Salesforce SAML account continuity The controlling boundary is: Renaming an identity must not silently provision a second account with more access.