← Learn AWS SAA-C03
Lesson 6 of 6 · 8 min
Reading a scenario question
The mechanical process that turns four plausible options into one defensible answer.
The procedure
- Read the final sentence first. It states what is being asked; the preceding paragraph is context.
- Underline the qualifier — 'most cost-effective', 'least operational overhead', 'highest availability', 'without managing servers'. It decides between otherwise valid options.
- Note the hard constraints: compliance, data residency, RTO/RPO figures, protocols, existing components that cannot change.
- Eliminate options that are technically impossible or violate a constraint. There are usually two.
- Compare the survivors on the qualifier alone. One will be better on that axis.
- Sanity check against least privilege and managed services — the intended answer rarely stores long-lived keys or builds something AWS already offers.
Qualifiers and what they eliminate
| Phrase | Points toward | Eliminates |
|---|---|---|
| Least operational overhead | Managed and serverless services | Self-managed instances, custom scripts |
| Most cost-effective | The cheapest option still meeting the requirement | Over-provisioned or active-active designs |
| Without managing servers | Lambda, Fargate, Aurora Serverless, S3 | Anything on EC2 |
| Minimal application changes | Lift-and-shift, EFS, RDS | Re-architecting to DynamoDB or Lambda |
| Must not traverse the internet | VPC endpoints, PrivateLink, Direct Connect | NAT gateway, public endpoints |
| Real time / sub-second | Kinesis, ElastiCache, DAX | Batch, Glue, Athena |
| Highly available | Multi-AZ, Auto Scaling across AZs | Any single-AZ design |
Distractor patterns worth recognising
An option that is technically correct but ignores the qualifier — it works, but costs more or requires more management than the intended answer.
An option naming a real service used for something it does not do, such as using Athena for real-time lookups or CloudTrail for performance metrics.
An option that solves a problem the question did not ask about. If the stem is about cost and an option improves security, it is a distractor.
An option that is subtly impossible — cross-Region VPC peering with overlapping CIDRs, or attaching one EBS volume to instances in two AZs.
Worth remembering
- Read the last sentence first — it contains the actual requirement.
- Qualifiers like 'least operational overhead' or 'most cost-effective' are the tie-breakers.
- Eliminate on technical impossibility before comparing the survivors.
Test it now
Apply this on the hard bank, where options are deliberately close.