Which action best ensures disaster recovery readiness for identity services?

• A. Rely on manual processes with no backups.
• B. Rely on vendor recovery only.
• C. Disable all logging during disaster.
• D. Ensure backups of identity data, establish IAM service failover, maintain runbooks, and conduct regular disaster recovery tests for identity workflows.

Answer: (D)

Disaster recovery readiness for identity services means having a resilient setup that keeps authentication and access control available even when parts of the system fail. The best approach combines protecting identity data, keeping the service running through proper failover, having clear recovery procedures, and validating everything with regular drills.

Backing up identity data is essential so you can fully restore users, groups, roles, policies, and credentials after a disruption. Establishing IAM service failover ensures the authentication system can switch to healthy instances or even another region without long downtime, preserving access for users and applications. Runbooks provide step-by-step, tested recovery actions so the team can respond quickly and consistently when disaster strikes. Regular disaster recovery tests verify that backups can be restored, failover works as expected, and that the recovery time and data loss targets are achievable, allowing you to refine the plan over time.

Relying solely on vendor recovery risks gaps in coverage or delays, and doing manual work with no backups leaves your identity data unrecoverable. Disabling logging during a disaster removes critical visibility for troubleshooting and auditing, making recovery harder and less secure.