I sat the SAA-C03 recently and passed. Before I forget what actually worked, here's the honest breakdown.
The exam is not a memory test
AWS publishes the exam guide openly. Four domains, weighted percentages: Secure Architectures is 30%, Resilient Architectures 26%, High-Performing 24%, Cost-Optimized 20%. The questions drop you inside a scenario with a compliance constraint, a budget ceiling, or a failure condition, then ask you to pick the right architecture.
If you study by memorising service features, you will fail on the scenario questions because you have never practiced making the decision. I knew this going in because I had already built a fraud detection pipeline with SQS, Lambda, DynamoDB, and SNS. When a question asked me to choose between Lambda and Fargate for a PCI-constrained workload, I had a real reference point. That matters more than any flashcard.
Tutorials Dojo was the core resource, not a supplement
I used Jon Bonso's practice exams as the primary study mechanism, not a final check before sitting. The reason it works is the explanations. When you get a question wrong, it does not just show you the correct answer. It tells you exactly why each wrong answer is wrong.
That distinction is the whole exam. You are not picking the right option out of five. You are eliminating three plausible options. If you do not understand why the wrong ones fail, you will keep making the same mistakes on different question wording.
Community benchmark on Tutorials Dojo is consistent 80% before sitting the real exam. I used that as my gate.
Every wrong answer became an architecture pattern
When I got a question wrong I did not just note the correct service. I mapped the whole scenario.
Wrong on a DynamoDB composite key question? That becomes a working mental model for when a Global Secondary Index is the actual fix versus just restructuring the partition key. Wrong on an S3 lifecycle transition? That maps to the 30-day minimum billing rule for Standard-IA and why an aggressive lifecycle policy can cost more than doing nothing and oh boy does the exam love S3.
You build a schema that generalises to questions you have never seen. That is the only way to handle the 65 questions in 130 minutes without running out of time on edge cases.
Breadth over depth, done deliberately
SAA-C03 tests roughly 35 to 40 services with meaningful depth. Going deep on everything is a waste. Going shallow on the high-weight domains is how people fail.
Secure Architectures is 30% of the exam. If you cannot immediately distinguish when to use a Customer Managed KMS key versus an AWS Managed Key for an audit requirement, you are losing points on the biggest single domain. I spent more time on IAM policies, KMS, VPC endpoints, and CloudTrail than on anything else, specifically because the exam weights said to.
What I would skip next time
I spent too long on ECS versus EKS distinctions early on and very hyper focused portions of services like lambda, Eventbridge and Config for example. That is not where the exam goes. The exam goes into architectural tradeoffs including Multi-AZ RDS versus Read Replicas versus Aurora Global Database. That type of decision appears repeatedly.
If you're preparing for SAA-C03, start with Tutorials Dojo's AWS Certified Solutions Architect Associate Practice Exams from day one, not after you've finished a course. The feedback loop from testing yourself early is faster than any other method.
Follow me on Reddit: reddit.com/user/Escanut/
GitHub: github.com/escanut
Top comments (0)