A company recently migrated a message processing system to AWS. The system receives messages into an ActiveMQ queue running on an Amazon EC2 instance. Messages are processed by a consumer application running on Amazon EC2. The consumer application processes the messages and writes results to a MySQL database running on Amazon EC2. The company wants this application to be highly available with low operational complexity.
Which architecture offers the HIGHEST availability?
To achieve the highest availability and low operational complexity, using Amazon MQ with active/standby brokers across two Availability Zones ensures the message queue remains available even if one zone fails. Adding an Auto Scaling group for the consumer EC2 instances across two Availability Zones provides redundancy and automatic management of instance health and scaling based on load, making it highly resilient to failures. Finally, using Amazon RDS for MySQL with Multi-AZ enabled ensures that the database will have automated failover and replication across Availability Zones, maintaining high availability without manual intervention. This architecture maximizes availability and minimizes operational complexity across all critical components.
Answer is D as the "HIGHEST available" and less "operational complex" The "Amazon RDS for MySQL with Multi-AZ enabled" option excludes A and B The "Auto Scaling group" is more available and reduces operational complexity in case of incidents (as remediation it is automated) than just adding one more instance. This excludes C. C and D to choose from based on D over C since is configured
Option D offers the highest availability because it addresses all potential points of failure in the system: Amazon MQ with active/standby brokers configured across two Availability Zones ensures that the message queue is available even if one Availability Zone experiences an outage. An Auto Scaling group for the consumer EC2 instances across two Availability Zones ensures that the consumer application is able to continue processing messages even if one Availability Zone experiences an outage. Amazon RDS for MySQL with Multi-AZ enabled ensures that the database is available even if one Availability Zone experiences an outage.
Option A addresses some potential points of failure, but it does not address the potential for the consumer application to become unavailable due to an Availability Zone outage. Option B addresses some potential points of failure, but it does not address the potential for the database to become unavailable due to an Availability Zone outage. Option C addresses some potential points of failure, but it does not address the potential for the consumer application to become unavailable due to an Availability Zone outage.
D: Managed and auto-scaling, resilient and HA service for each tier. This is well-architected too.
Using Amazon MQ with active/standby brokers provides highly available message queuing across AZs. Adding an Auto Scaling group for consumer EC2 instances across 2 AZs provides highly available processing. Using RDS MySQL with Multi-AZ provides a highly available database. This architecture provides high availability for all components of the system - queue, processing, and database.
Ans is C - C. Option C uses Amazon MQ with active/standby brokers, adds an additional consumer EC2 instance, and uses Amazon RDS for MySQL with Multi-AZ enabled. Amazon RDS Multi-AZ automatically replicates your database to another AZ and provides automated failover. This ensures high availability for both the messaging system and the database. Option D- bring More scalabilty rather HA
D automates replacement of failed instances, thus it has higher availability than C.
HIGHEST availability. Definitely option D.
The key reasons are: Amazon MQ active/standby brokers across AZs for queue high availability Auto Scaling group with consumer EC2 instances across AZs for redundant processing RDS MySQL with Multi-AZ for database high availability This combines the HA capabilities of MQ, EC2 and RDS to maximize fault tolerance across all components. The auto scaling also provides flexibility to scale processing capacity as needed.
D is the correct answer. Using Amazon MQ with active/standby brokers provides highly available message queuing across AZs. Adding an Auto Scaling group for consumer EC2 instances across 2 AZs provides highly available processing. Using RDS MySQL with Multi-AZ provides a highly available database. This architecture provides high availability for all components of the system - queue, processing, and database.
Keyword Amazon RDS, has C and D. Then D has "Auto Scaling group", choose D.
Amazon MQ with active/standby brokers configured across two AZ ensures high availability for the message broker. In case of a failure in one AZ, the other AZ's broker can take over seamlessly. Adding an ASG for the consumer EC2 instances across two AZ provides redundancy and automatic scaling based on demand. If one consumer instance becomes unavailable or if the message load increases, the ASG can automatically launch additional instances to handle the workload. Using RDS for MySQL with Multi-AZ enabled ensures high availability for the database. Multi-AZ automatically replicates the database to a standby instance in another AZ. If a failure occurs, RDS automatically fails over to the standby instance without manual intervention. This architecture combines high availability for the message broker (Amazon MQ), scalability and redundancy for the consumer EC2 instances (ASG), and high availability for the database (RDS Multi-AZ). It offers the highest availability with low operational complexity by leveraging managed services and automated failover mechanisms.
Definitely it's D
D With 3 options with Amazon MQ --> A is odd one out / Then ASG with M-AZ was an easy choice
Correct answer D
to achieve ha + low operational complexity, the solution architect has to choose option D, which fulfill these requirements.
Auto scaling and Multi-AZ enabled for high availability.
you can find some details about Amazon MQ active/standby broker for high availability https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/active-standby-broker-deployment.html
D as the Auto Scaling group offer the highest availability between all solutions