312-76 Sample Questions & Answers

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.

Risk mitigation (or risk reduction) involves taking action to reduce the likelihood or impact of a risk. By installing a UPS and a generator, the organization is actively reducing the impact of a power grid failure. They are not avoiding the risk (which would mean moving the data center) or simply accepting it. While they are transferring some risk (e.g., to the fuel supplier), the primary action of installing power backup is mitigation.

The RTO is a direct output of the BIA and dictates the maximum time allowed for restoring a business process, which is a primary driver for selecting a DR strategy (e.g., hot site vs. cold site).

The RPO, also determined during the BIA, defines the acceptable amount of data loss and directly influences the choice of data replication and backup technologies (e.g., synchronous replication vs. nightly backups).

The BIA's core purpose is to identify which business functions are most critical and map their dependencies on IT systems, personnel, and other resources. This prioritization is essential for designing an effective and efficient DR plan.

The 3-2-1 rule stipulates: having at least THREE copies of your data, storing the copies on TWO different media types, and keeping ONE of these copies offsite. This option perfectly matches the rule: 1. Production data (copy 1), 2. Local disk backup (copy 2), 3. Offsite tape backup (copy 3). It uses two different media (production disk, backup disk, and tape). And one copy (tape) is offsite.

This issue is a classic failure of integrating the business continuity plan with the organization's change management process. Any significant change to production systems, such as a major software upgrade, should automatically trigger a review and potential update of the DR plan and associated recovery configurations. Without this link, the DR plan quickly becomes outdated and unreliable.

True. A core function of the BIA is to move beyond a purely technology-focused view and understand the business context. It identifies the most critical business processes and then maps the IT systems, applications, data, and other assets that are essential for those processes to function. This mapping is what allows the organization to prioritize recovery efforts based on business impact.