Which practice supports reconciliation of user state across systems by ensuring consistency of identity attributes?

• A. Inconsistent attribute mappings
• B. Run tests only in production
• C. Consistent attribute mappings
• D. No event-driven updates

Answer: (C)

Maintaining alignment of identity attributes across systems is essential for reconciling user state. When attribute mappings are consistent, the same identifiers—like user IDs, emails, or usernames—mean the same person is represented in every system. This makes it possible to match records, merge duplicates, and propagate changes reliably, so updates in one place reflect correctly elsewhere.

The best practice, consistent attribute mappings, directly supports this reliable identity resolution and state reconciliation. Inconsistent mappings would create mismatches, making it hard to tell whether two records refer to the same user. Testing-only-in-production doesn’t address how identities are described and linked across systems, so it doesn’t fix reconciliation issues. And lacking event-driven updates means changes wouldn’t propagate timely across platforms, leading to stale or divergent user states.