Why I wanted it
I’m a developer, and for a long time my AWS credibility lived entirely in my portfolio. I could point to things I’d built and say “this works” - but I wanted something that pointed the other way too: a way to show AWS knowledge and experience directly, not just infer it from projects.
There was a second, more practical reason. Day-to-day, you naturally reach for the same handful of services. I wanted to deliberately explore the parts of AWS I don’t touch regularly, so I could be confident I was making the right technical decisions - on my own projects and on client work - rather than defaulting to what I already knew. The SAA-C03 was the forcing function to do that properly.
If you’re a working engineer weighing this cert, that’s exactly who I’m writing for.
What the exam tests
Strip away the branding and SAA-C03 is testing one thing: can you pick the architecture AWS would recommend, given constraints around security, resilience, performance, and cost?
The format, so you know what you’re walking into:
- 65 questions, multiple choice or multiple response, in 130 minutes.
- 15 of those are unscored trial questions, unmarked - so roughly 50 count, but you can’t tell which, so treat them all as real.
- Scored on a scaled 100–1,000, and you pass at 720.
- Four domains, weighted: Design Secure Architectures (30%), Design Resilient Architectures (26%), Design High-Performing Architectures (24%), and Design Cost-Optimized Architectures (20%).
The mindset shift that matters most: the exam rarely asks “does this work?” - several options usually work. It asks which is best against the stated priority. More on that below, because it’s the single biggest thing that separates a pass from a fail.
My study approach
I studied for a few weeks in total, but I’ll be honest about where the real learning happened: mock exams. They weren’t a final check for me - they were the study method.
My path was simple: learn, mock, book the exam.
- Learn the surface area. I worked through Stephane Maarek’s course to map every relevant service and where it fits: Ultimate AWS Certified Solutions Architect Associate SAA-C03.
- Mock relentlessly. I did 12 full practice exams - 6 from Stephane Maarek and 6 from Jon Bonso (Tutorials Dojo): Stephane Maarek - Practice Exams & Jon Bonso - Practice Exams
- Book it. Once the mock scores were consistently landing where I wanted, I booked the exam.
Here’s the part that made the mocks work: every question comes with a written explanation. When I got one wrong, I read the explanation and learned the concept from there. That loop - attempt, miss, understand why - taught me far more efficiently than re-watching lectures ever did. The mocks weren’t just measuring my readiness; they were building it.
The hardest part: questions where every answer “works”
The toughest questions weren’t the ones where I didn’t know the services. They were the ones where multiple answers would all technically work, and passing came down to spotting the key phrase steering you toward one of them.
Is the question quietly optimising for least cost? Most performant? Highest availability? Least operational overhead? That single qualifier is usually the whole question. Miss it and you’ll confidently pick an answer that works perfectly - and is wrong. Once I started hunting for that phrase in every scenario, my accuracy jumped.
Exam day (and a lesson about pets)
I took the exam online, from home. The flag-and-return feature was genuinely useful: I did a fast first pass, flagged anything I wasn’t sure about, and came back to those with a clearer head rather than burning time up front.
One thing the guides don’t warn you about: the home testing environment rules are strict, and they apply to pets too. No one else is allowed in the room, your desk has to be clear, and you can’t get up or talk. Which is a problem when Floki - one of my cats - decided halfway through that this was the moment he urgently needed into the room, scratching and meowing at the door. It was distracting, and a proctor can flag that kind of noise. So: if you’re testing from home, sort out the pets (and everyone else) before you start. Lock the door, and make sure your feline colleague is on the other side of it.
Was it worth it?
Yes. It was a great refresher on AWS features I don’t use day-to-day, and - exactly as I’d hoped - it gave me the confidence to reach for that functionality in future projects rather than sticking to my usual toolkit. The value wasn’t the PDF certificate; it was the broader mental map of what AWS can do and when to use it.
Who I’d recommend it to: developers already working near AWS who want to make design decisions deliberately, and who’d benefit from being pushed into the corners of the platform they normally avoid.
Advice to anyone starting
A few things I’d tell my past self, and a couple of extras worth knowing:
- Read the questions closely. They’re almost always directing you toward something specific - least cost, most performant, least overhead. Find that phrase before you look at the answers.
- Eliminate the obviously wrong answers first. You can usually rule out one or two options immediately — an answer that ignores the stated constraint, uses the wrong service entirely, or is clearly over-engineered. Cutting the field down to two makes the real decision far easier and faster.
- Don’t get tied up in hyper-specific detail. There will be the occasional question you just won’t know - I had one about pricing storage for a specific I/O profile, with tightly-coupled options that would be trivial to work out with a calculator online but are a real time-sink to reason through manually. In a normal working environment you’d just look it up. Don’t let one question like that rattle you or eat your clock; flag it, guess, move on.
- You don’t have to accept the first exam slot offered. When booking, it suggests the next available time - which for me kept landing very late at night or very early in the morning. There’s a small option to pick a different slot. Use it and choose a time when you’ll actually be sharp.
- Use the mocks as your teacher, not just your test. Read the explanation for every question you get wrong - and every one you got right by luck. That’s where the real learning is.
- Simulate the real thing. Do at least a few mocks full-length and timed, in one sitting, so 130 minutes of focus isn’t a shock on the day.
- Trust the flag-and-return rhythm. With 130 minutes for 65 questions you have room - but only if you don’t let one nasty scenario swallow it. First pass fast, revisit the flags after.
Wrapping up
If you’re mid-prep and want to compare notes, drop a comment or reach out - and if you’ve just passed, go enjoy that result screen. You earned it. (Floki sends his apologies.)
