Q43 — AWS SAA-C03 Ch.12

Question 43 of 100 | ← Chapter 12

Q843. A company runs a container application on a Kubernetes cluster in the company's data center. The application uses Advanced Message Queuing Protocol (AMQP) to communicate with a message queue. The data center cannot scale fast enough to meet the company's expanding business needs. The company wants to migrate the workloads to AWS.Which solution will meet these requirements with the LEAST operational overhead?

Correct Answer: B. Migrate the container application to Amazon Elastic Kubernetes Service (Amazon EKS). Use Amazon MQ to retrieve the messages.

Explanation

To meet the requirement of migrating a container application using AMQP to AWS with the least operational overhead, the recommended solution is:B. Migrate the container application to Amazon Elastic Kubernetes Service (Amazon EKS). Use Amazon MQ to retrieve the messages.Here's why:Option B suggests migrating the container application to Amazon Elastic Kubernetes Service (Amazon EKS) and using Amazon MQ to retrieve the messages. This solution leverages managed services provided by AWS, minimizing operational overhead.By migrating the container application to Amazon EKS, you can easily deploy and manage containers using Kubernetes. Amazon EKS takes care of the underlying infrastructure, including the control plane, making it a low-maintenance option.Amazon MQ is a managed message broker service that supports multiple messaging protocols, including AMQP. By using Amazon MQ, you can seamlessly integrate the container application with the message queue, ensuring reliable and scalable message communication.This solution provides the benefits of both managed container orchestration (Amazon EKS) and a managed message broker (Amazon MQ). It reduces the operational overhead associated with managing the underlying infrastructure and the message queue, allowing you to focus more on application development and business needs.Option A suggests migrating the container application to Amazon Elastic Container Service (Amazon ECS) and using Amazon Simple Queue Service (Amazon SQS) to retrieve messages. While this option provides managed container orchestration and a managed message queue, it may introduce additional operational complexity compared to using Amazon EKS and Amazon MQ.Option C suggests using highly available Amazon EC2 instances to run the application and Amazon MQ to retrieve messages. This option requires manual management of EC2 instances, including provisioning, scaling, and ensuring high availability, which can result in higher operational overhead.Option D suggests using AWS Lambda functions to run the application and Amazon SQS to retrieve messages. While Lambda provides serverless compute, it may not be the most suitable option for long-running containerized applications. Additionally, managing the application logic within Lambda functions may introduce operational challenges compared to using container orchestration platforms like Amazon EKS.Therefore, the recommended solution is to migrate the container application to Amazon EKS and use Amazon MQ to retrieve messages. This solution leverages managed services and provides a balance between operational simplicity and scalability for the containerized application using AMQP.