Multiple Choice
A company runs a production application workload in a single AWS account that uses Amazon Route 53, AWS Elastic Beanstalk, and Amazon RDS. In the event of a security incident, the Security team wants the application workload to fail over to a new AWS account. The Security team also wants to block all access to the original account immediately, with no access to any AWS resources in the original AWS account, during forensic analysis. What is the most cost-effective way to prepare to fail over to the second account prior to a security incident?
A) Migrate the Amazon Route 53 configuration to a dedicated AWS account. Mirror the Elastic Beanstalk configuration in a different account. Enable RDS Database Read Replicas in a different account.
B) Migrate the Amazon Route 53 configuration to a dedicated AWS account. Save/copy the Elastic Beanstalk configuration files in a different AWS account. Copy snapshots of the RDS Database to a different account.
C) Save/copy the Amazon Route 53 configurations for use in a different AWS account after an incident. Save/copy Elastic Beanstalk configuration files to a different account. Enable the RDS database read replica in a different account.
D) Save/copy the Amazon Route 53 configurations for use in a different AWS account after an incident. Mirror the configuration of Elastic Beanstalk in a different account. Copy snapshots of the RDS database to a different account.
Correct Answer:

Verified
Correct Answer:
Verified
Q600: An application runs on Amazon EC2 instances
Q601: What needs to be done in order
Q602: What is the expected behavior if Ansible
Q603: Customers have recently been complaining that your
Q604: You manage a three-tier web application consisting
Q605: When thinking of AWS Elastic Beanstalk's model,
Q606: A user is creating a new EBS
Q607: You are designing a service that aggregates
Q608: A Development team is working on a
Q610: You run a SIP-based telephony application that