Question 0060 — Identity Management Concepts
At fictional Meadow Point Software 06B, the team managing directory consolidation reports: Two identity systems exchange a NameID email value while Salesforce expects FederationIdentifier, and SSO succeeds for some users but not for those with aliases. Which recurring assurance practice most directly reduces the chance of this same failure recurring?
Explanation
Preliminary explanations — specialist key review ON HOLD
Correct Answer
Test federation mappings with alias, rename and duplicate-name cases before production rollouts. This recurring control addresses the observed problem: Two identity systems exchange a NameID email value while Salesforce expects FederationIdentifier, and SSO succeeds for some users but not for those with aliases. The measurable check is: Inspect a failing SAML assertion against the user federation field and confirm aliases no longer affect account lookup.
Incorrect Answers
Reconcile identity-store joiner and leaver events with Salesforce account creation and deactivation records. Test federation mappings with alias, rename and duplicate-name cases before production rollouts.
Include production-versus-sandbox audience checks in automated SSO regression cases. Test federation mappings with alias, rename and duplicate-name cases before production rollouts.
Audit tenant-scoped identity crosswalks before each organizational directory consolidation. Test federation mappings with alias, rename and duplicate-name cases before production rollouts.