A systems administrator must validate the organization's disaster-recovery plan by running a simulated failover of several virtual machines that continuously replicate to a warm site. Management requires that production workloads keep running, replication remain active, and no duplicate IP addresses appear on the corporate network during the test. Which action is required to meet these objectives?
Modify internal DNS and default-gateway records so users resolve services at the DR site.
Start the replica VMs on an isolated test network segment that is not routable to production.
Pause the replication job, then attach the replicas to the production VLAN at the DR site.
Shut down the primary VMs before powering on their replicas at the warm site.
A simulated (test) failover boots duplicate virtual machines at the recovery site so staff can verify that operating systems and applications start correctly. To avoid service disruption or IP conflicts with the still-running production VMs, the replicas must be connected to an isolated, non-routable network segment. Pausing replication is unnecessary and would defeat the goal of continuing protection, shutting down the primary VMs turns the exercise into a live failover, and updating DNS redirects users away from the primary site-both actions management explicitly forbids.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a simulated failover in disaster recovery testing?
Open an interactive chat with Bash
What is a 'non-routable network segment,' and why is it used during a simulated failover?
Open an interactive chat with Bash
Why is pausing replication or shutting down primary VMs not appropriate during a simulated failover?