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

Walkthrough Testing involves team members reviewing the DR plan in a structured discussion to confirm effectiveness, identify bottlenecks, and uncover weaknesses, as Joan did.

Option B (Full Interruption):Live shutdown test, not discussion-based.

Option C (Parallel):Runs recovery alongside primary, not weakness-focused.

Option D (Simulation):Mimics disasters, not confirmation-based.

“Walkthrough Testing engages team members to validate DR plan effectiveness and pinpoint weaknesses through detailed review” (Module: Testing Disaster Recovery Plans, Section: Test Types).

A Business Recovery Plan outlines actions for all phases—before, during, and after—a catastrophic event to ensure organizational recovery, matching Fred’s intent.

Option B (Risk Assessment):Identifies risks, not a phased action plan.

Option C (IT Disaster Recovery Plan):IT-focused, narrower than business-wide.

Option D (Data Backup Plan):Data-specific, not comprehensive.

“The Business Recovery Plan details proactive and reactive actions across pre-, during-, and post-catastrophe phases for holistic recovery” (Module: Business Continuity Planning, Section: Recovery Plans).

A Storage Area Network (SAN) is a dedicated high-speed network that separates storage devices from servers and user networks, providing centralized block-level storage access.

Option A (NAS):Network Attached Storage uses the user network, not a dedicated one.

Option B (SCSI):Small Computer System Interface, a protocol, not a network (likely a typo for SAS).

Option D (SAS):Serial Attached SCSI, a drive interface, not a network.

“SANs provide a dedicated storage network, isolating storage from server and user traffic for efficiency and security” (Module: Storage Technologies, Section: SAN Overview).

The Planning Team is tasked with developing, implementing, and executing the disaster recovery plan, including testing, to ensure preparedness and effectiveness.

Option A (Operations Team):Focuses on daily operations, not DR planning.

Option B (Support Team):Provides technical assistance, not plan execution.

Option D (Technology Team):Manages IT systems, not the DR plan itself.

“The Planning Team oversees the creation, implementation, and testing of the DR plan, ensuring alignment with organizational goals” (Module: Disaster Recovery Teams, Section: Roles and Responsibilities).

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

PASIS (Pittsburgh Advanced Survivable Information Storage) architecture balances availability, durability, and confidentiality. Increasing availability (easier data access) often reduces confidentiality (data protection) due to trade-offs in access control and encryption strength.

Option A (Nonrepudiation):Unrelated to availability trade-offs.

Option B (Durability):Remains high in PASIS, not decreased.

Option D (Latency):May decrease with higher availability, not increase.

EDRP v3 discusses PASIS trade-offs, noting confidentiality decreases as availability rises to ensure survivability (Module: Survivable Storage Systems).

A Threat is any circumstance or event with the potential to disrupt operations or degrade assets, as described.

Option A (Impact):Result of a threat, not the cause.

Option B (Vulnerability):Weakness exploited by threats.

Option C (Hazard):Natural danger, narrower than “threat.”

“A Threat is any potential event that can disrupt operations or assets, requiring identification for effective DR planning” (Module: Risk Management, Section: Threat Definitions).

Server Clustering connects multiple servers into a unified resource, improving scalability and protecting against failures, as Jack implemented.

Option A (Mirroring):Data duplication, not scalability-focused.

Option B (Deduplication):Storage optimization, not clustering.

Option C (Failover):Backup switching, not unified resource.

“Server Clustering unifies computing resources, enhancing scalability and resilience against application and site failures” (Module: Clustering Technologies, Section: Clustering Benefits).

Recovery Service Scalability (RSS) measures a recovery solution’s capacity to handle multiple applications or data sets and the maximum data size it can manage, reflecting its scalability.

Option B (RLS):Refers to the geographic scope of recovery, not capacity.

Option C (RPO):Measures data loss tolerance, not scalability.

Option D (RSR):Focuses on resilience, not size or number of applications.

EDRP v3 defines RSS as a metric for evaluating recovery solution scalability, critical for large-scale environments (Module: Recovery Metrics).