SOA-C02 practice question 10 of 10

[Security and Compliance] A company recently deployed an application in production. The production environment currently runs on a single Amazon EC2 instance that hosts the application's web application and a MariaDB database. Company policy states that all IT production environments must be highly available. What should a SysOps administrator do to meet this requirement?

Full set: 557 questions
Answer options
A: Migrale 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. Correct answer
B: 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.
C: 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.
D: 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.
Correct Answer:
A. Migrale 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.
Explanation

Designing a highly available (HA) architecture requires eliminating single points of failure across all architectural tiers. To achieve this, the administrator must decouple the database and web tiers that currently reside on a single instance. Migrating the MariaDB database to Amazon Relational Database Service (RDS) utilizing a Multi-AZ deployment ensures synchronous data replication and automatic failover functionality across disparate Availability Zones, providing robust database HA. Concurrently, the web application tier must be deployed onto Amazon EC2 instances managed by an Auto Scaling group configured to span multiple Availability Zones. Distributing web traffic via an Elastic Load Balancer across these varied EC2 instances guarantees that no single localized failure will compromise application availability, thereby comprehensively fulfilling the production high-availability mandate.

Why Incorrect

B: AWS Application Migration Service performs block-level replication to lift-and-shift servers directly to EC2; it cannot automatically refactor or convert legacy applications into native AWS Lambda functions. C: Utilizing scheduled Lambda functions to restore databases from snapshots introduces significant recovery time objectives (RTO) delays, classifying it as disaster recovery, not high availability. D: Maintaining a standby database instance in a stopped state provides cold disaster recovery rather than high availability, as it lacks synchronous data replication and automated, instantaneous failover capabilities.

References

AWS Whitepapers. "Reliability Pillar - AWS Well-Architected Framework." Section: Design principles (Failure management and highly available architecture).

AWS Documentation. "High availability (Multi-AZ) for Amazon RDS." Amazon RDS User Guide, Section: Multi-AZ deployments.

Scroll to Top