How I Passed the AWS Solutions Architect Professional

My AWS journey#copied

I started my career in a technology solutions company that was deeply rooted in AWS and Azure. Most of my early work involved building Java enterprise applications that were deployed on AWS infrastructure.

In 2020, the company kindly sponsored my first certification: the AWS Certified Developer – Associate. I still remember that period vividly; it's as if a wave of study momentum swept through our department. Software engineers were eagerly clearing AWS and Azure associate certifications, while the more experienced solution architects grinded for the professional-level exams. Among them, the AWS Certified Solutions Architect – Professional felt like the unofficial “holy grail” for my track.

That early exposure shaped how I approached learning in the years that followed. I carried that discipline across roles and kept building my certification journey:

By 2025, I felt fairly comfortable working with AWS services. Clearing the AWS Certified Solutions Architect – Associate and the AWS Certified Data Engineer – Associate that year felt less like a genuine challenge and more like a test of how quickly I could pass them with minimal preparation, leaning mostly on what I was already doing at work.

Looking back, the associate-level exams felt relatively straightforward. With some real-world experience and a good course such as Stephane Maarek’s AWS series on Udemy, the associate-level exams are very passable.

While it can feel like mundane memorization at first, I’ve always encouraged junior engineers to go through at least the curriculum of an associate-level certification (certification is optional). It gives you a broad overview of the essential AWS services and how they fit together.

Even in the age of AI, this foundational cloud knowledge is still valuable, not because you need to remember every detail, but because it builds your mental model on what is possible and what isn’t. That intuition helps you avoid unnecessary rabbit holes and gives you the confidence to defend your first few system designs or features.

Facing the gap between associate and professional level#copied

In 2026, I set my sights on the AWS Certified Solutions Architect – Professional as part of my personal annual goals to truly challenge myself to think and operate at the next level.

After attempting the free sample questions, the difference in level was evident. The questions were longer, more nuanced, and rarely had a straightforward answer you could spot at first glance. It wasn’t just about knowing services anymore; it was about interpreting intent. Understanding what the question was really asking became just as important as knowing AWS itself.

At that point, I knew I couldn’t approach this the same way as the associate exams.

That led to a more uncomfortable question:would I still feel accomplished if I passed it purely by memorizing patterns and passively watching videos?

The answer was a clear no for me.

At work, we may be exposed to a wide range of AWS services, but often only at varying depths. And outside your immediate role, there are entire domains you don’t really touch. For me, networking and security were often “just enough to get by” rather than explored deeply.

Armed with a one-month subscription to AWS Skill Builder, I gave myself a tight timebox to uncover my unk-unks about AWS. I worked through all of the AWS Cloud Quest learning paths and earned every available AWS micro-credential. The role-based labs pushed me into areas I rarely touched in my day-to-day work, especially networking and security.

A few reasons this approach worked well for me:

1. It rewards hands-on learning over passive consumption. Cloud Quest is role-based and gamified, so you’re actively building in the AWS console rather than watching explanations. That level of engagement stuck far better than watching videos and memorizing PowerPoint slides.
2. The labs run in isolated AWS accounts. There’s no billing anxiety or fear of breaking anything, which made it easy to practice consistently after work.
3. About half of the CloudQuest content overlapped with my day job, which turned into a structured way of reinforcing fundamentals I already knew.
4. The other half exposed blind spots, especially in networking, security.
5. It reinforced AWS’s own best practices, showing how services are meant to fit together in real production systems "the AWS way".

AWS Skill Builder also comes with a full set of official practice questions for the SAP exam which is a sweet bonus after clearing 100–200 labs in a month.

Tips#copied

• Earn at least one associate-level certification first.
  • The Professional builds directly on what you learn for the SAA. Knowing your fundamentals at some level gives you the confidence to choose between two close options under pressure.
  • AWS often runs campaigns that provide up to 50% off their certification. However, these coupons are only available for Practitioner and Associate level. Passing any certification gives you a 50% coupon, and I find that using it on Professional / Speciality certs gives the most ROI.
• Get your hands dirty and read the docs.
  • Labs will get you comfortable building things, but the documentation is where you find the details. Do both.
• Take notes you'll actually reread.
  • Whenever I learn something new or realise I was wrong about how something works, I turn it into short, actionable notes in my Obsidian vault. The point isn’t documentation for its own sake; it’s building something I can quickly pull up later when the same pattern shows up at work.
• Try the official AWS practice exam.
  • Getting used to how AWS phrases its questions makes it much easier to read the intent behind them. This often determines whether you pass the exam or not.
• Leverage company sponsorship
  • AWS professional-level certifications are expensive even with discount coupons. If your company offers certification funding, use it meaningfully and strategically. It can also contribute to your KPIs, which adds an extra layer of accountability

Start today#copied

If you are also thinking about clearing the AWS SAP certification, the easiest mistake is waiting for the “right time” to start. There isn’t one. Just start today, even if you feel unprepared at first. Pick one weak area.

Is clearing 100–200 Cloud Quest labs within a month overkill for SAP? Probably yes, if you have sufficient real-world experience. Can you speed run AWS SAP? Also probably yes, it is possible to cram with short study sprints and question banks. But that misses the point.

Because the certification is not the goal.

The real value is in how it changes the way you think about systems, how you evaluate trade-offs, and how you question defaults. The real challenge is making the more optimal architectural decision every day. Without that intuition, AWS SAP is just a fancy badge on your resume.

And passing doesn’t mean you’re done either. AWS ships changes constantly, and certain services such as Bedrock move faster than the exam blueprint can keep up with. But that’s exactly where SAP pays off. It challenges you to build a strong mental model of how AWS services work and fit together. With that foundation, new services are easier to absorb because you can map them onto existing patterns and structures.

So start today, but don’t start to finish quickly. Start to understand.

Reactions