There is one exam on my list that reading could not get me through.

Solutions Architect Professional. I sat it in my first months at AWS, and it was the certification where my usual approach stopped working. Read the guide, watch the videos, do the practice questions, turn up. That is how most of us study.

Not this one. The questions did not ask what a service does. They were scenarios. Several services working together, a constraint, a trade-off, and something that had to keep running.

You cannot memorise that. You only recognise it if you have watched it break.

So I stopped reading and started building. Small things, each built so I understood one topic well enough to answer a question about it under pressure. That is what got me through.

I am studying again now, and the same thing is happening. I am building more than I am reading.

I have earned ten cloud certifications, six AWS and four Azure. The ones that changed how I work are the ones that made me build.

Here is what I see with career changers every month. They treat the exam guide as a reading list. They pass, put the badge on LinkedIn, then freeze in the first interview that asks "walk me through how you would set that up".

Memorised knowledge does not survive a follow-up question. Built knowledge does.

So my rule is simple. Choose certs that make you build, and study for every cert as if it does.

Start with the domain headings. Every certification publishes them. Each domain is a list of things you should be able to do, not things you should know, so treat it that way.

For each domain, pick the smallest thing that uses it. A networking topic becomes two subnets and a route that should not work. A storage topic becomes a bucket with a policy you try to get past. An afternoon, not a weekend.

Break it on purpose, in a sandbox. Remove a permission, delete a route, switch off the thing you think is optional. The error you get teaches you more than the paragraph explaining the concept, and scenario questions are built around exactly that kind of failure.

Write one line on what broke and one on what you learnt. Those two lines are your answer to the interview question, and they are what you will remember on exam day.

Do this for every domain and the practice questions start to look familiar. Not because you have seen the question, but because you have lived the scenario in miniature.

Today's sponsor is Wispr Flow. If you are logging what you built and what broke while you study, voice dictation can capture the note before you lose the detail.

If you have paid time left on an individual Granola plan, we'll match it with a Wispr Flow subscription that includes Notetaker and dictation, and add bonus time, up to 12 months total. Sign in or create a Wispr account and submit proof of your plan to check eligibility.

Try Notetaker Free

💬 Which cert are you studying for right now, and have you built anything for it yet?

Reply with LAB and the cert. I will suggest the first small thing I would build for it this week. I read every reply.

Know someone studying for a cert with a highlighter and no console open? Share your referral link. One friend subscribes, you get a free LinkedIn Profile Optimisation Checklist.

{{rp_refer_url}}

Shola

P.S. If you want one row per exam domain for what you will build, what broke and what you learnt, here is the Build-While-You-Study Log (1-page PDF), direct link, no signup. Next Tuesday: the everyday ways I use AI outside the day job, including helping family and friends and running a few bots of my own. 6PM UK.