Drag a concept onto its matching description — or click a concept then click the description.
Object storage
NoSQL database
Serverless compute
RESTful API creation
Message queuing
Match each AWS service to its primary use case.
Drag a concept onto its matching description — or click a concept then click the description.
Object storage
NoSQL database
Serverless compute
RESTful API creation
Message queuing
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
AWS Lambda: Serverless compute service that runs code in response to events.
Correct matches: Lambda is serverless compute, DynamoDB is NoSQL database, S3 is object storage, Elastic Beanstalk is PaaS. Common confusions include swapping Lambda and DynamoDB definitions.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
AWS Lambda: Serverless compute service that runs code in response to events.
Why this is correct
AWS Lambda is a serverless compute service that executes code in response to triggers such as API Gateway requests, S3 object uploads, or DynamoDB table updates, automatically managing the underlying infrastructure. You write functions in languages like Python, Node.js, or Java, and Lambda scales horizontally by running concurrent instances for each event, with billing based on execution time and requests. It is purpose-built for event-driven, short-lived workloads, not as a persistent data store.
Amazon DynamoDB: Fully managed NoSQL database service for key-value and document data.
Why this is correct
Amazon DynamoDB is a fully managed NoSQL key-value and document database that delivers single-digit millisecond latency at any scale, using tables, items, and attributes rather than SQL relational schemas. It supports on-demand and provisioned capacity modes, global tables for multi-Region replication, and features like DynamoDB Streams and TTL for time-based data expiration. Its design makes it ideal for high-traffic web apps, gaming, and IoT telemetry, but it does not execute arbitrary code.
Amazon S3: Scalable object storage service for storing and retrieving any amount of data.
Why this is correct
Amazon S3 is a scalable object storage service that stores data as objects in buckets, offering 99.999999999% (11 nines) durability through redundant replication across multiple Availability Zones. It supports versioning, lifecycle policies, server-side encryption, and static website hosting, and you can retrieve any amount of data from anywhere via REST APIs or SDKs. S3 is not a database or a compute runtime, but a highly durable, cost-effective storage tier for backups, data lakes, and media.
AWS Elastic Beanstalk: PaaS for deploying and scaling web applications.
Why this is correct
AWS Elastic Beanstalk is a platform-as-a-service that automates the deployment, capacity provisioning, load balancing, and auto-scaling of web applications, letting developers upload code and have AWS handle the operational stack. It supports common platforms like Java, .NET, PHP, Node.js, Python, Ruby, and Docker, while giving optional access to the underlying EC2 instances. Unlike Lambda, it runs long-lived web servers rather than event-driven functions, and you still pay for the underlying compute resources.
AWS Lambda: Fully managed NoSQL database service for key-value and document data.
Why it's wrong here
This option mistakenly describes DynamoDB as AWS Lambda. Lambda is not a database at all; it is an event-driven compute service that executes function code, while DynamoDB is the fully managed NoSQL key-value and document database. Using Lambda in place of DynamoDB would fail entirely because Lambda functions have no persistent data model, no query engine, and no table-based storage, so treating it as a database would be architecturally invalid.
Amazon DynamoDB: Serverless compute service that runs code in response to events.
Why it's wrong here
This option wrongly assigns Lambda's compute behavior to DynamoDB. DynamoDB is a managed NoSQL database, not a serverless compute service; it exposes APIs for PutItem, Query, and Scan but provides no general-purpose code execution runtime. You can trigger a Lambda function from a DynamoDB stream, but the database itself never runs your application logic, and any attempt to deploy function code into DynamoDB is unsupported and conceptually confused.
Quick reference
| 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
About these practice questions
Courseiva writes every DVA-C02 question from scratch — 724 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 →
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.