312-76 ECCouncil EC-Council Disaster Recovery Professional v3 (EDRP) Free Practice Exam Questions (2025 Updated)

“Resume” refers to restarting or recommencing business operations post-disaster as systems become available, aligning with business continuity goals.

Option A (Return):Too vague, not a specific DR term.

Option C (Reduce):Unrelated to restarting operations.

Option D (Recover):Focuses on data/system restoration, not operational resumption.

EDRP v3 uses “resume” to describe the phase of restoring business functions after recovery (Module: Business Continuity Management).

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

Recovery Point Objective (RPO) measures the data loss window, here 13 hours from the last backup (8:00 pm) to the disaster (9:00 am), not recovery time (8 hours). The ‘minus 13 hours’ phrasing is misleading; RPO is the correct term for potential data loss.

Option A (RTO):Time to restore (8 hours), not data loss.

Option B (MAO):Maximum downtime tolerance, not data-specific.

Option D (SPOF):A failure point, unrelated to time.

“RPO defines the time between the last backup and a disaster, indicating potential data loss, critical for planning” (Module: Recovery Metrics, Section: RPO Definition).

The Data Protection Continuum is a conceptual framework (often depicted graphically) that illustrates various data protection tools and services, balancing their costs against recovery time objectives (RTO). It helps organizations choose appropriate strategies, from basic backups to advanced replication, based on cost and recovery speed.

Option A (3DR):Likely a typo or unrelated term; not a standard concept.

Option B (Continuous Data Protection):A specific technology, not a broad representation.

Option D (Data Backup):A general process, not a graphical framework.

“The Data Protection Continuum provides a visual model to evaluate data protection options, aligning tools like snapshots, CDP, and replication with cost and RTO requirements, aiding strategic decision-making” (Module: Data Protection Strategies, Section: Protection Frameworks).

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

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

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

Risk Assessment evaluates risk factors and their interrelationships to understand potential threats, as described.

Option A (Risk Models):Tools for assessment, not the process.

Option B (Risk Management):Broader process including assessment.

Option C (Risk Mitigation):Reducing risks, not assessing them.

“Risk Assessment analyzes risk factors and their relationships to identify and prioritize threats for DR planning” (Module: Risk Management, Section: Assessment Definition).

Qualitative Impact assesses non-measurable effects, such as morale, productivity, and reputation, which align with the scenario’s focus on slowed progress and team morale.

Option A (Semi-Qualitative):A hybrid term, less precise here.

Option C (Quantitative):Measurable losses (e.g., financial), not the primary focus.

Option D (Industrial):Too broad, not specific to impact type.

“Qualitative Impact evaluates intangible consequences like morale and operational delays following a breach, critical for BIA” (Module: Business Impact Analysis, Section: Impact Types).

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

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

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

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

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

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

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

A centralized governance structure for Business Continuity and Risk Management typically includes Programs and Practices (strategies and processes), Enablement (resources and support), and Effectiveness (measuring outcomes). Authenticity, while important in security, is not a standard governance component.

Option A:Core to defining continuity practices.

Option B:Ensures implementation support.

Option C:Evaluates governance success.

“Centralized governance includes Programs and Practices, Enablement, and Effectiveness to ensure robust continuity; Authenticity is not a structural component” (Module: Governance Structures, Section: BC Governance).

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

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