How to work through the deck
The AWS Certified Solutions Architect – Associate exam asks you to choose between plausible architecture options in short scenarios. The useful question is not just “What does this service do?” but “Which requirement makes this service the best fit?” A card should make you retrieve one decision or distinction, then check whether you can explain why it fits.
Work through the deck one card at a time. Read the question, answer from memory, then reveal the answer and choose a grade honestly: Again if you could not retrieve it; Hard if you got it with effort or missed an important condition; Good if you answered correctly; Easy if you could explain it promptly and clearly. A correct guess is not the same as a reliable answer.
For scenario questions, practise adding a short reason to each answer: name the constraint, the AWS service or pattern that meets it, and the key setting or limitation. This helps with distractors that use a real service but fail on cost, security, availability or networking boundaries. The deck below concentrates on distinctions that often change the architecture choice.
The deck: retrieve, reveal, grade
A MySummaries AWS SAA deck puts the prompt first and the answer on the card. Start with the first prompt, retrieve your answer before revealing it, and grade the recall before moving on.
How can CloudFront access a private S3 bucket without making the bucket public?
Use CloudFront Origin Access Control (OAC) and a bucket policy that grants the CloudFront service principal access for the intended distribution.
All 19 cards
That is a MySummaries deck, filled with AWS SAA material. Yours is written from your own notes. Start free
After the first pass, do not spend equal time on every card. Mark a card Again or Hard if you named the service but missed the architectural consequence. For example, knowing that RDS Multi-AZ improves availability is incomplete if you then choose it to serve extra reads. Likewise, remembering that an SQS standard queue is highly scalable is not enough if your consumer assumes each message arrives exactly once and in order.
On a second pass, say the answer as a compact decision rule. “Use an S3 gateway endpoint for S3 access from private subnets” is more useful when you can add that it is associated with route tables and does not require a NAT gateway for that traffic. Keep the explanation tied to the card’s fact; do not turn every review into a long service summary.
The must-not-miss core behind the cards
A MySummaries core checklist reduces the deck to the facts most likely to change a design choice. Use it as a final retrieval test: explain each line without looking, then return to any card you could not justify.
The checklist is intentionally compact. It is not a substitute for reading the scenario carefully: an answer that is generally valid can still be wrong if it ignores a stated cost limit, latency target, data-protection condition or network boundary. Practise identifying the requirement first, then selecting the pattern that satisfies it with the least unnecessary complexity.
Turn repeated misses into a repair task
If the same distinction keeps costing you recall, isolate it instead of rereading the whole deck. A useful repair prompt makes you choose between two similar options and state why one fits. Answer it aloud or in a sentence, then revisit the related cards on your next review.
A MySummaries remediation tray can hold a short prompt for a repeated miss, ready for another attempt.
You have twice chosen a NAT gateway for private-subnet access to S3. Which VPC endpoint type can route S3 traffic through route tables without NAT, and what must you associate it with?
A complete repair answer is: “Use an S3 gateway endpoint and associate it with the route tables used by the subnets.” If you only recalled “endpoint”, grade the answer as incomplete. The point is to retrieve the service type and the configuration detail that makes it work.
When you have finished, sort the remaining weak cards by the decision they test: networking, availability, messaging, storage or security. That gives you a practical next study task. For a card you repeatedly miss, add a small architecture scenario and compare the best-fit choice with its closest distractor. Do not memorise a service name without learning the condition that makes it the right answer.
How MySummaries helps
Build an AWS SAA revision board from your own notes, then use it to generate and review cards like these. Open MySummaries to work from your study material.