The EC-Council Disaster Recovery Professional v3 (EDRP) (312-76)

Bootrec /RebuildBCD repairs the Boot Configuration Data (BCD) store, fixing boot manager corruption, as Matt needs for Windows Server 2012.

Option A (sfc /scannow): Scans system files, not boot-specific.

Option B (ntdsutil): Active Directory tool, not boot repair.

Option D (repadmin): Replication diagnostics, not boot-related.

“Bootrec /RebuildBCD in Windows recovery rebuilds the BCD store, resolving boot manager issues post-update” (Module: System Recovery, Section: Windows Recovery Commands).

System Restore in Windows 10 creates restore points to preserve system state (files, apps, settings) for recovery.

Option A (System Backup): Full backup, not point-in-time preservation.

Option C (System Update): Updates OS, not preservation.

Option D (Failover Replication): DR term, not Windows feature.

“System Restore in Windows preserves system state via restore points, enabling recovery of files and settings” (Module: System Recovery, Section: Windows Tools).

Backup Integrity Testing is the process of verifying that backed-up data remains safe, secure, and readable after operations such as updates, restores, or retrievals. This involves checking for corruption, ensuring data consistency, and confirming that the backup can be successfully restored. In disaster recovery, this is a critical step to ensure that backups are reliable when needed.

Option A (Database Authentication): Refers to verifying user access, not data integrity.

Option B (Database Consolidation): Involves merging databases, not testing backup integrity.

Option C (Database Integrity Testing): Focuses on database consistency, not specifically backup verification.

“Backup Integrity Testing ensures that data backups remain uncorrupted and usable post-operation. This process includes validation checks after updates or restores to guarantee recoverability, a key component of data protection strategies” (Module: Data Backup and Recovery, Section: Backup Validation Techniques).

System Recovery is the process of restoring a system’s applications and data to a previous state within an acceptable timeframe, as described.

Option A (System Migration): Moving systems, not restoring.

Option B (System Backup): Creating copies, not restoration.

Option C (System Replication): Duplicating data, not recovery.

“System Recovery restores applications and data to a prior state within defined timeframes, ensuring operational continuity post-disaster” (Module: System Recovery, Section: Recovery Processes).

NFPA 1600 (National Fire Protection Association Standard on Disaster/Emergency Management and Business Continuity Programs) is a widely recognized standard that provides a comprehensive framework for managing disasters and ensuring business continuity. It covers all phases—prevention, mitigation, preparedness, response, continuity, and recovery—and defines disasters explicitly.

Option B (ISO 27005): This is an information security risk management standard, not specific to disaster or business continuity programs.

Option C (INCITS 483-2012): This standard relates to virtualization security, not disaster management or business continuity.

Option D (ISO 27031): This focuses on ICT readiness for business continuity, a narrower scope than NFPA 1600.

EDRP v3 references NFPA 1600 as a key standard for disaster recovery and business continuity planning, emphasizing its holistic approach (Module: Business Continuity Management).

Cloud Backup provides encrypted, secure data storage accessible anytime, anywhere via the internet, meeting the company’s needs.

Option A (Offsite): Offsite, but not necessarily accessible or encrypted by default.

Option C (Onsite): Local, not location-independent.

Option D (Hot Site): Recovery site, not a backup method.

“Cloud Backup ensures data security with encryption and offers ubiquitous access, ideal for flexible recovery needs” (Module: Data Backup and Recovery, Section: Cloud-Based Solutions).

Risk Mitigation involves implementing measures (e.g., generator, malware protection) to reduce identified risks’ impact or likelihood, as Fred did.

Option A (Assessment): Evaluating risks, not acting.

Option B (Management): Broader process including mitigation.

Option C (Identification): Naming risks, not mitigating.

“Risk Mitigation applies specific actions to lessen the impact or probability of identified risks, such as power or email threats” (Module: Risk Management, Section: Mitigation Strategies).

A Survivable Storage System is designed to maintain data integrity and access despite failures or attacks, as described (e.g., PASIS architecture).

Option B (Decentralized Computing): Broad computing model, not storage-specific.

Option C (Mirroring): Redundancy technique, not a full system.

Option D (Mainframe): Robust systems, but not survivability-focused.

“Survivable Storage Systems ensure data availability and integrity against failures and attacks across storage and network components” (Module: Survivable Storage Systems, Section: Overview).

Managed Disaster Recovery (MDR) involves third-party services handling backups and offsite replication, providing a comprehensive solution for data protection and recovery. This fits the description of outsourcing backup and replication to an external provider.

Option A (Continuous Data Protection): Real-time backup technology, not inherently third-party or offsite-focused.

Option C (Tape Vaulting): Offsite tape storage, but not replication-focused and typically manual, not managed.

Option D (Disk Shadowing): A form of mirroring, not third-party or offsite by definition.

“Managed Disaster Recovery leverages third-party expertise for offsite replication and backups, ensuring robust data protection with minimal internal overhead” (Module: Disaster Recovery Strategies, Section: Managed Services).