Question 590
A service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems. Most decisive verification?
Explanation
Correct Answer
“Map identity source, federation roles, app audiences, license needs and lifecycle ownership” distinguishes sign-in from entitlement administration in a service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems It checks whether evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP.
Incorrect Answers
“Inspect source object IDs, provisioning feed, conflicts, deactivate path and stale account checks” needs to be evaluated against A service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.
“Verify subscription end date, identity sync, deactivation behavior and SSO fallback” needs to be evaluated against A service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.
“Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation” needs to be evaluated against A service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.