My Journey to SAA-C03: How I Cleared the AWS Solutions Architect Associate Exam
A student’s practical guide to the jump from Cloud Practitioner to Associate: what’s harder, how I prepared, and tips for your own attempt.
Why I went for SAA-C03
I'm a final-year computer science student graduating in 2 months. I passed the AWS Certified Cloud Practitioner (CLF-C02) in May 2026 and the Solutions Architect Associate (SAA-C03) in September 2026.
I'd already used AWS in a few school projects, mostly S3, DynamoDB with a bit of IAM and EC2 along the way. But I wanted to graduate with a proper associate-level certification, not just the foundational one. If you're a student or beginner thinking about the same jump, this post is for you.
How big is the jump from CLF-C02?
Bigger than I expected. Cloud Practitioner asks what a service is. The Associate exam goes deeper: most of the answer options are technically correct, and your job is to pick the most correct one for the scenario, whether that's the cheapest, the most resilient or the least operational overhead. Knowing what each service does isn't enough. You have to know when to choose it over the alternatives.
My study plan
I prepared for about 4 to 5 weeks, roughly 2 hours a day on weekdays. That's around 40 to 50 hours in total.
- Video course. I followed an online tutorial that teaches each service one by one. This built the base.
- Exam domains in order. I went through Domains 1 and 2 first, then Domain 3, and left Domain 4 for last.
- AWS Skill Builder. Verified students on Builder Center get a year of Skill Builder access, which gave me Builder Labs and official practice question sets.
- Hands-on work. I completed the free AWS Serverless microcredential prep and built a few small projects. Actually clicking through the console made the services stick far better than reading about them.
Practice tests
I took practice tests from Tutorialsdojo, 65 questions each with and I was averaging around 72% ine each. Two things made them useful:
- Explanations and per-domain breakdowns. After each test I could see exactly which domain was dragging my score down, so I knew where to spend my next study session.
- An LLM as a mistake analyzer. I pasted in the questions I got wrong and asked it why my choice was wrong and what clue in the question pointed to the right answer. This helped me spot patterns in how I was misreading questions.
- Topic based and sections based exams were useful for revision too
My scores went from 50% to 80% across attempts.
My weak spots and how I fixed them
I used spaced repetition to drill the pairs I kept mixing up. Some of them are:
| Pair | Rule of thumb |
|---|---|
| Route 53 vs Global Accelerator | Route 53 is DNS-based routing (latency, geolocation, weighted, failover) and is subject to DNS caching. Global Accelerator gives you static anycast IPs and routes traffic over the AWS global network, with fast failover and no DNS caching. |
| Auto Scaling group health checks | By default an ASG only uses EC2 status checks. If you want it to replace instances that the load balancer marks unhealthy, enable ELB health checks and set a sensible grace period. |
| FSx for Lustre vs EFS | Lustre is for high-performance workloads like HPC and ML, and integrates with S3. EFS is general-purpose shared NFS storage for Linux workloads. |
Exam day
I took the exam at a test center instead of at home. It costs the same, and a test center is simply the safer option: no worrying about my internet, webcam or room setup.
Topics that showed up a lot for me were serverless architectures, including the SNS-to-SQS fan-out pattern, DB settings, ASG of EC2 instances behind ALB/ NLB type scenarios. If you're short on time, make sure you understand those well.
What I'd do differently
- Practice more. More practice tests means more exposure to the "pick the most correct answer" style.
- Do more labs on Skill Builder. I'd spend a bigger share of my time on hands-on labs instead of just watching and testing.
Tips if you're starting out
- Learn the services with a course, but switch to practice questions early. They show you what the exam actually asks.
- Always ask "what's the best option for this scenario?" Several answers will work, but only one fits the stated requirements best.
- Review your wrong answers properly, not just your score.
- Build something small with the services you're studying.
- Drill confusing pairs with spaced repetition until you can explain the difference without notes.
What's next
Now comes the part that matters most: using what I learned in my school projects, at work and in my personal projects, where I can design things properly instead of just making them work.
What was your toughest SAA topic, and how did you study it? Let me know in the comments.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article