SAA-C03 Design High-Performing Architectures Practice Question
A team wants to run containerized services with AWS-managed orchestration and autoscaling. They do NOT require Kubernetes compatibility. Which AWS service choice is most appropriate to meet these goals?
⚠ Common exam trap
Many candidates confuse Amazon ECS with Amazon EKS, assuming that Kubernetes compatibility is required for container orchestration, but ECS provides a simpler, AWS-native alternative without Kubernetes overhead.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Amazon ECS
Amazon ECS is the most appropriate choice because it provides AWS-managed container orchestration and autoscaling without requiring Kubernetes compatibility. ECS integrates natively with AWS services like Application Auto Scaling and CloudWatch to automatically scale container tasks based on metrics such as CPU or memory utilization, meeting the team's requirements directly.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Amazon EKS
Why it's wrong here
Amazon EKS is Kubernetes-based. Even though it is AWS-managed, it still requires a Kubernetes control plane and Kubernetes-specific operational concepts (for example, deployments, services, and Kubernetes APIs). This is unnecessary when Kubernetes compatibility is explicitly not required.
- ✓
Amazon ECS
Why this is correct
Amazon ECS is a native container orchestration service. You can run containers without Kubernetes, and ECS integrates with AWS-native autoscaling (for example, ECS Service Auto Scaling with targets such as CPU/memory or request-based metrics when applicable to the architecture).
- ✗
An EC2 Auto Scaling group only
Why it's wrong here
An EC2 Auto Scaling group can scale compute instances, but it does not orchestrate containers (it does not schedule, place, or manage container tasks). You would still need an orchestration/control layer (such as ECS/EKS or a custom solution).
- ✗
Amazon SQS as the compute layer
Why it's wrong here
Amazon SQS is a fully managed message queuing service designed for decoupling application components; it does not provide compute capacity or container orchestration. It cannot schedule, place, or run container tasks, nor can it maintain a desired task count or manage runtime health checks. To actually run containers, you need a compute service like ECS, EKS, or EC2, and SQS is typically used as a buffer or event source for those workers, not as a compute layer itself.
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 935-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.