Migrating Kubernetes with AMQP to AWS
Short answer
B Migrate the container application to Amazon EKS and use Amazon MQ to support the existing AMQP protocol with minimal overhead.
Question
Key Takeaways
This question tests the ability to match existing application protocols (AMQP) and orchestration (Kubernetes) to AWS managed services, trapping those who default to lower-overhead services that lack protocol support.
Migrating a Kubernetes application using AMQP to AWS requires selecting services that support the existing protocols and orchestration to minimize operational overhead. This page establishes that Amazon EKS and Amazon MQ are the correct choices for a seamless migration.
Common mistake: Choosing Amazon ECS with Amazon SQS (Option A) because ECS has less overhead than EKS, but failing to recognize that SQS does not support AMQP and would require application refactoring.
Expert Analysis
Why the Answer Is Correct
Option B correctly identifies Amazon EKS as the managed Kubernetes service that allows a seamless migration of existing Kubernetes workloads with minimal refactoring, and Amazon MQ as the managed message broker service that natively supports the AMQP protocol. By using these managed services, the company avoids the operational overhead of managing the underlying infrastructure for both the container orchestration and the message broker.
Why the Other Options Are Wrong
Option A is incorrect because Amazon SQS does not support the AMQP protocol; migrating to SQS would require significant code refactoring to change how the application communicates. Option C is incorrect because running the application on highly available Amazon EC2 instances introduces significantly more operational overhead than a managed Kubernetes service like Amazon EKS, as it requires managing the OS, instance scaling, and self-managing Kubernetes. Option D is incorrect because AWS Lambda requires significant application refactoring to adapt to an event-driven model, and like Option A, Amazon SQS does not support AMQP.
Community Comment Notes
Commenters highlighted the protocol trap, noting that "SQS do not implement AMQP" so Amazon MQ is required. As Mikado211 noted, while ECS has less overhead, the protocol requirement forces the use of Amazon MQ, and EKS is the natural fit for an existing Kubernetes cluster. Another commenter pointed out that "Amazon MQ is a managed message broker service" providing compatibility with protocols like AMQP.
Official Reference
https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/welcome.html
This link opens the official vendor documentation in a new tab.
Exam Strategy
When evaluating migration options with least operational overhead, always check for protocol or runtime dependencies first. If the application relies on a specific protocol like AMQP, you must select a service that supports it natively to avoid costly refactoring.
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 6 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 6
-
Mikado211 👍 13 Answered BThis question is a trap because A is definitely the answer for a Least overhead (ECS + SQS) and in a real life scenario could be good in 99% of cases. However SQS do not implement AMQP (SQS is only a simple queueing system very basic) so we have to use Amazon MQ. In terms of containers EKS will always be a better solution than a manual setup of Docker. Good solution would have been ECS+AmazonMQ not given here Lambda can work with containers, but since there are limitations like 15 minutes limit we can't really consider it as a good solution. So B is the least bad solution.
-
Scheldon 👍 1 Answered BAnswerB For me B is a correct solution. In question AMQP is mentioned and Amazon on his doc page about MQ is providing such information: "Amazon MQ is a managed message broker service that provides compatibility with many popular message brokers. We recommend Amazon MQ for migrating applications from existing message brokers that rely on compatibility with APIs such as JMS or protocols such as AMQP 0-9-1, AMQP 1.0, MQTT, OpenWire, and STOMP." I cannot be coincidence that documentation is mentioning about AMQP. https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/welcome.html
-
sandordini 👍 1 Answered AI'd go for A. Although the ideal solution and least modification would require B, with heavy rework the application can be (most likely) adopted to ECS+SQS. As it is an AWS exam, not a vendor-agnostic SA exam, A will be the correct answer.
-
Dantecito 👍 1 Answered BWe were asked for the LEAST operational overhead, so the company already has a managed message broker and thats why we use Amazon MQ and they are already using Kubernetes.
-
seetpt 👍 1 Answered BB because only solution with Kubernetes
Show 1 more comment
-
asdfcdsxdfc 👍 2 Answered BShould be B
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →