AWS Fargate for Serverless Container Execution
A company wants to update its online data processing application by implementing container-based services that run for 4 hours at a time. The company does not want to provision or manage server instances. Which AWS service will meet these requirements?
Community Votes
75% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The core concept tested is identifying serverless compute options for containerized workloads, with the common trap being the confusion between Lambda (function-based) and Fargate (container-based).
This question addresses the selection of AWS container services that eliminate server management overhead. It establishes that AWS Fargate is the correct service for running containers without provisioning EC2 instances.
Many learners incorrectly choose AWS Lambda because it is the most popular serverless option, but they overlook the specific requirement to run 'container-based' services rather than code functions.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
AWS Fargate is a serverless compute engine for containers that works with both Amazon ECS and EKS. The question explicitly requires a "container-based" solution where the company "does not want to provision or manage server instances." Fargate abstracts away the underlying infrastructure, allowing you to run Docker containers on demand for the specified duration (4 hours) without managing any servers.Why the Other Options Are Wrong
Amazon EC2 requires manual or automated provisioning and management of virtual machines, violating the no-management constraint. AWS Elastic Beanstalk is a Platform as a Service (PaaS) that often provisions EC2 instances in the background, requiring some level of infrastructure management compared to Fargate. AWS Lambda is serverless but executes code in response to events (functions), not long-running containerized applications in the same manner as Fargate.Community Comment Notes
Community feedback highlights the importance of keywords. As user AravindrajG noted, the key phrase is "container-based services," which directly points to Fargate over other serverless options like Lambda. User ShaiTay initially considered Lambda but corrected themselves to Fargate upon realizing the container distinction.Exam Strategy
When reviewing AWS compute options, always check if the workload is code-based (Lambda) or container-based (Fargate). If the prompt mentions 'containers' and 'no server management,' Fargate is almost always the answer.
Frequently Asked Questions
Why isn't AWS Lambda the right choice here?
Lambda is designed for short-lived function execution, whereas Fargate is built specifically for running containers, including those that may run for longer durations like 4 hours.
Does Fargate support all container images?
Yes, Fargate supports any container image stored in Amazon ECR, Docker Hub, or other registries, provided the image is compatible with the architecture.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →