312-76 EC-Council Disaster Recovery Professional v3 (EDRP) Questions and Answers

Proven Reliability is a hallmark of mainframes, known for uptime and robustness in critical applications.

Option B (Openness):More for open systems, not mainframes.

Option C (Pluralism):Not a technical feature.

Option D (Transparency):Not a mainframe characteristic.

“Mainframes feature proven reliability, supporting continuous operation for mission-critical environments” (Module: Computing Systems, Section: Mainframe Features).

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).

A Synthetic Backup combines a full backup with subsequent incremental backups to create an updated full backup, as described.

Option A (Incremental):Only changes, not combined with full.

Option B (Differential):Changes since last full, not synthesized.

Option D (Incremental Forever):Continuous incrementals, not full synthesis.

“Synthetic Backup merges a full backup with incrementals, creating an efficient, updated full copy for recovery” (Module: Data Backup and Recovery, Section: Backup Techniques).

The main objective of a Business Continuity (BC) test plan is to ensure the plan’s accuracy and relevance under adverse conditions, validating its effectiveness.

Option A:Secondary, not the primary goal.

Option C:Unplanned events may occur, but not the objective.

Option D:A consideration, not the main purpose.

“The primary objective of a BC test plan is to confirm its accuracy and relevance, ensuring it performs under disaster conditions” (Module: Testing Disaster Recovery Plans, Section: BC Testing Goals).

Colocation facilities provide shared infrastructure like cooling, power, and space (economic advantages) and support backups, but “recovery of servers” is not an inherent advantage—they don’t actively recover servers; that’s the tenant’s responsibility.

Option B (Backup):Supported via infrastructure for backup systems.

Option C (Cooling):A key feature of colocation.

Option D (Economic Advantages):Cost-sharing reduces expenses.

EDRP v3 notes colocation benefits like cooling and cost savings but excludes active server recovery as a facility-provided service (Module: Alternate Sites).

The Review Phase of scenario training occurs after execution and involves a debrief with participants to gather feedback, assess performance, and identify improvements. This aligns with the question’s focus on obtaining feedback post-training.

Option A (Execution Phase):The active running of the scenario, no debrief yet.

Option C (Warning Phase):Not a standard phase; implies pre-event alerts.

Option D (Planning Phase):Prepares the scenario, not for feedback collection.

“The Review Phase follows scenario execution, involving a debrief to collect participant feedback and refine the training process” (Module: Training and Awareness, Section: Training Phases).

RAID 0 splits data across drives (striping) for performance but offers no redundancy, requiring a minimum of two drives.

Option B:RAID 5 minimum, not RAID 0.

Option C/D:Higher RAID levels, not RAID 0.

“RAID 0 uses striping across at least two drives for speed, sacrificing redundancy for performance” (Module: Storage Technologies, Section: RAID Levels).

Network Attached Storage (NAS) is a dedicated server designed for file storage and sharing over a network, perfectly matching the question’s description.

Option A (Data Virtualization):Abstracts data access, not a server.

Option B (Cloud Storage):Offsite storage service, not a dedicated server.

Option C (SAN):Block-level storage network, not file-focused.

“NAS is a dedicated file storage and sharing server, accessible over networks, ideal for centralized data management” (Module: Storage Technologies, Section: NAS Overview).

Mission Essential Functions (MEF) are critical tasks an organization must maintain or quickly resume post-disruption to ensure continuity.

Option A (BIA):Identifies impacts, not tasks.

Option B (Mitigation):Reduces risks, not task-focused.

Option D (MAD):Downtime limit, not tasks.

“Mission Essential Functions (MEF) are vital tasks requiring continuous or rapid resumption to sustain operations post-incident” (Module: Business Continuity Planning, Section: MEF Definition).

Disaster Recovery (DR) encompasses restoring data, applications, and infrastructure post-disaster, ensuring business operations resume, aligning with the question’s broad scope.

Option A (Data Recovery):Limited to data, not applications or infrastructure.

Option C (Application Recovery):Focuses only on applications.

Option D (Recovery Management):A process, not the ability itself.

“Disaster Recovery restores data, applications, and infrastructure after a disaster, enabling business continuity” (Module: Disaster Recovery Planning, Section: DR Definition).

Polly estimated theImpact, which is the magnitude of damage (here, $200,000) resulting from a risk event (data leak). This drove her decision to upgrade, comparing it to the cost.

Option B (Hazard):A potential source of harm, not the damage estimate.

Option C (Likelihood):Probability of occurrence, not addressed here.

Option D (Vulnerability):Weakness (vulnerable server), not the damage itself.

“Impact, the estimated magnitude of loss from a risk event, such as a data leak costing $200,000, guides mitigation decisions in risk assessment” (Module: Risk Management, Section: Risk Factors).

In PASIS architecture, increasing confidentiality (e.g., via encryption) increases storage requirements due to added overhead (e.g., metadata, keys).

Option A (Reaction):Not a PASIS feature.

Option B (Latency):May increase, but not direct as storage.

Option D (Durability):Unaffected by confidentiality.

“Higher confidentiality in PASIS, through encryption, directly increases storage needs due to additional data overhead” (Module: Survivable Storage Systems, Section: PASIS Trade-offs).

 RAID 1:Mirroring. Requires a minimum of 2 drives. Provides high redundancy but doesn't inherently increase read/write speed significantly on its own.

 RAID 5:Striping with parity. Requires a minimum of 3 drives. Offers a balance of performance and fault tolerance. Not high fault tolerance as asked.

 RAID 10 (RAID 1+0):A combination of mirroring and striping. Requires a minimum of 4 drives. Provides high performance and good fault tolerance.

 RAID 50 (RAID 5+0):A combination of RAID 5 striping with parity and RAID 0 striping. Requires a minimum of 6 drives. Provides high performance and higher fault tolerance than RAID 5.

An Incremental Backup captures only files created or modified since the last backup (full or incremental), making it faster and less storage-intensive, as Kelly is doing.

Option A (Full Backup):Copies all data, not just changes.

Option B (Normal Backup):Synonym for full backup, not selective.

Option D (Differential Backup):Copies changes since the last full backup, not the last backup.

“Incremental Backups save only data changed since the last backup, optimizing speed and storage for frequent operations” (Module: Data Backup and Recovery, Section: Backup Types).

Global Load Balancing routes traffic across geographically distributed servers (e.g., London to Mumbai) to optimize performance and handle server loss, as described.

Option A (High-Availability):Ensures uptime, not geographic routing.

Option C (Failover):Switches to a backup, not load distribution.

Option D (Network Load Balancing):Local load sharing, not global.

“Global Load Balancing distributes traffic across global servers, mitigating slowdowns from server loss by rerouting effectively” (Module: System Resilience, Section: Traffic Management).

In virtualization (e.g., VMware, Hyper-V), deleting snapshots may not free space if dependent child disks (differencing disks) remain. Deleting these child disks consolidates space, resolving Remus’s issue.

Option B:Deleting the VM database risks data loss, not space recovery.

Option C (Uninstall Hypervisor):Drastic, loses all VMs.

Option D (Shutdown/Restart):Temporary, doesn’t free space.

“Deleting child disks of snapshots in VMs consolidates storage, freeing space when snapshot deletion alone is insufficient” (Module: Virtualization and Recovery, Section: Storage Management).

A Team-wide BIA (Business Impact Analysis) evaluates interruptions specific to a department or team due to internal system failures, as described.

Option B (Organization-wide):Covers the entire organization, not department-specific.

Option C (Country-wide):Too broad, not system-focused.

Option D (Branch-wide):Branch-level, not necessarily team/department.

“Team-wide BIA assesses the impact of internal system failures on a specific department, tailoring continuity plans to team needs” (Module: Business Impact Analysis, Section: BIA Scope).

A Software Defined Data Center (SDDC) is a fully virtualized infrastructure where storage, compute, and networking are abstracted and delivered as a service, aligning with the question’s description. It encompasses more than just storage, including processing capabilities.

Option A (Cloud-based Storage):Refers only to storage, not a full facility with processing.

Option B (Virtual Machines):Individual virtualized servers, not a complete facility.

Option D (Data Virtualization):Focuses on abstracting data access, not a full service facility.

EDRP v3 covers SDDC as an advanced virtualization concept for disaster recovery and service delivery (Module: Virtualization and Cloud Computing).

Crisis Management involves strategies to handle sudden, significant events (e.g., disasters), focusing on immediate response and mitigation, as described.

Option A (Risk Assessment):Identifies risks, not manages events.

Option B (Application Recovery):Restores applications, not a broad strategy.

Option D (BIA):Analyzes impacts, not event handling.

“Crisis Management applies strategies to address sudden, disruptive events, ensuring organizational stability during emergencies” (Module: Crisis Management, Section: Overview).

Opportunity Cost is the value of the next best alternative forgone when choosing one option over others, directly matching the question’s definition.

Option A (BIA):Assesses disruption impacts, not alternatives.

Option C (Fixed Cost):A static expense, unrelated to choices.

Option D (Cost Benefit Analysis):Compares costs and benefits, not forgone gains.

“Opportunity Cost represents the potential benefit lost by choosing one recovery strategy over another, a key consideration in resource allocation” (Module: Risk Management, Section: Cost Analysis).

Electronic Vaulting transfers data electronically (e.g., via FTP) to a remote backup site, as Jennifer is doing.

Option B (Disk Duplexing):RAID technique, not remote transfer.

Option C (Disk Shadowing):Mirroring, not offsite transfer.

Option D:Manual process, not electronic via FTP.

“Electronic Vaulting uses electronic means, such as FTP, to transfer critical data to a remote backup site for protection” (Module: Data Backup and Recovery, Section: Remote Backup Methods).

Availability ensures a system is operational and can serve requests correctly and timely, directly matching the question’s focus.

Option B (Integrity):Ensures data accuracy, not service delivery.

Option C (Nonrepudiation):Prevents denial of actions, not request handling.

Option D (Precaution):A preventive measure, not a system property.

“Availability is the system’s capacity to respond to requests effectively, a cornerstone of disaster recovery and continuity” (Module: System Resilience, Section: Core Properties).

Detailed Awareness Training targets key BCP execution staff, providing in-depth knowledge of framework, processes, and strategies, as described.

Option B (Simulation):Hands-on practice, not framework-focused.

Option C (Scenario):Scenario-based, not comprehensive training.

Option D (Introductory):Basic overview, not detailed.

“Detailed Awareness Training equips key BCP personnel with deep understanding of processes and strategies for effective execution” (Module: Training and Awareness, Section: Training Types).

Confidentiality in PASIS ensures data is protected from unauthorized access, using encryption and access controls, aligning with Jessie’s goal of restricting access to authorized employees.

Option A (Reaction):Not a PASIS feature.

Option C (Availability):Ensures access, not restriction.

Option D (Maintenance):Not a security feature.

“Confidentiality in PASIS architecture secures data against unauthorized access, employing encryption and controls to safeguard critical information” (Module: Survivable Storage Systems, Section: PASIS Features).

An Incremental Backup only backs up files changed or added since the last backup (full or incremental), making it faster and less disruptive, ideal for Alan’s daily, small-volume needs.

Option B (Differential Backup):Backs up all changes since the last full backup, growing larger and slower over time.

Option C (Full System Backup):Copies everything, time-consuming and unnecessary here.

Option D (Online Data Backup):A method, not a type; could be any backup, but not specific.

“Incremental Backups minimize downtime by capturing only changes since the last backup, suitable for frequent, low-volume data updates” (Module: Data Backup and Recovery, Section: Backup Types).

Time Machine is a built-in backup feature of macOS that allows users to automatically back up their entire system, including applications, system files, and personal data, to an external drive or network location. It enables users to restore their Mac to a previous state, such as before a problematic update, by selecting a specific backup point. In this scenario, Jack needs to revert his MacBook to the previous OS version due to issues with the beta update. Time Machine is the appropriate tool because it provides a user-friendly way to restore the system to a prior working state.

Option A (Time Shift):This is not a recognized feature in macOS. It seems to be a fictional or misnamed option.

Option B (Image Recovery):While image recovery refers to restoring a system from a disk image, it’s not a specific macOS feature and is less user-friendly than Time Machine for this purpose.

Option C (Snapshots):Snapshots are point-in-time copies of data, but in macOS, they are part of Time Machine’s local backup system and not a standalone feature Jack would directly use to restore his OS.

While EDRP focuses on enterprise disaster recovery, it covers backup and restoration tools like Time Machine under personal system recovery concepts, emphasizing the importance of regular backups for system restoration.

Tier 6 in DR tier models (e.g., SHARE) provides automated recovery of data and applications with near-zero downtime and data loss, fitting Phil’s scenario.

Option A (Tier 4):Point-in-time copies, less automated.

Option B (Tier 7):Fully mirrored, zero loss, more than needed here.

Option D (Tier 2):Basic offsite backup, not automated.

“Tier 6 offers automated recovery of data and applications, minimizing manual intervention and downtime” (Module: Disaster Recovery Tiers, Section: Tier Definitions).

ISO/IEC 27005 is an information security risk management standard that requires identifying, assessing, and prioritizing risks (like George’s exercise) to develop a mitigation plan. It fits his prioritization of electrical surges.

Option A (ISO 27001):Broad security management, not risk-specific.

Option B (INCITS 483-2012):Virtualization security, not risk management.

Option C (ISO 27031):ICT continuity, narrower than 27005.

“ISO/IEC 27005 guides organizations in risk identification, assessment, and prioritization, forming the basis for security and DR planning” (Module: Risk Management, Section: Standards).

Bare Metal Recovery (BMR) restores a system from backups to a new, blank machine (no OS/software), automating the process to a prior state, as the IT team did.

Option B (System Restore):Windows feature, not full system recovery.

Option C (Mirroring):Real-time duplication, not recovery.

Option D (System Image):Similar, but less automated/full-system focus.

“Bare Metal Recovery automates full system restoration to new hardware from backups, ideal for rapid, accurate recovery” (Module: System Recovery, Section: Recovery Methods).

Restoration involves repairing a damaged site or establishing a new one to enable operations, focusing on infrastructure recovery.

Option B (Resumption):Refers to restarting operations, not site repair/setup.

Option C (Response):Immediate actions during a disaster, not post-disaster site work.

Option D (Business Continuity):A broader strategy, not specific to site restoration.

EDRP v3 defines restoration as rebuilding or replacing physical infrastructure post-disaster (Module: Disaster Recovery Planning).

Physical data loss occurs due to physical damage to storage media (e.g., James damaging the hard drive), making data unreadable, as described.

Option A (Logical):Software or file system issues, not physical damage.

Option B (Natural Disaster):Environmental events (e.g., flood), not accidental damage.

Option D (Data Corruption):Data alteration, not physical inaccessibility.

“Physical data loss results from hardware damage, such as a broken hard drive, rendering data inaccessible due to physical failure” (Module: Data Backup and Recovery, Section: Types of Data Loss).

Latency is the time delay between a request and the system’s response, directly matching the question’s description.

Option A (Reaction):Not a technical term for delay.

Option B (Durability):Refers to data persistence, not response time.

Option C (Nonrepudiation):Ensures actions can’t be denied, unrelated to delay.

“Latency measures the delay in system response to requests, a critical factor in assessing recovery and performance” (Module: System Resilience, Section: Performance Metrics).

Disk Imaging software creates a block-level copy of an entire disk or partition, capturing all data, including the OS and applications, for restoration. This fits Cameron’s need for a comprehensive server backup.

Option A (Cloud Backup):Typically file-based, not block-level imaging.

Option C (Visualization):Likely a typo for “Virtualization,” which isn’t backup software.

Option D (Bare-metal Restore):A recovery process, not the software creating the image.

EDRP v3 discusses disk imaging as a key backup method for complete system recovery (Module: Data Backup and Recovery).

Deduplication eliminates redundant data copies, reducing storage and bandwidth usage while minimizing data leak risks by centralizing control. It’s ideal for this scenario where multiple individual backups exist.

Option A (Data Erasure):Deletes data, not a solution for redundancy.

Option B (Data Remanence):Refers to residual data, not a fix here.

Option C (Failover):Switches to a backup system, unrelated to data management.

EDRP v3 highlights deduplication as a storage optimization technique to enhance efficiency and security (Module: Data Backup and Recovery).

A Storage Cluster ensures a consistent file system image across servers, enabling simultaneous read/write access to shared storage, as described.

Option A (High-Performance):Focuses on computation, not file consistency.

Option B (High-Availability):Ensures uptime, not shared file systems.

Option C (Failover):Switches to backups, not simultaneous access.

“Storage Clusters maintain a unified file system across nodes, supporting simultaneous access for data consistency and availability” (Module: Clustering Technologies, Section: Cluster Types).

Qualitative Risk Assessment evaluates risks based on subjective likelihood (e.g., “high,” “low”) and impact, without precise numerical values, fitting Seth’s high-level probability approach.

Option A (Quantitative):Uses numerical data (e.g., percentages), not applicable here.

Option C (Semi-Qualitative):A hybrid, but Seth’s method is fully qualitative.

Option D (Semi-Quantitative):Combines numbers with qualitative, not evident here.

“Qualitative Risk Assessment prioritizes risks using descriptive scales (e.g., high, low) for probability and impact, ideal for resource-constrained planning” (Module: Risk Management, Section: Assessment Types).

NFPA 1600 (National Fire Protection Association Standard on Disaster/Emergency Management and Business Continuity Programs) is a widely recognized standard that provides a comprehensiveframework 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).

Tier 4 in DR tier models (e.g., SHARE) uses point-in-time copies (e.g., snapshots) for recovery, balancing cost and data loss.

Option B (Tier 5):Adds remote replication, not just point-in-time.

Option C (Tier 0):No backup.

Option D (Tier 6):Near-zero data loss, beyond simple copies.

“Tier 4 employs point-in-time copies to provide reliable recovery with moderate RPO, suitable for many organizations” (Module: Disaster Recovery Tiers, Section: Tier Definitions).

PASIS (Pittsburgh Advanced Survivable Information Storage) integrates Decentralized Storage Systems, Data Redundancy and Encoding, and Dynamic Self-Maintenance for survivable storage, as Matt researched.

Option A:Centralized, not PASIS’s decentralized focus.

Option B:Distributed computing is broader than storage-specific.

Option D:Centralized, contradicts PASIS principles.

“PASIS architecture combines decentralized storage, redundancy with encoding, and self-maintenance for robust, survivable data systems” (Module: Survivable Storage Systems, Section: PASIS Components).

Snapshot Replication copies the entire dataset (or changes) at a specific point in time to a replica, ideal for infrequent updates like ABC Inc.’s annual database refresh. It’s simple and suits low-frequency synchronization.

Option A (Merge Replication):Combines changes from multiple sources, complex for this case.

Option B (Transactional Replication):Tracks incremental changes in real time, overkill here.

Option C (SQL Server Replication):A general category, not a specific method.

“Snapshot Replication provides a point-in-time copy of data, efficient for infrequent updates where full synchronization is needed annually” (Module: Data Replication, Section: Replication Types).

ISO/TS 22317 is a technical specification providing detailed guidance on conducting a formal Business Impact Analysis (BIA) process, aligning with Jane’s goal of establishing and maintaining a documented BIA.

Option A (ISO/IEC 27005):Focuses on information security risk management, not BIA-specific.

Option B (AS/NZS 5050):Australian/New Zealand standard for business continuity, less BIA-focused.

Option D (ISO/IEC 27031):ICT continuity, not BIA-specific.

“ISO/TS 22317 offers a structured approach to BIA, guiding organizations in formally documenting and maintaining the process for continuity planning” (Module: Business Impact Analysis, Section: Standards for BIA).

Colocation Facilities involve renting space and infrastructure (e.g., cooling, power) in a shared data center, offering a cost-effective backup site solution, as Jack chose.

Option A (Hot Sites):Fully operational, expensive, not cost-focused.

Option B (Cold Sites):Basic space, no pre-installed infrastructure like cooling.

Option C (Warm Sites):Partially equipped, more costly than colocation.

“Colocation Facilities provide cost-efficient backup by renting shared data center resources, including cooling and security, ideal for budget-conscious organizations” (Module: Alternate Sites, Section: Site Types).