Question 600
A regional retailer connects customer identifiers across apps and claims the identity system alone solves consent and CRM matching. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Separate authentication federation from customer identity resolution, data governance and consent obligations. Verification: Verify ID links, profile merge policy, consent records and account ownership. Boundary: One login identity does not guarantee a complete accurate customer 360 data profile” addresses the access-design responsibilities in a regional retailer connects customer identifiers across apps and claims the identity system alone solves consent and CRM matching Test against verify ID links, profile merge policy, consent records and account ownership; one login identity does not guarantee a complete accurate customer 360 data profile.
Incorrect Answers
“Action: Separate authentication federation from customer identity resolution, data governance and consent obligations. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. Boundary: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership” may apply to a related identity task, but it does not establish verify ID links, profile merge policy, consent records and account ownership for a regional retailer connects customer identifiers across apps and claims the identity system alone solves consent and CRM matching The controlling boundary is: One login identity does not guarantee a complete accurate customer 360 data profile.
“Action: Inventory Identity Connect dependencies and design a supported migration before the existing subscription ends. Verification: Inspect source object IDs, provisioning feed, conflicts, deactivate path and stale account checks. Boundary: One login identity does not guarantee a complete accurate customer 360 data profile” may apply to a related identity task, but it does not establish verify ID links, profile merge policy, consent records and account ownership for a regional retailer connects customer identifiers across apps and claims the identity system alone solves consent and CRM matching The controlling boundary is: One login identity does not guarantee a complete accurate customer 360 data profile.
“Action: Treat subscription expiration as a migration deadline and document affected features and user controls. Verification: Verify ID links, profile merge policy, consent records and account ownership. Boundary: Switching sync tools without controlling identity continuity can create duplicate users or orphan permissions” may apply to a related identity task, but it does not establish verify ID links, profile merge policy, consent records and account ownership for a regional retailer connects customer identifiers across apps and claims the identity system alone solves consent and CRM matching The controlling boundary is: One login identity does not guarantee a complete accurate customer 360 data profile.