Service-Fit Recognition — AWS Developer (DVA-C02)
The Workload Noun Narrows the Service Before Constraints Do
'Relational database' in a scenario maps to RDS or Aurora, not DynamoDB. 'Object storage' maps to S3, not EFS. 'Event-driven compute' maps to Lambda, not EC2. 'Virtual machine' or 'persistent OS access' maps to EC2, not Lambda. Candidates over-complicate by introducing DynamoDB into relational scenarios or Lambda into always-on compute requirements. Each workload noun carries an implied access pattern, billing model, and operational boundary that the wrong service cannot replicate without added glue configuration. Read the workload noun before reading the constraints; the noun alone often eliminates two or three answer choices immediately.
What This Pattern Tests
The exam tests whether you match a specific requirement to the most appropriate service even when a more powerful service could technically handle it. DynamoDB excels at single-digit millisecond key-value access at any scale but cannot do joins. Aurora excels at complex relational queries with up to 128TB storage but has provisioning overhead. ElastiCache Redis provides microsecond reads but data is volatile. The exam gives a specific access pattern and tests whether you pick the service that fits rather than the service that can do the most.
Decision Axis
Requirement precision vs. service capability. The best fit is the simplest service that fully meets the access pattern.
Associated Traps
More Top Traps on This Exam
Decision Rules
When the data model requires variable or sparse attributes per item AND the only query shape is a single-key lookup at unpredictable write throughput, DynamoDB's schema-less design and key-based performance contract disqualify RDS as the near-right relational default.
Domain Coverage
Difficulty Breakdown