Which solution will meet these requirements?
Launch two EC2 instances, each in a different Availability Zone in the same AWS Region. Install the database on both EC2 instances. Configure the EC2 instances as a cluster. Set up database replication.
Launch an EC2 instance in an Availability Zone. Install the database on the EC2 instance. Use an Amazon Machine Image (AMI) to back up the data. Use AWS CloudFormation to automate provisioning of the EC2 instance if a disruptive event occurs.
Launch two EC2 instances, each in a different AWS Region. Install the database on both EC2 instances. Set up database replication. Fail over the database to a second Region.
Launch an EC2 instance in an Availability Zone. Install the database on the EC2 instance. Use an Amazon Machine Image (AMI) to back up the data. Use EC2 automatic recovery to recover the instance if a disruptive event occurs.
Explanations:
This option provides high availability by deploying two EC2 instances in different Availability Zones, allowing for automatic failover through clustering and database replication. This setup ensures minimal downtime during a disruptive event.
This option does not provide high availability, as it only uses a single EC2 instance. Relying solely on an AMI for backup and CloudFormation for provisioning does not ensure automatic failover or availability during an outage.
While using two EC2 instances in different AWS Regions can provide redundancy, it does not allow for automatic failover within the same Region and adds complexity due to inter-region latency and management. Automatic failover typically needs to occur within the same Region for critical applications.
This option relies on a single EC2 instance, which does not ensure high availability. While EC2 automatic recovery can help in certain failure scenarios, it does not provide the level of redundancy or failover capabilities needed for a critical application.