Which architecture offers the HIGHEST availability?
Add a second ActiveMQ server to another Availability Zone. Add an additional consumer EC2 instance in another Availability Zone. Replicate the MySQL database to another Availability Zone.
Use Amazon MQ with active/standby brokers configured across two Availability Zones. Add an additional consumer EC2 instance in another Availability Zone. Replicate the MySQL database to another Availability Zone.
Use Amazon MQ with active/standby brokers configured across two Availability Zones. Add an additional consumer EC2 instance in another Availability Zone. Use Amazon RDS for MySQL with Multi-AZ enabled.
Use Amazon MQ with active/standby brokers configured across two Availability Zones. Add an Auto Scaling group for the consumer EC2 instances across two Availability Zones. Use Amazon RDS for MySQL with Multi-AZ enabled.
Explanations:
While adding a second ActiveMQ server and an additional consumer EC2 instance in another Availability Zone increases availability, it does not eliminate the operational complexity associated with managing multiple ActiveMQ servers and handling failover. Additionally, the MySQL database replication does not provide the same level of high availability as the Multi-AZ feature of Amazon RDS.
This option improves availability by using Amazon MQ with active/standby brokers and adding a second consumer EC2 instance. However, it still lacks the fully managed and highly available database solution provided by Amazon RDS with Multi-AZ. The complexity of managing the database is still higher than using RDS.
This option incorporates Amazon MQ with active/standby brokers and an additional consumer EC2 instance. It also utilizes Amazon RDS for MySQL with Multi-AZ enabled, which significantly increases database availability. However, it does not include an Auto Scaling group for the consumer EC2 instances, which limits scalability and availability under load.
This option provides the highest availability. Using Amazon MQ with active/standby brokers ensures message durability and failover capabilities. The Auto Scaling group for consumer EC2 instances ensures that the application can handle varying loads and automatically scales across Availability Zones, while Amazon RDS with Multi-AZ ensures that the database is highly available and fault-tolerant. This architecture minimizes operational complexity while maximizing availability.
I compute that the answer is:
Use Amazon MQ with active/standby brokers configured across two Availability Zones. Add an Auto Scaling group for the consumer EC2 instances across two Availability Zones. Use Amazon RDS for MySQL with Multi-AZ enabled.