EC-Council Intermediate

312-76

EDRP - EC-Council Disaster Recovery Professional

The EC-Council Disaster Recovery Professional (EDRP) validates expertise in business continuity planning (BCP) and disaster recovery (DR) strategies. This certification covers the entire DR lifecycle from risk assessment and business impact analysis through recovery strategy development, plan implementation, testing, and maintenance. EDRP prepares professionals to ensure organizational resilience and minimize downtime during disruptive events.

The exam covers five domains: Business Continuity and Disaster Recovery Concepts (BCP/DR fundamentals, regulatory requirements, industry standards), Risk Assessment and Management (threat identification, vulnerability assessment, business impact analysis, risk mitigation), Recovery Strategies and Planning (recovery objectives, RTO/RPO, recovery strategies, plan development), Disaster Recovery Implementation (backup solutions, data replication, site recovery, cloud DR), and Testing and Maintenance (DR testing methodologies, plan maintenance, training programs, continuous improvement).

This certification is ideal for disaster recovery managers, business continuity planners, IT managers, risk managers, security managers, and professionals responsible for ensuring business continuity and disaster recovery. EDRP provides comprehensive knowledge of DR planning, backup and recovery technologies, crisis management, and DR testing methodologies aligned with industry best practices and standards such as ISO 22301 and NFPA 1600.

Updated Feb 2022 Cybersecurity

150

Questions

Practice Tests

70%

Pass Score

Views

Total Attempts

Avg. Score

Pass Rate

Discussions

Practice Tests Flash Cards Exam Topics Cheat Sheet

€5.00

EDRP Practice Exam 1

Comprehensive 50-question practice exam covering business continuity and disaster recovery concepts, risk assessment and management, recovery strategies and planning, disaster recovery implementation, and testing and maintenance for the EC-Council Disaster Recovery Professional certification.

50 Q 90 minutes 70%

Test Drive

€5.00

EDRP Practice Exam 2

50 Q 90 minutes 70%

Test Drive

€5.00

EDRP Practice Exam 3

50 Q 90 minutes 70%

Test Drive

€5.00

EDRP Practice Exam 4

50 Q 90 minutes 70%

Test Drive

€5.00

EDRP Practice Exam 5

50 Q 90 minutes 70%

Test Drive

€5.00

EDRP Practice Exam 6

50 Q 90 minutes 70%

Test Drive

Unlock All Content for 312-76

6 Practice Test(s) + Flash Cards — 3 months access

€39.99 €26.99 Save 30%

or included with Monthly subscription / Content Bundle

312-76 Cheat Sheet

Quick reference guide - 6 sections

Free Access

EDRP 312-76 Exam Details

Detail	Value
Exam Code	312-76 EDRP
Full Name	EC-Council Disaster Recovery Professional
Duration	120 minutes (2 hours)
Number of Questions	50 multiple-choice questions
Passing Score	70%
Exam Format	Multiple choice
Testing Center	ECC Exam / Pearson VUE
Certification Body	EC-Council

Exam Domain Breakdown

Domain	Focus Areas
Business Continuity & Disaster Recovery Concepts	BC/DR lifecycle, standards, risk management
Business Continuity Planning	BIA, risk assessment, BC plan development
Disaster Recovery Planning	DR strategies, DR sites, recovery procedures
Data Backup & Recovery	Backup methods, storage, cloud backup, database recovery
Virtualization & Cloud DR	VM replication, DRaaS, hybrid DR, network DR

About EDRP Certification

The EC-Council Disaster Recovery Professional (EDRP) certification is a vendor-neutral credential that validates a professional's ability to plan, strategize, implement, and maintain business continuity and disaster recovery plans. EDRP focuses on practical methodologies for identifying vulnerabilities and taking countermeasures against both natural and man-made disasters. The certification covers the full BC/DR lifecycle including business impact analysis, risk assessment, recovery strategy development, plan implementation, and testing.

EDRP is ideal for IT professionals involved in business continuity, disaster recovery, risk management, and system administration. It complements other EC-Council certifications like CEH and ECSA by adding organizational resilience capabilities. There are no mandatory prerequisites, but experience in IT administration and familiarity with networking concepts is recommended.

Tip: Focus on understanding the relationships between RTO, RPO, MTPD, and MTBF. These metrics are tested heavily and form the foundation for DR strategy selection.

Business Impact Analysis (BIA)

BIA is the foundation of any BC/DR program. It identifies critical business functions, quantifies the impact of disruptions, and determines recovery priorities. BIA drives all subsequent planning decisions.

BIA Component	Description
Critical Business Functions	Identify processes essential to organizational survival and rank by priority
Impact Assessment	Financial loss, reputational damage, legal/regulatory penalties, operational impact
Resource Dependencies	IT systems, personnel, facilities, suppliers, utilities, and communications
Recovery Time Objectives	Maximum acceptable downtime for each critical function (RTO)
Recovery Point Objectives	Maximum tolerable data loss measured in time (RPO)
Maximum Tolerable Period of Disruption	MTPD - Absolute maximum downtime before irreversible damage occurs

Tip: BIA must be completed before selecting recovery strategies. RTO and RPO values from the BIA directly determine the type of DR site and backup frequency required.

Risk Assessment Process

Step	Activity	Output
1. Asset Identification	Inventory all IT and physical assets	Asset register with valuations
2. Threat Identification	Identify natural and man-made threats	Threat catalog (earthquakes, floods, cyberattacks, power outages)
3. Vulnerability Assessment	Identify weaknesses that threats can exploit	Vulnerability report
4. Risk Analysis	Calculate risk = Threat x Vulnerability x Impact	Risk matrix / heat map
5. Risk Treatment	Mitigate, transfer, accept, or avoid risk	Risk treatment plan

Quantitative Analysis: Uses numerical values. ALE = SLE x ARO (Annualized Loss Expectancy = Single Loss Expectancy x Annual Rate of Occurrence)
Qualitative Analysis: Uses descriptive categories (High/Medium/Low) based on expert judgment and interviews
SLE Formula: SLE = Asset Value (AV) x Exposure Factor (EF). Example: Server worth $100,000 with 40% EF = $40,000 SLE
ALE Formula: ALE = SLE x ARO. If the threat occurs twice per year: $40,000 x 2 = $80,000 ALE

Business Continuity Planning Lifecycle

Phase	Activities
1. Project Initiation	Secure management support, define scope, assign BC team, establish budget
2. Risk Assessment	Identify threats, assess vulnerabilities, analyze risk, determine treatment
3. Business Impact Analysis	Identify critical functions, determine RTO/RPO/MTPD, assess dependencies
4. Strategy Development	Select recovery strategies, identify resources, determine DR site type
5. Plan Development	Document procedures, assign roles, create communication plans
6. Testing & Exercises	Validate plans through walkthroughs, simulations, and full-interruption tests
7. Maintenance & Review	Update plans regularly, incorporate lessons learned, audit compliance

Tip: Management support is the single most critical success factor for any BC/DR program. Without executive sponsorship, the program will lack funding, authority, and organizational buy-in.

BC/DR Standards & Frameworks

Standard	Focus	Key Points
ISO 22301	Business Continuity Management Systems	International standard for BCMS; Plan-Do-Check-Act (PDCA) cycle; certifiable
ISO 27031	ICT Readiness for Business Continuity	Guidelines for ICT readiness as part of BCMS; IRBC framework
NIST SP 800-34	Contingency Planning Guide	IT contingency planning for US federal systems; 7-step process
NIST SP 800-53	Security & Privacy Controls	CP (Contingency Planning) control family for federal information systems
BS 25999 (legacy)	Business Continuity Management	Predecessor to ISO 22301; British Standard now superseded
COBIT	IT Governance Framework	Includes BC/DR within IT governance objectives; DSS04 process domain

BC Team Roles & Responsibilities

BC Coordinator / Manager: Overall responsibility for BC/DR program; reports to senior management; coordinates all planning and testing activities
Crisis Management Team: Senior decision-makers who activate the BC plan and manage strategic response during an incident
Emergency Response Team: First responders handling immediate physical safety (evacuation, fire suppression, first aid)
Damage Assessment Team: Evaluates the extent of damage to facilities, systems, and infrastructure after an incident
IT Recovery Team: Responsible for restoring IT systems, applications, data, and network infrastructure
Communications Team: Manages internal/external communications, media relations, and stakeholder notifications
Business Recovery Team: Ensures business operations resume at the alternate site or through manual workarounds

Key Recovery Metrics

Metric	Full Name	Definition	Example
RTO	Recovery Time Objective	Maximum acceptable time to restore a system after disruption	Email server RTO = 4 hours
RPO	Recovery Point Objective	Maximum tolerable data loss measured in time before the disruption	Database RPO = 1 hour (max 1 hour of data loss)
MTPD	Maximum Tolerable Period of Disruption	Absolute maximum downtime before irreversible business impact	Payment system MTPD = 24 hours
MTBF	Mean Time Between Failures	Average operational time between system failures (reliability measure)	Server MTBF = 25,000 hours
MTTR	Mean Time To Repair	Average time needed to repair a failed component and restore service	Switch MTTR = 2 hours
WRT	Work Recovery Time	Time to verify system integrity and catch up on lost work after restoration	WRT = 2 hours (data validation)

Tip: RTO + WRT must be less than or equal to MTPD. If MTPD = 24 hours and WRT = 4 hours, then RTO cannot exceed 20 hours. MTBF / (MTBF + MTTR) = System Availability.

RTO vs RPO Visual Timeline

Understanding the relationship between RPO and RTO on a disaster timeline:

Timeline Position	Metric	Direction	Determines
Before Disaster	RPO	Looks backward from disaster	Backup frequency & replication method
After Disaster	RTO	Looks forward from disaster	DR site type & recovery procedures
After Recovery	WRT	Follows RTO	Verification, validation, data catch-up
Absolute Limit	MTPD	Overall constraint	RTO + WRT ≤ MTPD

DR Site Types Comparison

Feature	Hot Site	Warm Site	Cold Site
Hardware	Fully equipped, identical to production	Partially equipped, some hardware	Empty facility, basic infrastructure only
Data	Real-time or near-real-time replication	Periodic data backups (hours/days old)	No data on-site, must restore from backups
Activation Time	Minutes to hours	Hours to days	Days to weeks
Cost	Highest ($$$$)	Moderate ($$$)	Lowest ($$)
Best For	Mission-critical systems, near-zero RTO	Important systems, RTO of hours	Non-critical systems, RTO of days/weeks
Network	Active connectivity, ready to use	Connectivity available, needs configuration	No network pre-configured
Staff	May have on-site staff	Staff dispatched upon activation	Staff dispatched, longer setup required

Tip: Additional DR site types include Mirror Site (exact duplicate with automatic failover, most expensive), Mobile Site (transportable trailers with equipment), and Reciprocal Agreement (mutual aid between organizations, least reliable).

DR Plan Development Components

Plan Objectives & Scope: Define systems, facilities, and processes covered; set recovery priorities based on BIA
Roles & Responsibilities: DR coordinator, recovery teams, escalation matrix, contact lists (primary and alternate)
Notification Procedures: Incident declaration criteria, call tree/cascade, internal and external communication protocols
Recovery Procedures: Step-by-step technical instructions for restoring each system in priority order
Alternate Site Procedures: Activation checklist, travel logistics, equipment setup, network configuration at DR site
Return-to-Normal: Criteria for returning to primary site, data synchronization, reverse migration procedures
Appendices: Vendor contacts, SLAs, network diagrams, system configurations, software licenses, insurance details

DR Plan Testing Types

Test Type	Description	Disruption	Cost
Checklist / Desk Check	Distribute plan to team members for review and feedback	None	Lowest
Tabletop / Walkthrough	Team members walk through plan steps in a meeting, discuss scenarios	None	Low
Simulation	Practice responding to a simulated disaster scenario with role-playing	Minimal	Moderate
Parallel Test	Activate DR site and run systems in parallel with production (production stays live)	Low	High
Full-Interruption Test	Shut down primary site completely, operate entirely from DR site	High	Highest

Tip: Start with low-disruption tests (checklist, tabletop) and progressively move to higher-disruption tests. Full-interruption tests provide the most realistic validation but carry the highest risk. Testing should occur at least annually.

DR Strategy Selection Matrix

RTO Requirement	RPO Requirement	Recommended Strategy
Near-zero (minutes)	Near-zero	Hot site / Mirror site + synchronous replication
1-8 hours	1-4 hours	Hot site + asynchronous replication / frequent backups
8-24 hours	4-24 hours	Warm site + daily backups + off-site storage
1-7 days	24 hours	Warm/Cold site + daily tape/disk backup rotation
1+ weeks	24+ hours	Cold site + weekly off-site backups

Backup Types Comparison

Backup Type	What It Backs Up	Speed	Restore Time	Storage	Archive Bit
Full	All selected data	Slowest	Fastest (single restore)	Most storage	Clears (resets)
Incremental	Only data changed since last backup (any type)	Fastest	Slowest (full + all incrementals)	Least storage	Clears (resets)
Differential	All data changed since last full backup	Moderate (grows daily)	Moderate (full + latest differential)	Moderate	Does NOT clear
Mirror	Exact copy with no compression/encryption	Fast	Fast (direct copy)	Equal to source	Clears (resets)
Synthetic Full	Constructs a full backup from existing full + incrementals	Fast (no source access needed)	Fastest	Most storage	N/A

Tip: The key difference between incremental and differential is the archive bit behavior. Incremental clears the bit (backs up changes since ANY last backup), while differential does NOT clear the bit (always backs up changes since the last FULL backup). This directly affects restore complexity.

Backup Rotation Schemes

Scheme	Description	Media Sets
Grandfather-Father-Son (GFS)	Daily (son), weekly (father), monthly (grandfather) rotation. Most common scheme. Son tapes overwritten weekly, father tapes overwritten monthly, grandfather tapes kept for a year or longer.	~20 tapes minimum
Tower of Hanoi	Mathematical rotation pattern using multiple media sets with varying frequencies. Set A used every other day, Set B every 4th day, Set C every 8th day. More complex but uses fewer media.	5 sets typically
Round Robin	Simple sequential rotation: each tape used in order, then cycle repeats. Simplest scheme but limited retention window.	Varies (5-14 typical)

3-2-1 Backup Rule

3 copies: Maintain at least 3 copies of your data (1 primary + 2 backups)
2 different media types: Store backups on at least 2 different storage media (e.g., disk + tape, SSD + cloud)
1 off-site copy: Keep at least 1 backup copy in a geographically separate location (off-site vault, cloud)

The extended 3-2-1-1-0 rule adds: 1 copy that is air-gapped or immutable (protection against ransomware), and 0 errors (verified through regular restore testing).

Tip: The 3-2-1 rule is a best practice minimum. For mission-critical data, consider the 3-2-1-1-0 extension. Always verify backups through periodic test restores - an untested backup is not a backup.

RAID Levels Comparison

RAID Level	Method	Min Disks	Fault Tolerance	Usable Capacity	Performance
RAID 0	Striping (no redundancy)	2	None - any disk failure = total loss	100% (N disks)	Best read/write
RAID 1	Mirroring	2	1 disk failure	50% (N/2)	Good read, normal write
RAID 5	Striping + distributed parity	3	1 disk failure	(N-1) disks	Good read, slower write (parity calc)
RAID 6	Striping + double distributed parity	4	2 disk failures	(N-2) disks	Good read, slowest write
RAID 10	Mirroring + striping (1+0)	4	1 disk per mirrored pair	50% (N/2)	Best for databases

Tip: RAID is NOT a backup solution - it provides fault tolerance against disk failure only. You still need proper backups for protection against data corruption, ransomware, accidental deletion, and site-level disasters.

Storage Technologies

Technology	Description	DR Use Case
SAN (Storage Area Network)	Block-level storage via Fibre Channel or iSCSI; high performance	Primary storage, synchronous replication between sites
NAS (Network Attached Storage)	File-level storage via NFS/SMB/CIFS; shared access	File-level backups, user data, unstructured data
Tape (LTO)	Sequential access, high capacity, low cost per GB	Long-term archival, off-site vault storage, air-gapped backup
Cloud Storage	Object/block/file storage via cloud providers	Off-site backup, DRaaS, geographic redundancy
Deduplication Appliance	Eliminates duplicate data blocks to reduce storage	Reduce backup storage footprint by 10-50x

Database Recovery Techniques

Transaction Log Shipping: Periodically copy and restore transaction logs to a standby server. RPO depends on shipping interval (typically 15-60 minutes). Standby database is in restoring state.
Database Mirroring: Real-time transaction log forwarding to a mirror server. Synchronous mode = zero data loss (higher latency); Asynchronous mode = minimal data loss (better performance).
Replication: Publish/subscribe model to distribute data changes. Snapshot replication (periodic full copy), Transactional replication (real-time changes), Merge replication (bidirectional).
Point-in-Time Recovery: Restore database to a specific timestamp using full backup + transaction logs. Essential for recovering from accidental data corruption or deletion.
Clustering (Always On): Failover clusters with shared storage or Always On Availability Groups for automatic failover. Provides both HA and DR capabilities.
Export/Import (Dump): Logical backup using database dump utilities. Portable across platforms but slower for large databases. Best for small to medium databases.

Replication Types

Feature	Synchronous Replication	Asynchronous Replication
Data Loss (RPO)	Zero data loss (RPO = 0)	Minimal data loss (RPO > 0, seconds to minutes)
Write Confirmed	Only after data written to both sites	After written to primary only
Performance Impact	Higher latency (waits for remote acknowledgment)	Minimal impact on primary performance
Distance Limitation	Limited (~100-200 km due to latency)	Unlimited (any distance)
Cost	Higher (requires low-latency links)	Lower (standard bandwidth sufficient)
Best For	Financial systems, transaction databases	Cross-region DR, long-distance replication

VM-Based Disaster Recovery

DR Method	Description	RTO	RPO
VM Replication	Continuously replicate VM changes to a secondary host/site	Minutes	Seconds to minutes
VM Snapshots	Point-in-time capture of VM state (memory, disk, config)	Minutes	Time since last snapshot
VM Backup & Restore	Full VM image backup to off-site storage, restore when needed	Hours	Time since last backup
Live Migration (vMotion)	Move running VM between hosts with zero downtime	Near-zero	Zero (VM stays live)
VM Failover Clusters	Automatic restart of failed VMs on healthy hosts in the cluster	Minutes	Zero (shared storage)

Tip: VM snapshots are NOT backups. Snapshots grow over time and can degrade performance. They are best used for short-term rollback (e.g., before patching). Always use dedicated backup solutions for VM protection.

Cloud-Based DR (DRaaS)

Disaster Recovery as a Service (DRaaS) leverages cloud infrastructure to provide DR capabilities without maintaining a dedicated physical DR site. The cloud provider hosts replicated copies of production systems that can be activated during a disaster.

DRaaS Model	Description	Best For
Self-Service DRaaS	Customer manages DR planning, replication, and failover using provider tools	Organizations with skilled IT staff, cost-conscious
Assisted DRaaS	Provider offers tools and expert guidance; customer manages day-to-day	Mid-size organizations wanting expert support
Managed DRaaS	Provider fully manages DR including planning, testing, and failover execution	Organizations without dedicated DR staff

Advantages: Pay-as-you-go pricing, no capital expenditure for DR hardware, geographic diversity, scalable resources, faster deployment
Challenges: Bandwidth dependency for replication, data sovereignty/compliance concerns, vendor lock-in, ongoing costs, shared responsibility model

Hybrid DR Architecture

Hybrid DR combines on-premises infrastructure with cloud resources to create a flexible and cost-effective DR solution. Critical systems may failover to a local hot site while less critical workloads recover in the cloud.

Component	On-Premises	Cloud
Tier 1 (Mission Critical)	Local hot site, synchronous replication	Secondary failover if on-prem DR also fails
Tier 2 (Important)	Local backup, asynchronous replication	Primary DR site, cloud-based recovery
Tier 3 (Non-Critical)	Local backup only	Cloud backup storage, cold recovery

Network DR Strategies

Redundant WAN Links: Multiple ISP connections with automatic failover (MPLS + Internet, dual carriers). Use BGP or OSPF for dynamic routing failover.
DNS Failover: Update DNS records to redirect traffic to DR site. Global Server Load Balancing (GSLB) automates DNS-based failover across sites.
SD-WAN: Software-defined WAN enables application-aware routing and automatic failover across multiple transport links (MPLS, broadband, LTE).
VPN Re-establishment: Pre-configure VPN tunnels to DR site. Maintain current IPsec/SSL VPN configurations for rapid connectivity restoration.
Network Configuration Backup: Regularly backup switch/router/firewall configurations. Use configuration management tools (Ansible, RANCID) for automated backup and rapid restore.
IP Address Management: Plan IP addressing for DR site in advance. Use NAT or IP address re-mapping for seamless application connectivity after failover.

System Recovery Procedures

Phase	Activities	Key Considerations
1. Assessment	Evaluate damage, determine systems affected, declare disaster	Use pre-defined criteria for disaster declaration
2. Activation	Notify teams, activate DR site, begin recovery procedures	Follow notification call tree, activate in priority order
3. Recovery	Restore systems from backups/replicas, validate functionality	Restore in BIA priority order, verify data integrity
4. Operations	Run production workloads from DR site, monitor performance	Ensure adequate capacity, update DNS/routing
5. Return-to-Normal	Rebuild primary site, sync data back, plan failback	Failback is as complex as failover - test thoroughly
6. Post-Incident Review	Document lessons learned, update DR plan, improve processes	Conduct within 2 weeks while details are fresh

Business Continuity vs Disaster Recovery

Aspect	Business Continuity (BC)	Disaster Recovery (DR)
Scope	Entire organization (people, processes, technology)	IT systems and data recovery
Focus	Maintaining business operations during disruption	Restoring IT infrastructure after a disaster
Timeframe	Before, during, and after an incident	Primarily after an incident occurs
Includes	DR + crisis management + manual workarounds + communications	System restore, data recovery, site failover
Relationship	DR is a subset of BC	DR is a component within the broader BC plan

High Availability vs Disaster Recovery

Aspect	High Availability (HA)	Disaster Recovery (DR)
Purpose	Minimize downtime from routine failures	Recover from major disasters
Scope	Component-level redundancy (same site)	Site-level recovery (different location)
Failure Type	Hardware failure, software crash, network issue	Natural disaster, fire, flood, cyberattack
Failover	Automatic (seconds/minutes)	Manual or semi-automatic (minutes to hours/days)
Examples	Clustering, load balancing, RAID, redundant PSU	DR sites, backup restoration, DRaaS

RTO vs RPO Quick Reference

Aspect	RTO (Recovery Time Objective)	RPO (Recovery Point Objective)
Measures	Maximum acceptable downtime	Maximum acceptable data loss
Direction	Forward from disaster (how long to recover)	Backward from disaster (how much data can be lost)
Drives	DR site type, recovery procedures, staffing	Backup frequency, replication method
Zero Value	Requires hot/mirror site with instant failover	Requires synchronous replication
Cost Impact	Lower RTO = higher cost (faster recovery needed)	Lower RPO = higher cost (more frequent backups/replication)

Backup Strategy Comparison

Strategy	Monday (Full)	Tue-Fri Backup	Friday Restore Needs	Total Media
Full Daily	Full	Full each day	Friday full only (1 tape)	5 full backups
Full + Incremental	Full	Incremental each day	Monday full + Tue-Fri incrementals (5 tapes)	1 full + 4 incremental
Full + Differential	Full	Differential each day	Monday full + Friday differential (2 tapes)	1 full + 4 differential

Tip: Incremental = fastest backup, slowest restore. Differential = moderate backup speed, moderate restore speed. Full + Differential is the most common enterprise strategy, balancing backup window with recovery time.

DR Site Cost vs Recovery Speed

Site Type	Setup Cost	Ongoing Cost	Recovery Speed	Data Currency
Mirror Site	Very High	Very High	Instant (automatic failover)	Real-time (synchronous)
Hot Site	High	High	Minutes to hours	Near-real-time
Warm Site	Moderate	Moderate	Hours to days	Hours to days old
Cold Site	Low	Low	Days to weeks	Last off-site backup
Cloud (DRaaS)	Low	Variable (pay-per-use)	Minutes to hours	Depends on replication config
Mobile Site	Moderate	Low	Hours to days	Last backup transported
Reciprocal Agreement	Very Low	Very Low	Days to weeks	Last off-site backup

Testing Methods: Effort vs Value

Test Type	Effort	Realism	Risk	Finds Issues
Checklist	Very Low	Very Low	None	Documentation gaps only
Tabletop	Low	Low	None	Process gaps, role confusion
Simulation	Moderate	Moderate	Minimal	Decision-making issues, communication gaps
Parallel	High	High	Low	Technical recovery issues, timing problems
Full-Interruption	Very High	Very High	High	All issues including real failover problems

Tip: For the EDRP exam, remember that parallel testing is the highest-fidelity test that does NOT disrupt production. Full-interruption testing provides the most accurate results but carries actual business risk. Organizations should use a combination of all test types throughout the year.

312-76

EDRP - EC-Council Disaster Recovery Professional

EDRP Practice Exam 1

EDRP Practice Exam 2

EDRP Practice Exam 3

EDRP Practice Exam 4

EDRP Practice Exam 5

EDRP Practice Exam 6

Unlock All Content for 312-76

Preview (10 / 120)

Flash Cards

Available Languages

Exam Topics

312-76 Cheat Sheet

EDRP 312-76 Exam Details

Exam Domain Breakdown

About EDRP Certification

Business Impact Analysis (BIA)

Risk Assessment Process

Business Continuity Planning Lifecycle

BC/DR Standards & Frameworks

BC Team Roles & Responsibilities

Key Recovery Metrics

RTO vs RPO Visual Timeline

DR Site Types Comparison

DR Plan Development Components

DR Plan Testing Types

DR Strategy Selection Matrix

Backup Types Comparison

Backup Rotation Schemes

3-2-1 Backup Rule

RAID Levels Comparison

Storage Technologies

Database Recovery Techniques

Replication Types

VM-Based Disaster Recovery

Cloud-Based DR (DRaaS)

Hybrid DR Architecture

Network DR Strategies

System Recovery Procedures

Business Continuity vs Disaster Recovery

High Availability vs Disaster Recovery

RTO vs RPO Quick Reference

Backup Strategy Comparison

DR Site Cost vs Recovery Speed

Testing Methods: Effort vs Value