Which solution will provide DR with the LOWEST RTO?
Create an AWS Lambda function to check the availability of the Amazon Connect instance and to send a notification to the operations team in case of unavailability. Create an Amazon EventBridge rule to invoke the Lambda function every 5 minutes. After notification, instruct the operations team to use the AWS Management Console to provision a new Amazon Connect instance in a second Region. Deploy the contact flows, users, and claimed phone numbers by using an AWS CloudFormation template.
Provision a new Amazon Connect instance with all existing users in a second Region. Create an AWS Lambda function to check the availability of the Amazon Connect instance. Create an Amazon EventBridge rule to invoke the Lambda function every 5 minutes. In the event of an issue, configure the Lambda function to deploy an AWS CloudFormation template that provisions contact flows and claimed numbers in the second Region.
Provision a new Amazon Connect instance with all existing contact flows and claimed phone numbers in a second Region. Create an Amazon Route 53 health check for the URL of the Amazon Connect instance. Create an Amazon CloudWatch alarm for failed health checks. Create an AWS Lambda function to deploy an AWS CloudFormation template that provisions all users. Configure the alarm to invoke the Lambda function.
Provision a new Amazon Connect instance with all existing users and contact flows in a second Region. Create an Amazon Route 53 health check for the URL of the Amazon Connect instance. Create an Amazon CloudWatch alarm for failed health checks. Create an AWS Lambda function to deploy an AWS CloudFormation template that provisions claimed phone numbers. Configure the alarm to invoke the Lambda function.
Explanations:
This option has a high RTO due to manual intervention. It requires the operations team to provision a new Amazon Connect instance and deploy resources after receiving a notification, which would significantly delay the recovery process.
This option improves upon Option A by provisioning users in advance, but it still delays the DR process. The contact flows and claimed phone numbers are only deployed after an outage is detected, leading to a longer recovery time.
This option provisions contact flows and claimed phone numbers in advance, reducing the setup time in DR. However, it requires the deployment of all users upon an alarm trigger, which can take time and increase the RTO.
This option pre-deploys users and contact flows in the secondary Region, ensuring they are readily available. Only claimed phone numbers need to be provisioned upon failover, minimizing the setup time and providing the lowest RTO among the options.
I value that the answer is:
Provision a new Amazon Connect instance with all existing users and contact flows in a second Region. Create an Amazon Route 53 health check for the URL of the Amazon Connect instance. Create an Amazon CloudWatch alarm for failed health checks. Create an AWS Lambda function to deploy an AWS CloudFormation template that provisions claimed phone numbers. Configure the alarm to invoke the Lambda function.