DVA-C02 Development with AWS Services Practice Question
A developer needs to deploy a containerized application on AWS. The application requires persistent storage for stateful data. Which AWS compute service should the developer choose?
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 with Fargate
Amazon ECS with Fargate is the best choice for deploying a containerized application with persistent storage. Fargate supports persistent storage by integrating with Amazon EFS. While Amazon EKS with Fargate also supports persistent storage, ECS with Fargate offers simpler management and is often preferred for stateful containers. AWS Elastic Beanstalk can run containers but is more opinionated and less flexible for stateful configurations. AWS Lambda is stateless and ephemeral, not suitable for persistent storage.
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 ECS with Fargate
Why this is correct
This combination is ideal for deploying containerized applications requiring persistent storage because Amazon ECS provides robust container orchestration, while Fargate eliminates the need to manage underlying EC2 instances. For stateful applications, ECS tasks running on Fargate can seamlessly integrate with Amazon EFS for shared file system access or utilize bind mounts to local ephemeral storage (though EFS is preferred for true persistence across task restarts). This offers a fully managed, scalable, and highly available solution for stateful container workloads without server management overhead.
- ✗
AWS Elastic Beanstalk
Why it's wrong here
While AWS Elastic Beanstalk can deploy containerized applications using Docker environments, it operates as an application platform that abstracts much of the underlying infrastructure. This abstraction, while simplifying deployment for many web applications, often limits the granular control over container orchestration and persistent storage configurations that a developer might need for complex stateful containerized applications. Its primary design focuses on stateless web applications, making it less optimal for directly managing stateful container persistence compared to specialized container services.
- ✗
Amazon EKS with Fargate
Why it's wrong here
Amazon EKS with Fargate provides a powerful Kubernetes control plane for orchestrating containers on serverless compute, and it fully supports persistent storage through various CSI drivers, including Amazon EFS. However, deploying and managing Kubernetes, even with Fargate handling the data plane, introduces significant operational complexity and a steeper learning curve compared to Amazon ECS. For a stateful containerized application that is not inherently complex, the extensive feature set and inherent complexity of Kubernetes are generally considered overkill, leading to unnecessary overhead.
- ✗
AWS Lambda
Why it's wrong here
AWS Lambda is fundamentally designed for ephemeral, event-driven, and stateless functions, executing code in response to triggers with short maximum execution durations. Although Lambda now supports deploying functions using container images, the execution environment itself remains stateless and temporary, discarding any local state between invocations. This inherent statelessness and lack of persistent local storage make Lambda entirely unsuitable for stateful containerized applications that require data to persist across invocations or for long-running processes.
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 |
Go deeper
Related to this question
About these practice questions
Courseiva writes every DVA-C02 question from scratch — 1,135 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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 DVA-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 DVA-C02 exam.