My Honest Review of the AWS Solutions Architect Exam

I passed the AWS Solutions Architect Associate exam after roughly 3 to 4 months of studying.

I am also going to tell you something most people leave out of these posts. I failed my first attempt, yes, you heard right, I failed after months of studying and preparing for the exam.

I walked into that first exam feeling fairly confident, and I walked out of it humbled. There were practice exams that wrecked my confidence, concepts I had to relearn three or four times before they stuck, moments where I genuinely wondered if I was cut out for this but I persevered, was I pained? Yes, but I had to stay calm and reassess what happened to know why I failed.

I passed on my second attempt. And now I want to give you the honest version of what that journey actually looked like not the polished LinkedIn highlight reel, but the real tips, the real failure, and the real things I wish someone had told me before I started.

If you are thinking about this certification, this one is for you.

Why I Chose This Certification
After passing my AWS Cloud Practitioner which was foundation in cloud, There were a lot of other AWS certifications. I chose Solutions Architect Associate because it is widely recognised as the best general purpose entry point into cloud it does not lock you into one narrow specialty, and it builds a foundation that almost every other AWS path builds on, including security.

If you are coming from a non technical background like I was, this is the certification that proves you understand how cloud infrastructure actually works not just in theory, but in how real systems are designed.

What the Exam Actually Tests
This is the part people get wrong before they start. The Solutions Architect Associate exam is not about memorising AWS service names, It is about understanding how to design systems that are

- Secure: using IAM, encryption, and access controls correctly
- Resilient: built to handle failure without falling apart
- High performing: choosing the right services for the right workload
- Cost optimized: designing solutions that do not waste money

Almost every question is a scenario. "A company needs X and Y Which solution is the best fit?" You are rarely just recalling facts, you are carefully analyzing the situation and offering the best solution. That distinction changes how you should study which leads me to the biggest lesson I learned.

The Biggest Mistake I Made Early On
I started by trying to memorise services, I made flashcards, I wrote out service names and definitions. I genuinely believed if I could recite what each AWS service did, I would be ready.

I was wrong, badly wrong, the exam does not ask "What is Amazon S3?" It asks something closer to "A company needs to store infrequently accessed data for compliance purposes for 7 years at the lowest possible cost. Which storage solution is best?" You need to know S3 Glacier exists, understand its use case, and recognise it instantly inside a scenario.

What Happened When I Failed
I missed the pass mark not by a huge margin, but enough to know the gap was real, not a fluke. I remember sitting in my car afterward feeling embarrassed, replaying every question I was unsure about, wondering if I had wasted months of effort.

This is what that failure actually taught me, once I let myself look at it honestly:

- I had memorised services instead of understanding scenarios and concepts.
- I was weak in networking and compute, two areas I had under studied because they felt "boring" compared to high availability and storage
- I had not taken nearly enough timed practice exams to get comfortable with the pacing and pressure of the real thing.
Failing was not the end of the story, It was the most useful feedback I got in the entire process.

What I changed before the retake

I rebuilt my study plan around my weak areas instead of restudying everything from scratch. I took a full timed practice exam every few days instead of occasionally and focused on understanding concepts. I stopped consuming new content two weeks before the retake and spent that time purely reviewing wrong answers and weak topics.

Five to six weeks later, I sat the exam again and I passed.
If you fail, you are not behind. You are one step closer to knowing exactly what to fix.

What I Wish Someone Had Told Me

Failing is part of the process for a lot of people, not a sign you do not belong. I am talking about mine because I think the silence around it makes everyone else's struggle feel abnormal, It is not.
It is normal to feel behind. Cloud concepts takes time to click. If something does not make sense the first time, that does not mean you are not capable, it means you need to see it from a different angle or in a different scenario.
The exam rewards well analysed solution, not memorisation. Stop trying to memorise everything, start asking "why would I choose this over that?"
You do not need a technical background to pass this exam. I came from project management, What helped me most was not prior technical knowledge, it was discipline, structured studying, and a willingness to be a beginner again, twice.

Beyond the certification itself, this process taught me how cloud systems are actually designed, knowledge that now underpins everything I am learning in cybersecurity. It also taught me something less technical but just as valuable, how to fail, reassess and try again without letting it define me.

If you are on the fence about starting, that uncertainty is normal. Start anyway, and if you fail along the way, that is not the end of your story either, it was not the end of mine.