CLF-C02 · Question #256
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…
The correct answer is B. AWS Fargate. AWS Fargate (B) is the right choice because it is a serverless compute engine for containers - you define your container workload and Fargate handles the underlying infrastructure, with no limits on task duration (supports the 4-hour runtime requirement). Why the others are…
Question
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?
Options
- AAWS Lambda
- BAWS Fargate
- CAmazon EC2
- DAWS Elastic Beanstalk
How the community answered
(60 responses)- A7% (4)
- B78% (47)
- C3% (2)
- D12% (7)
Explanation
AWS Fargate (B) is the right choice because it is a serverless compute engine for containers - you define your container workload and Fargate handles the underlying infrastructure, with no limits on task duration (supports the 4-hour runtime requirement).
Why the others are wrong:
- A. AWS Lambda - serverless but limited to a maximum 15-minute execution timeout, making it unsuitable for 4-hour tasks.
- C. Amazon EC2 - requires you to provision and manage virtual server instances directly, violating the "no server management" requirement.
- D. AWS Elastic Beanstalk - abstracts some infrastructure management but still provisions and manages EC2 instances under the hood; it is not truly serverless.
Memory tip: Think "Fargate = serverless containers, Lambda = serverless functions." When a question mentions containers + no server management, Fargate wins. When it mentions functions/code snippets with short runtimes, Lambda wins.
Topics
Community Discussion
No community discussion yet for this question.