Question 947 of 988
AWS Fargate: Run Containers Without Managing EC2 Instances
A company runs a containerized application that uses multiple Docker containers. The development team wants to run these containers on AWS without provisioning or managing any EC2 instances. They also do not want to manage the container orchestration control plane. The application requires consistent access to persistent storage volumes that can be attached to containers. Which AWS service should the team use to run the containers with the least operational overhead?
Quick Answer
The answer is AWS Fargate. This is the correct choice because Fargate is a serverless compute engine for containers that lets you run Docker containers without provisioning or managing any EC2 instances, and it also eliminates the need to manage the container orchestration control plane, as Fargate handles both Amazon ECS and Amazon EKS cluster management for you. For the persistent storage requirement, Fargate tasks can attach Amazon EFS file systems or Docker volumes, ensuring consistent access to storage volumes without additional infrastructure overhead. On the AWS Certified Cloud Practitioner CLF-C02 exam, this question tests your understanding of serverless container compute without managing instances, often appearing as a direct comparison to Amazon ECS on EC2 or Amazon EKS with managed node groups. A common trap is choosing Amazon ECS or EKS alone, but remember that the key phrase “without managing the orchestration control plane” points directly to Fargate. Memory tip: think “Fargate = Forget about instances and the control plane.”
⚠ Common exam trap
Candidates often confuse AWS Fargate with Amazon ECS or EKS, thinking they must choose a managed orchestration service that still requires EC2 management, but Fargate eliminates both instance and control plane management.
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
✓
AWS Fargate
AWS Fargate is a serverless compute engine for containers that allows you to run containers without provisioning or managing EC2 instances or the underlying container orchestration control plane (Amazon EKS or Amazon ECS). It directly meets the requirement of zero infrastructure management while supporting persistent storage through Amazon EFS filesystems or Docker volumes that can be attached to Fargate tasks, providing consistent access to storage volumes.
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 EC2 with a container-optimized AMI
Why it's wrong here
This option still requires the team to provision, manage, and patch EC2 instances, and manage the container orchestration control plane (e.g., installing Docker, managing cluster state). This does not meet the requirement of zero server management.
When this WOULD be correct
This option would be correct if the question required running containers on AWS with full control over the underlying EC2 instances, such as for compliance or performance tuning, and the team was willing to manage the instances and orchestration control plane.
- ✗
AWS Lambda
Why it's wrong here
AWS Lambda is a serverless compute service for running code (functions), not for running Docker containers as-is. While Lambda can package and run container images, it is not designed for running multi-container applications with persistent storage volumes in the same way as container orchestration services. Lambda also has execution time and resource limits that are not suitable for all containerized workloads.
When this WOULD be correct
A company needs to run a lightweight, stateless containerized function in response to events (e.g., file uploads to S3) without provisioning servers. The function runs for a few seconds and does not require persistent storage. AWS Lambda would be the correct choice.
- ✓
AWS Fargate
Why this is correct
AWS Fargate is a serverless compute engine for containers. It eliminates the need to provision and manage EC2 instances or the container orchestration control plane. You define your containerized application (task definition) and Fargate launches and runs the containers. Fargate also supports persistent storage through Amazon EFS or Docker volumes, meeting the storage requirement with minimal operational overhead.
- ✗
Amazon ECR (Amazon Elastic Container Registry)
Why it's wrong here
Amazon ECR is a fully managed container image registry for storing, managing, and deploying container images. It does not run containers. ECR is used to store images that can be pulled by a compute service like Fargate or EC2, but by itself it cannot run the application.
When this WOULD be correct
A question asks which AWS service to use for securely storing and managing Docker container images, with requirements for image scanning, replication across regions, and integration with Amazon ECS or EKS. ECR would be the correct answer.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The CLF-C02 exam frequently reuses these exact scenarios with slightly different constraints.
✓AWS FargateCorrect answer▾
Why this is correct
AWS Fargate is a serverless compute engine for containers. It eliminates the need to provision and manage EC2 instances or the container orchestration control plane. You define your containerized application (task definition) and Fargate launches and runs the containers. Fargate also supports persistent storage through Amazon EFS or Docker volumes, meeting the storage requirement with minimal operational overhead.
✗Amazon EC2 with a container-optimized AMIWrong answer — click to see why▾
Why this is wrong here
Amazon EC2 with a container-optimized AMI requires provisioning and managing EC2 instances, which contradicts the requirement to not manage any EC2 instances or the container orchestration control plane.
★ When this WOULD be the correct answer
This option would be correct if the question required running containers on AWS with full control over the underlying EC2 instances, such as for compliance or performance tuning, and the team was willing to manage the instances and orchestration control plane.
Why candidates choose this
Candidates may think container-optimized AMIs are the simplest way to run containers on EC2, overlooking that they still require instance management, which the question explicitly wants to avoid.
✗AWS LambdaWrong answer — click to see why▾
Why this is wrong here
AWS Lambda is designed for short-running, event-driven functions, not for running multiple Docker containers with persistent storage volumes attached. It does not support long-running containerized applications or consistent access to persistent storage.
★ When this WOULD be the correct answer
A company needs to run a lightweight, stateless containerized function in response to events (e.g., file uploads to S3) without provisioning servers. The function runs for a few seconds and does not require persistent storage. AWS Lambda would be the correct choice.
Why candidates choose this
Candidates may think Lambda can run any container because it supports custom runtimes, but they overlook its limitations on execution duration, storage, and stateful workloads.
✗Amazon ECR (Amazon Elastic Container Registry)Wrong answer — click to see why▾
Why this is wrong here
Amazon ECR is a container image registry for storing and managing Docker images, not a compute service for running containers. It does not provide the ability to run containers or attach persistent storage volumes.
★ When this WOULD be the correct answer
A question asks which AWS service to use for securely storing and managing Docker container images, with requirements for image scanning, replication across regions, and integration with Amazon ECS or EKS. ECR would be the correct answer.
Why candidates choose this
Candidates may confuse ECR with a compute service because it is part of the container ecosystem and has 'container' in its name, leading them to think it can run containers.
Analysis generated from the official CLF-C02blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on CLF-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company is developing a microservices application using Docker containers. The development team wants to deploy and run these containers on AWS without having to provision or manage any underlying EC2 instances. Additionally, the team does not want to manage the container orchestration control plane. They need a fully serverless compute engine for containers that automatically scales based on demand. Which AWS compute option should the team use?
medium- A.Amazon EC2 instances with Docker installed
- B.AWS Lambda
- ✓ C.Amazon ECS with the AWS Fargate launch type
- D.Amazon EKS with managed node groups
Why C: Amazon ECS with the AWS Fargate launch type is the correct choice because it provides a fully serverless compute engine for containers. Fargate eliminates the need to provision or manage EC2 instances and removes the burden of managing the container orchestration control plane, as AWS handles both the underlying infrastructure and the orchestration layer. It automatically scales container instances based on demand, meeting the team's requirement for a serverless, auto-scaling container solution.
Last reviewed: Jun 11, 2026
This CLF-C02 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 CLF-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.