Question 1
A regional insurer plans one employee login across Salesforce, payroll and an internal claims portal, but the application owners disagree about who grants permissions. Best next IAM response?
Explanation
Correct Answer
“Separate authentication, authorization and accountability responsibilities before selecting the federation pattern” addresses the access-design responsibilities in a regional insurer plans one employee login across Salesforce, payroll and an internal claims portal, but the application owners disagree about who grants permissions Test against map credential issuer, application permission owner and traceable audit events for each relying system; a shared login does not automatically grant the same data entitlements in all applications.
Incorrect Answers
“Establish an authoritative joiner-mover-leaver flow and independent deprovisioning controls beyond sign-in” may apply to a related identity task, but it does not establish map credential issuer, application permission owner and traceable audit events for each relying system for a regional insurer plans one employee login across Salesforce, payroll and an internal claims portal, but the application owners disagree about who grants permissions The controlling boundary is: A shared login does not automatically grant the same data entitlements in all applications.
“Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements” may apply to a related identity task, but it does not establish map credential issuer, application permission owner and traceable audit events for each relying system for a regional insurer plans one employee login across Salesforce, payroll and an internal claims portal, but the application owners disagree about who grants permissions The controlling boundary is: A shared login does not automatically grant the same data entitlements in all applications.
“Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required” may apply to a related identity task, but it does not establish map credential issuer, application permission owner and traceable audit events for each relying system for a regional insurer plans one employee login across Salesforce, payroll and an internal claims portal, but the application owners disagree about who grants permissions The controlling boundary is: A shared login does not automatically grant the same data entitlements in all applications.