After identifying duplicates, which is the recommended sequence to resolve them?

After identifying duplicates, which is the recommended sequence to resolve them?

• A. Delete all duplicates immediately without review.
• B. Notify users and defer action for later.
• C. Create new roles to cover missing permissions.
• D. Identify duplicates via the user ID, merge or deactivate duplicates, and consolidate roles.

Answer: (D)

In identity and access management, handling duplicates in a careful, structured way protects data integrity and keeps access control clear. Start by identifying duplicates using the unique user ID, which ties all records to the same person rather than relying on names or emails that can change or collide. This ensures you’re matching the right accounts across systems. Next, merge or deactivate the duplicate records so there is a single active account. This prevents conflicting permissions and reduces the risk of unauthorized or unclear access. A unified account also makes auditing and compliance much simpler. Finally, consolidate the roles for the unified account. Review and align the permissions, remove redundancies, and ensure the user has the appropriate level of access without overlaps or gaps. This solidifies the governance around that user’s entitlements and avoids permission drift over time. Taking this sequence helps avoid data loss from hasty deletions, reduces security risk from lingering duplicates, and prevents the proliferation of new roles that don’t address the underlying duplication.

In identity and access management, handling duplicates in a careful, structured way protects data integrity and keeps access control clear. Start by identifying duplicates using the unique user ID, which ties all records to the same person rather than relying on names or emails that can change or collide. This ensures you’re matching the right accounts across systems.

Next, merge or deactivate the duplicate records so there is a single active account. This prevents conflicting permissions and reduces the risk of unauthorized or unclear access. A unified account also makes auditing and compliance much simpler.

Finally, consolidate the roles for the unified account. Review and align the permissions, remove redundancies, and ensure the user has the appropriate level of access without overlaps or gaps. This solidifies the governance around that user’s entitlements and avoids permission drift over time.

Taking this sequence helps avoid data loss from hasty deletions, reduces security risk from lingering duplicates, and prevents the proliferation of new roles that don’t address the underlying duplication.