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

Deja Dup is Ubuntu’s native backup and restore tool, allowing Sam to recover deleted files from a previous backup.

Option B (Checkpoints):Hyper-V term, not Ubuntu.

Option C (Shadow Copy):Windows feature, not Ubuntu.

Option D (Snapshots):General term, not Ubuntu-specific.

“Deja Dup, Ubuntu’s native backup utility, enables file recovery from prior backups, simplifying restoration on Linux systems” (Module: System Recovery, Section: OS-Specific Tools).

N-Tier Architecture combines client-server principles with multiple layers (e.g., presentation, application, data), enhancing scalability and flexibility.

Option B:Not a standard term.

Option C:Basic client-server, not layered.

Option D:Refers to dependency, not architecture type.

“N-Tier Architecture merges client-server with layered design, supporting robust, scalable systems for DR” (Module: Network Architectures, Section: Architecture Types).

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

Return on Risk Adjusted Capital (RORAC) is a financial metric often used to allocate funds for risk mitigation, including emergency reserves like James’ $20,000 for virtual connections. It reflects the return expected after accounting for risk costs.

Option A (RAROC):Similar, but typically broader, not specific to emergency funds.

Option B (RAPM):A management approach, not a fund term.

Option C (RARORAC):A variant, less commonly used in this context.

“RORAC quantifies funds set aside for risk scenarios, such as emergency recovery costs, ensuring financial preparedness aligns with risk exposure” (Module: Risk Management, Section: Financial Metrics).

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

Exit Criteria define the conditions for test completion, here 90% pass rate, indicating successful DR plan validation.

Option A (Entry Criteria):Conditions to start testing, not finish.

Option C (STLC):Broad testing process, not specific criteria.

Option D (Suspension):Conditions to pause testing, not success.

“Exit Criteria, such as a 90% pass rate, determine when DR testing is successfully completed, ensuring plan reliability” (Module: Testing Disaster Recovery Plans, Section: Test Criteria).

ISO 22301:2012 is the international standard for Business Continuity Management Systems (BCMS), specifying requirements for planning, implementing, and auditing a BCP to ensure it meets continuity objectives. An internal audit of a BCP would align with this standard.

Option B (ISO/IEC 27005:2011):Focuses on information security risk management, not BCP auditing.

Option C (ISO/IEC 27031:2011):Addresses ICT continuity, narrower than BCP.

Option D (ISO 22313):A guidance document for ISO 22301, not the auditable standard.

“ISO 22301:2012 defines the auditable framework for BCP, ensuring compliance and effectiveness through internal audits” (Module: Business Continuity Management, Section: Standards and Compliance).

Tier 5 in the disaster recovery tier model (e.g., SHARE or IBM models) typically involves backing up data over a Wide Area Network (WAN) to a remote site, providing offsite redundancy with minimal data loss.

Option B (Tier 3):Basic offsite backup, often tape-based, not WAN-specific.

Option C (Tier 0):No backup, not applicable.

Option D (Tier 6):Advanced, often with zero data loss, beyond simple WAN backup.

“Tier 5 utilizes WAN connections for remote data backups, enhancing resilience with offsite replication and moderate RPO” (Module: Disaster Recovery Tiers, Section: Tier Definitions).

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

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

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

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

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

Non-Authoritative Active Directory Restoration is used to restore a domain controller’s Active Directory database from a backup when other domain controllers in the domain are still operational. It allows the restored server to synchronize with the intact servers, updating its directory to the current state. Since Zane’s other servers have intact Active Directories, this method ensures consistency without overwriting domain-wide data.

Option A (Server Migration):Involves moving services to a new server, not restoring AD.

Option B (Data Replication):A general process, not specific to AD restoration.

Option C (Authoritative Restoration):Used when the restored AD data must override others, not applicable here.

“Non-Authoritative Active Directory Restoration recovers a domain controller by leveraging replication from other intact controllers, ensuring domain consistency without forcing changes” (Module: System Recovery, Section: Active Directory Recovery).

RAID 3 uses striping with a dedicated parity drive, meeting all requirements: parity for reconstruction, good speed (sequential access), and lower cost than RAID 10 or RAID 1 (fewer drives than RAID 10). Option C duplicates RAID 1, likely a typo.

Option A (RAID 10):Mirroring and striping, expensive, no parity drive.

Option B/C (RAID 1):Mirroring, no parity, costly for multiple drives.

Option D (RAID 3):Parity-based, cost-effective, meets all criteria.

“RAID 3 employs a dedicated parity drive for data reconstruction, offering good performance and cost-efficiency for backup solutions” (Module: Storage Technologies, Section: RAID Levels).

A Simulation Test mimics a specific disaster scenario to evaluate the BCP’s effectiveness, as Roger did.

Option B (Orientation):Introduces the plan, not scenario-based.

Option C (Checklist):Reviews steps, not a simulation.

Option D (Tabletop):Discussion-based, not a live simulation.

“Simulation Tests replicate disaster scenarios to assess BCP response, testing procedures in a controlled environment” (Module: Testing Disaster Recovery Plans, Section: Test Types).

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

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

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

Disaster Recovery Management refers to the processes, policies, and procedures an organization uses to restore systems, applications, and data to normal operating conditions after a disruptive event, within a prescribed and acceptable time frame.

Business Continuity Management (BCM)focuses on ensuring the overall continuation of business operations during and after a disruption, which includes but is not limited to IT recovery.

Risk Managementinvolves identifying, assessing, and mitigating risks but does not specifically address the restoration process.

Recovery Managementis a vague term and not a standard industry-specific term for this context.

A Storage Cluster uses mounted file systems to enable multiple servers to read and write data simultaneously to a shared storage pool, as described.

Option B (High-Performance):Focuses on computation, not file systems.

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

Option D (High-Availability):Ensures uptime, not necessarily mounted file systems.

“Storage Clusters utilize mounted file systems for concurrent read/write access, ensuring data consistency across nodes” (Module: Clustering Technologies, Section: Cluster Types).

A Functional Test mobilizes resources to test specific BCP components in a live setting, as Archie did.

Option B (Simulation):Mimics scenarios, not resource mobilization.

Option C (Checklist):Reviews steps, not active testing.

Option D (Orientation):Introduces plan, not resource-based.

“Functional Tests activate resources to validate BCP components, ensuring operational readiness” (Module: Testing Disaster Recovery Plans, Section: Test Types).

RMAN (Recovery Manager) is Oracle’s tool for backing up, restoring, and recovering database files using server sessions, matching Joanna’s description.

Option A (Virtuozzo):Virtualization platform, not database-specific.

Option B (Disk Drill):General data recovery, not database-focused.

Option C (Recuva):File recovery, not server-session-based.

“RMAN leverages database server sessions to manage backup, restoration, and recovery of Oracle databases efficiently” (Module: Database Recovery, Section: Recovery Tools).

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

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

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

ISO 27031 focuses on ICT readiness for business continuity, providing methods to enhance IT resilience, as Max and Carl discussed.

Option B (ISO 27005):Risk management, not ICT continuity-specific.

Option C (ISO 22313):General BCM guidance, not ICT-focused.

Option D (INCITS 483-2012):Virtualization security, not continuity.

“ISO 27031 outlines processes to improve ICT readiness, ensuring IT supports business continuity effectively” (Module: Standards and Compliance, Section: ICT Continuity).

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

High Availability (HA) ensures continuous operation by automatically switching to backup components (like virtual memory) during a failure, minimizing downtime, as in ABC Inc.’s case.

Option A (Deduplication):Removes redundant data, not a failover feature.

Option C (Fault Tolerance):Prevents failure impact but typically implies no interruption, not a switch.

Option D (Mirroring):Duplicates data, a component of HA, but not the full feature.

“High Availability maintains operations through automatic failover to backup resources, ensuring business continuity during component failures” (Module: System Resilience, Section: Availability Features).

Offsite Backup stores data at a separate location (e.g., home or bunker) to protect against site-specific disasters, as described.

Option A (Near-line):Intermediate storage, not offsite-specific.

Option B (Onsite):Local, vulnerable to site issues.

Option C (Online):Cloud-based, not necessarily physical offsite.

“Offsite Backup safeguards data at remote locations, from simple offices to secure bunkers, against site-specific disasters” (Module: Data Backup and Recovery, Section: Backup Locations).

Qualitative Risk Assessment uses descriptive scales (e.g., Very High to Very Low) based on subjective judgment and interaction, as Jonathan did.

Option A (Quantitative):Numeric values, not descriptive.

Option B (Semi-Quantitative):Combines numbers and descriptions, not purely qualitative.

Option C (Semi-Qualitative):Not a standard term, likely a typo.

“Qualitative Risk Assessment ranks risks using descriptive categories like ‘Very High’ to ‘Very Low’ based on observation and input” (Module: Risk Management, Section: Assessment 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).

A Disaster Management Plan identifies personnel for research, development, and implementation of disaster-related strategies, broader than just DR, as Jake did.

Option A (BCP):Focuses on continuity, not personnel identification alone.

Option C (IT Recovery):IT-specific, narrower scope.

Option D (DRP):Recovery-focused, not as broad as management.

“The Disaster Management Plan assigns personnel for research, development, and implementation, encompassing all disaster response aspects” (Module: Disaster Recovery Planning, Section: Management Plans).

Full Interruption Testing involves shutting down primary systems to test recovery processes, making it expensive (due to downtime costs) and disruptive to normal operations.

Option B (Simulation Testing):Mimics a disaster without stopping operations.

Option C (Parallel Testing):Runs recovery systems alongside primary ones, non-disruptive.

Option D (Checklist Testing):A review process, no operational impact.

“Full Interruption Testing, while thorough, incurs high costs and disrupts business by halting primary systems to validate recovery” (Module: Testing Disaster Recovery Plans, Section: Test Types).

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

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

Hardening secures systems (e.g., virtual machines) by disabling unnecessary components like interfaces, ports, and services, reducing attack surfaces.

Option A:Physical security, not VM-specific.

Option B (Defense-in-Depth):A layered strategy, not specific to disabling components.

Option C:Separates security functions, not about disabling.

“Hardening enhances VM security by disabling unused interfaces, ports, and services, minimizing vulnerabilities” (Module: Virtualization and Recovery, Section: Security Practices).

On-Premise Disk-Based Archiving uses local disk systems with tools for access and cataloging, incurring cooling and maintenance costs, as described.

Option A (Optical):Low cost, no cooling needs.

Option C (Legacy):Outdated systems, not specified here.

Option D (Cloud-Based):Offsite, minimal local maintenance costs.

“On-Premise Disk-Based Archiving offers accessible data cataloging with recurring costs for cooling and upkeep” (Module: Data Archiving, Section: Archiving Methods).

Recovery Time Objective (RTO) is the target time to restore a system (primary server) after a disruption, here four hours, to avoid exceeding the secondary server’s capacity.

Option A (WRT):Time to resume work post-recovery, not restoration time.

Option C (MTD):Maximum tolerable downtime, broader than RTO.

Option D (RPO):Data loss window, not recovery time.

“RTO defines the acceptable time to restore systems post-disaster, ensuring operations resume before secondary capacity is exceeded” (Module: Recovery Metrics, Section: RTO Definition).

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

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

Durability in PASIS (Pittsburgh Advanced Survivable Information Storage) ensures data remains recoverable despite node failures, using redundancy and encoding, enabling James to retrieve data post-earthquake.

Option B (Availability):Ensures access, not recovery after loss.

Option C (Reaction):Not a PASIS feature.

Option D (Integrity):Ensures data accuracy, not recovery.

“Durability in PASIS architecture guarantees data recovery from failed nodes through redundancy and encoding, enhancing survivability” (Module: Survivable Storage Systems, Section: PASIS Features).

Cost Benefit Analysis (CBA) compares the costs of an investment (e.g., food truck) with its expected financial benefits to determine profitability, matching Jill’s goal.

Option A (Risk Analysis):Focuses on risks, not profitability.

Option C (Cost Analysis):Examines costs only, not benefits.

Option D (BIA):Assesses disruption impacts, not investment feasibility.

“Cost Benefit Analysis evaluates the financial viability of projects by weighing costs against benefits, aiding investment decisions” (Module: Risk Management, Section: Financial Analysis).

Time scales for assessment are a critical BIA consideration, defining the period over which impacts are evaluated (e.g., hours, days).

Option A/B/D:Mitigation strategies, not BIA components.

“BIA requires defining time scales for assessing disruption impacts, ensuring accurate prioritization of processes” (Module: Business Impact Analysis, Section: BIA Methodology).

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