Question 480
An acquired business has hundreds of user profiles with inconsistent object entitlements. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties. Verification: Review license prerequisites, profile defaults, permission sets and effective access tests. Boundary: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged” addresses the access-design responsibilities in an acquired business has hundreds of user profiles with inconsistent object entitlements Test against review license prerequisites, profile defaults, permission sets and effective access tests; a successful federation login does not prove that the user's actual Salesforce data rights are least privileged.
Incorrect Answers
“Action: Preserve Setup Audit Trail and relevant configuration-change evidence with approved retention. Verification: Review license prerequisites, profile defaults, permission sets and effective access tests. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation” may apply to a related identity task, but it does not establish review license prerequisites, profile defaults, permission sets and effective access tests for an acquired business has hundreds of user profiles with inconsistent object entitlements The controlling boundary is: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged.
“Action: Use a login flow for approved post-authentication business steps without replacing core authentication controls. Verification: Compare new permissions, active sessions, app policies and denied legacy actions. Boundary: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged” may apply to a related identity task, but it does not establish review license prerequisites, profile defaults, permission sets and effective access tests for an acquired business has hundreds of user profiles with inconsistent object entitlements The controlling boundary is: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged.
“Action: Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties. Verification: Inspect permission activation event, session level, granted rights and expiration. Boundary: A second password or another knowledge-only challenge is not automatically an independent MFA factor” may apply to a related identity task, but it does not establish review license prerequisites, profile defaults, permission sets and effective access tests for an acquired business has hundreds of user profiles with inconsistent object entitlements The controlling boundary is: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged.