AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A financial services company is using AWS Elastic Disaster Recovery (DRS) to protect a critical on-premises VMware-based application. The replication to the DR region in AWS is healthy, and the company is preparing for its first non-disruptive disaster recovery drill. A solutions architect must configure the EC2 launch template that DRS will use to launch the recovery instances for this drill. The primary requirements for the drill are to validate the recovery process and data integrity without impacting the on-premises production environment and to minimize the costs associated with the drill. Which configuration should the architect implement in the EC2 launch template for the drill?
Configure the instances to launch into the production VPC but assign them to a new, isolated security group that denies all inbound and outbound traffic to production resources.
Configure the instances to launch with the same high-performance instance types and Provisioned IOPS SSD (io2) EBS volumes used in production to ensure an accurate performance baseline.
Configure a post-launch script in the launch template to immediately install and run the AWS DRS Failback Client on the recovery instances to prepare for the return to on-premises.
Configure the instances to launch into a dedicated, isolated VPC that mirrors the production network CIDR range. Specify a general-purpose instance type (e.g., T3) and General Purpose SSD (gp3) EBS volumes.
The correct approach for a non-disruptive disaster recovery drill is to launch the recovery instances into an isolated network environment to prevent any conflicts, such as IP address clashes, with the production systems. This is a crucial best practice. Additionally, since the goal is to validate the process and not to run a full performance test, using cost-effective, general-purpose resources like T3 or T4g instances and gp3 EBS volumes is the most appropriate choice to meet the requirement of minimizing costs. The EC2 launch template in AWS DRS is the mechanism used to define these parameters for drill and recovery instances.
Launching instances with production-equivalent specifications is unnecessarily expensive for a validation drill and goes against the cost-minimization requirement. Launching instances into the production VPC, even with different security groups, introduces a significant risk of IP address conflicts and unintended interaction with live production services. Finally, while the Failback Client is a component of DRS, its purpose is to prepare for replicating data back to the source site after a recovery event; it is not relevant to the initial failover validation drill.
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.
Why is it necessary to use an isolated VPC for the disaster recovery drill?
Open an interactive chat with Bash
What is the benefit of using general-purpose instance types and gp3 EBS volumes for the recovery drill?
Open an interactive chat with Bash
What role does the EC2 launch template play in AWS Elastic Disaster Recovery?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design Solutions for Organizational Complexity
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access