What should a SysOps administrator do to meet this requirement?
Migrate the database from the EC2 instance to an Amazon RDS for MariaDB Multi-AZ DB instance. Run the application on EC2 instances that are in an Auto Scaling group that extends across multiple Availability Zones. Place the EC2 instances behind a load balancer.
Migrate the database from the EC2 instance to an Amazon RDS for MariaDB Multi-AZ DB instance. Use AWS Application Migration Service to convert the application into an AWS Lambda function. Specify the Multi-AZ option for the Lambda function.
Copy the database to a different EC2 instance in a different Availability Zone. Use AWS Backup to create Amazon Machine Images (AMIs) of the application EC2 instance and the database EC2 instance. Create an AWS Lambda function that performs health checks every minute. In case of failure, configure the Lambda function to launch a new EC2 instance from the AMIs that AWS Backup created.
Migrate the database to a different EC2 instance. Place the application EC2 instance in an Auto Scaling group that extends across multiple Availability Zones. Create an Amazon Machine Image (AMI) from the database EC2 instance. Use the AMI to launch a second database EC2 instance in a different Availability Zone. Put the second database EC2 instance in the stopped state. Use the second database EC2 instance as a standby.
Explanations:
Migrating the database to Amazon RDS for MariaDB Multi-AZ ensures high availability with automatic failover. Running the web application on EC2 instances in an Auto Scaling group across multiple Availability Zones, behind a load balancer, ensures that the application is highly available and can handle failures in one AZ.
While migrating the database to Amazon RDS for MariaDB Multi-AZ is correct, using AWS Application Migration Service to convert the application to a Lambda function is not feasible for a traditional web application that likely relies on persistent state and complex processing. Lambda would not be suitable for all workloads in this context.
Copying the database to a different EC2 instance and using AWS Backup with AMIs does not fully ensure high availability. The manual nature of using Lambda to check health and restart instances makes it a reactive solution, not a proactive, highly available system.
Migrating the database to another EC2 instance in a different Availability Zone and using AMIs for standby does not ensure high availability. This approach requires manual intervention for failover and does not offer automated failover or scaling, making it less reliable compared to other solutions.
I classify that the answer is:
Migrate the database from the EC2 instance to an Amazon RDS for MariaDB Multi-AZ DB instance. Run the application on EC2 instances that are in an Auto Scaling group that extends across multiple Availability Zones. Place the EC2 instances behind a load balancer.
I have a feeling that the answer is:
Migrate the database from the EC2 instance to an Amazon RDS for MariaDB Multi-AZ DB instance. Run the application on EC2 instances that are in an Auto Scaling group that extends across multiple Availability Zones. Place the EC2 instances behind a load balancer.