Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam SAA-C03 Topic 3 Question 33 Discussion

Actual exam question for Amazon's SAA-C03 exam
Question #: 33
Topic #: 3
[All SAA-C03 Questions]

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? \

Show Suggested Answer Hide Answer
Suggested Answer: B

This option is the best solution because it allows the company to migrate the container application to AWS with minimal changes and leverage a managed service to run the Kubernetes cluster and the message queue. By using Amazon EKS, the company can run the container application on a fully managed Kubernetes control plane that is compatible with the existing Kubernetes tools and plugins. Amazon EKS handles the provisioning, scaling, patching, and security of the Kubernetes cluster, reducing the operational overhead and complexity. By using Amazon MQ, the company can use a fully managed message broker service that supports AMQP and other popular messaging protocols. Amazon MQ handles the administration, maintenance, and scaling of the message broker, ensuring high availability, durability, and security of the messages.

A) Migrate the container application to Amazon Elastic Container Service (Amazon ECS) Use Amazon Simple Queue Service (Amazon SQS) to retrieve the messages. This option is not optimal because it requires the company to change the container orchestration platform from Kubernetes to ECS, which can introduce additional complexity and risk. Moreover, it requires the company to change the messaging protocol from AMQP to SQS, which can also affect the application logic and performance. Amazon ECS and Amazon SQS are both fully managed services that simplify the deployment and management of containers and messages, but they may not be compatible with the existing application architecture and requirements.

C) Use highly available Amazon EC2 instances to run the application Use Amazon MQ to retrieve the messages. This option is not ideal because it requires the company to manage the EC2 instances that host the container application. The company would need to provision, configure, scale, patch, and monitor the EC2 instances, which can increase the operational overhead and infrastructure costs. Moreover, the company would need to install and maintain the Kubernetes software on the EC2 instances, which can also add complexity and risk. Amazon MQ is a fully managed message broker service that supports AMQP and other popular messaging protocols, but it cannot compensate for the lack of a managed Kubernetes service.

D) Use AWS Lambda functions to run the application Use Amazon Simple Queue Service (Amazon SQS) to retrieve the messages. This option is not feasible because AWS Lambda does not support running container applications directly. Lambda functions are executed in a sandboxed environment that is isolated from other functions and resources. To run container applications on Lambda, the company would need to use a custom runtime or a wrapper library that emulates the container API, which can introduce additional complexity and overhead. Moreover, Lambda functions have limitations in terms of available CPU, memory, and runtime, which may not suit the application needs. Amazon SQS is a fully managed message queue service that supports asynchronous communication, but it does not support AMQP or other messaging protocols.


1Amazon Elastic Kubernetes Service - Amazon Web Services

2Amazon MQ - Amazon Web Services

3Amazon Elastic Container Service - Amazon Web Services

4AWS Lambda FAQs - Amazon Web Services

Contribute your Thoughts:

Felice
1 days ago
But wouldn't using Amazon Elastic Kubernetes Service (Amazon EKS) with Amazon MQ be a better option for scalability?
upvoted 0 times
...
Isabelle
2 days ago
I think we should migrate the container application to Amazon Elastic Container Service (Amazon ECS) and use Amazon Simple Queue Service (Amazon SQS) to retrieve the messages.
upvoted 0 times
...
Arminda
15 days ago
I agree. Migrating to ECS and using SQS seems like the most efficient choice.
upvoted 0 times
...
Hannah
16 days ago
That sounds like a good option. It would definitely reduce the operational overhead.
upvoted 0 times
...
Art
17 days ago
I think the best solution would be to migrate the container application to Amazon Elastic Container Service (Amazon ECS) and use Amazon Simple Queue Service (Amazon SQS) to retrieve the messages.
upvoted 0 times
Nohemi
7 days ago
I agree, Lambda functions could also help with scaling the application.
upvoted 0 times
...
Daisy
8 days ago
D) Use AWS Lambda functions to run the application Use Amazon Simple Queue Service (Amazon SQS) to retrieve the messages.
upvoted 0 times
...
Maile
9 days ago
Using Amazon ECS and SQS might be simpler in this case.
upvoted 0 times
...
Zachary
10 days ago
B) Migrate the container application to Amazon Elastic Kubernetes Service (Amazon EKS) Use Amazon MQ to retrieve the messages.
upvoted 0 times
...
Ashleigh
11 days ago
That sounds like a good option for reducing operational overhead.
upvoted 0 times
...
Denise
12 days ago
A) Migrate the container application to Amazon Elastic Container Service (Amazon ECS) Use Amazon Simple Queue Service (Amazon SQS) to retrieve the messages.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77