Disaster Recovery Professional (EDRP) Free Sample Questions

The most effective solution is to perform a P2V conversion. This decouples the legacy operating system and application from the specific underlying hardware. Once virtualized, the VM can be replicated to a warm site. This allows for rapid failover to dissimilar hardware, easily meeting the 4-hour RTO without the high cost of a full platform migration or a dedicated hot site. Migrating to a cloud-native platform is a major, expensive project, not a DR solution. A hot site would work but is very expensive. Improving logistics for the cold site doesn't solve the fundamental hardware dependency issue.

Source-side deduplication reduces the amount of data that needs to be sent over the WAN by eliminating redundant blocks before transmission. This directly addresses the goal of minimizing WAN traffic.

A centralized backup server allows for the consolidation and management of backups from all remote offices, meeting the requirement for efficient recovery at a central data center.

Before any technical failover procedures are initiated, a formal disaster declaration must be made by authorized executive management. This is a critical governance step that authorizes the significant resources, costs, and operational changes associated with activating the DR plan. The DR team lead does not typically have the authority to make this declaration independently. This step ensures the decision is made at the appropriate business level.

While the VM data is available (meeting the RPO), the inability to quickly and accurately restore the network environment will significantly delay the process of bringing services back online. Manually reconfiguring complex network settings under pressure is time-consuming and error-prone, which directly impacts and extends the recovery time, making it highly likely that the RTO will be missed. The RPO is related to data loss, which is handled by replication, whereas RTO is about the time to restore service.

False. According to ISO 22301, the BIA and risk assessment are related and sequential activities. The BIA is conducted first to identify critical business activities and their recovery timeframes (RTOs). The results of the BIA then inform the risk assessment, which focuses on identifying risks to these specific critical activities. The BIA determines 'what' is important, and the risk assessment determines 'what' can harm it.

A parallel test is the most appropriate choice. In this test, the recovery site is brought online and used to process transactions in parallel with the primary production site. This allows the organization to validate the full functionality of the recovery environment under a realistic workload for an extended period (a full business day) without impacting live production operations. This provides the robust evidence required by regulators. A full-interruption test is too risky, and tabletop/walk-through tests do not involve actual system activation.

A differential backup contains all changes made since the last full backup. Therefore, to restore a system that failed on Thursday, you need the last full backup (Sunday) and the most recent completed differential backup (Wednesday). The restore process involves restoring the Sunday full backup first, followed by the Wednesday differential backup. Thursday's backup would not have completed before the crash.

A Storage Area Network (SAN) is specifically designed to provide high-performance, low-latency, block-level storage access. It creates a dedicated network for storage traffic, typically using Fibre Channel or iSCSI. This architecture is ideal for demanding applications like large database clusters that require direct block-level access to disks for optimal performance and clustering capabilities. NAS provides file-level access, which is generally not suitable for this use case.

The Recovery Point Objective (RPO) defines the maximum amount of data, measured in time, that can be lost after a recovery from a disaster. It essentially answers the question, 'To what point in time can the business's data be recovered?' An RPO of 1 hour means that at most, 1 hour of data will be lost.

Hypervisor-based replication (like VMware vSphere Replication or third-party tools like Zerto/Veeam) is the ideal solution. It directly addresses the RPO requirement of 15 minutes through continuous or near-continuous data replication. It leverages the existing VMware environment and the Denver facility, meeting the constraint to use existing assets. This approach is generally more cost-effective than array-based replication and keeps the solution in-house, aligning with the limited budget and small team. It also allows for automated, non-disruptive testing, a key requirement. DRaaS is a viable option but doesn't leverage the existing Denver site. Array-based synchronous replication would be very expensive and may not be necessary to meet a 15-minute RPO.