Which practice supports reconciliation of user state across systems?

• A. Scheduled reconciliations, event-driven updates, and consistent attribute mappings.
• B. One-time export with no ongoing updates.
• C. Isolated directories with no mappings.
• D. Manual changes only in each system.

Answer: (A)

Reconciliation of user state across systems means keeping the same user data and entitlements consistent in every connected system. The best approach combines scheduled reconciliations to regularly detect any drift, event-driven updates to push changes as soon as they happen, and consistent attribute mappings so the same user fields (like username, email, roles) line up across systems. This creates automated, ongoing synchronization and verification, reducing gaps where a user’s data or access could become out of sync.

Why the other options fall short: a one-time export doesn’t address changes that occur after the export, leaving data out of date; isolated directories with no mappings can’t align identities across systems; manual changes only in each system lead to frequent divergence and are not scalable or reliable.