Amazon SAA-C03 Exam - Topic 3 Question 33 Discussion

Actual exam question for Amazon's SAA-C03 exam

Question #: 33
Topic #: 3

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

AMigrate the container application to Amazon Elastic Container Service (Amazon ECS) Use Amazon Simple Queue Service (Amazon SQS) to retrieve the messages.

BMigrate the container application to Amazon Elastic Kubernetes Service (Amazon EKS) Use Amazon MQ to retrieve the messages.

CUse highly available Amazon EC2 instances to run the application Use Amazon MQ to retrieve the messages.

DUse AWS Lambda functions to run the application Use Amazon Simple Queue Service (Amazon SQS) to retrieve the messages.

Show Suggested 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

by Nettie at Apr 25, 2024, 04:20 AM

Limited Time Offer

25%

Off

Get Premium SAA-C03 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Alease

3 months ago

ECS could work too, but EKS feels more aligned with the current setup.

upvoted 0 times

...

Laurena

3 months ago

Surprised that EC2 is even an option here, feels outdated!

upvoted 0 times

...

Aretha

3 months ago

Not sure about using Amazon SQS, it might not handle AMQP well.

upvoted 0 times

...

Leigha

4 months ago

I agree, EKS with Amazon MQ is a solid choice!

upvoted 0 times

...

Tora

4 months ago

Option B seems like the best fit for Kubernetes users.

upvoted 0 times

...

Anastacia

4 months ago

AWS Lambda sounds appealing for low overhead, but I can't recall if it can handle the same message queue functionality as AMQP.

upvoted 0 times

...

Chanel

4 months ago

I practiced a similar question where EC2 instances were mentioned, but I feel like that option adds too much management complexity.

upvoted 0 times

...

Maddie

4 months ago

I think using EKS with Amazon MQ makes sense since it supports AMQP, but it might have more overhead than ECS.

upvoted 0 times

...

Ula

5 months ago

I remember that ECS is simpler to manage than EKS, but I'm not sure if SQS can fully replace AMQP.

upvoted 0 times

...

Ling

5 months ago

I feel pretty confident about this one. Migrating the container app to ECS and using SQS for the message queue seems like the simplest and most operationally efficient solution. The question is specifically asking for the "LEAST operational overhead", so that's the approach I'm leaning towards.

upvoted 0 times

...

Louis

5 months ago

Okay, let's see. They want to minimize operational overhead, so I'm thinking managed services like ECS, EKS, or Lambda would be the way to go. And for the message queue, SQS or Amazon MQ seem like the logical choices. I'll have to weigh the pros and cons of each.

upvoted 0 times

...

Shaquana

5 months ago

Hmm, I'm a bit unsure about this one. Migrating a container app and message queue to AWS seems tricky. I'll need to carefully consider the options and think through the operational overhead for each.

upvoted 0 times

...

Helga

5 months ago

This looks like a straightforward cloud migration question. I think I can handle this one - the key is to identify the AWS services that best match the requirements.

upvoted 0 times

...

Angelo

5 months ago

This is a tough one. There are a lot of moving parts with the container app, Kubernetes, and the message queue. I'm not sure I fully understand all the requirements and tradeoffs between the different AWS services. I may need to spend some extra time reviewing this before answering.

upvoted 0 times

...

Mendy

5 months ago

Okay, I think I understand the steps here. First, I'll need to reconfigure the API server to use the Node and RBAC authorization modes, as well as the NodeRestriction admission controller. Then I'll need to remove the ClusterRoleBinding for the anonymous user.

upvoted 0 times

...

Izetta

5 months ago

I'm a bit confused by the options. Let me re-read the question and think through the tradeoffs of each approach.

upvoted 0 times

...

Chantell

5 months ago

I'm leaning towards MP-BGP or BGP as the answer here. Those seem like the most likely protocols for exchanging VPRN routes between PE devices.

upvoted 0 times

...

Evangelina

2 years ago

What about using AWS Lambda functions instead? Wouldn't that simplify things even further?

upvoted 0 times

...

Shantay

2 years ago

I agree with User1, ECS with SQS seems like the least operational overhead solution.

upvoted 0 times

...

Felice

2 years 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 years 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

2 years ago

I agree. Migrating to ECS and using SQS seems like the most efficient choice.

upvoted 0 times

...

Hannah

2 years ago

That sounds like a good option. It would definitely reduce the operational overhead.

upvoted 0 times

...

Art

2 years 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

2 years ago

I agree, Lambda functions could also help with scaling the application.

upvoted 0 times

...

Daisy

2 years 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

2 years ago

Using Amazon ECS and SQS might be simpler in this case.

upvoted 0 times

...

Zachary

2 years ago

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

upvoted 0 times

...

Ashleigh

2 years ago

That sounds like a good option for reducing operational overhead.

upvoted 0 times

...

Denise

2 years 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

...