My 4-Step Study Plan for Passing the AWS Solutions Architect – Associate

As a Web Engineer focused on full-stack implementations, I've spent years immersed in the AWS ecosystem. My daily toolkit prominently features services like EC2, DynamoDB, Redis, Lambda, API Gateway, and S3. While I was comfortable building and deploying applications, I knew there was a vast universe of AWS services and architectural best practices beyond my day-to-day work.

This year, I set a personal goal at work to achieve the AWS Certified Solutions Architect – Associate certification. It wasn't just about a badge; it was about truly going deeper into subjects I touched lightly, understanding how to architect robust solutions, and ultimately becoming a more well-rounded cloud professional. I'm thrilled to say I passed the SAA-C03 exam on my first attempt with an impressive score of 903/1000!

Here’s the exact study plan I followed over nine consistent months.

Introduction: What is the Solutions Architect - Associate Exam?

The AWS Certified Solutions Architect – Associate exam is a benchmark in the cloud industry, validating your ability to design and implement secure, resilient, high-performing, and cost-optimized systems on AWS. It moves beyond simply knowing what individual services do; it challenges you to understand how they integrate to form complete, well-architected solutions.

The exam focuses on four key domains:
  • Design Secure Architectures (30%)
  • Design Resilient Architectures (26%)
  • Design High-Performing Architectures (24%)
  • Design Cost-Optimized Architectures (20%)
This means you need a broad understanding across many AWS pillars, including networking, databases, security, serverless, and more.

My 4-Step Preparation Strategy

My study journey spanned about nine months, dedicating roughly 5 hours each week. While my existing hands-on experience with core services was a huge advantage, this structured approach was vital for delving into unfamiliar areas and mastering the exam's specific questioning style.

1. The 30,000-Foot View: AWS Certified Solutions Architect Study Guide by Ben Piper

I began my journey with this book to get a comprehensive, high-level overview of the entire AWS landscape relevant to the Solutions Architect Associate exam. It was an excellent way to map out the vast territory, identify services I wasn't familiar with, and understand the general concepts before diving into the nitty-gritty. Think of it as setting the stage for everything that followed.

My Takeaway: This book provides a solid foundational understanding and helps you structure your subsequent, more detailed studies. Don't aim for memorization here, but rather a broad understanding.

2. The Deep Dive: Adrian Cantrill's Video Course (learn.cantrill.io)

This course formed the absolute backbone of my preparation. Adrian's approach isn't just about passing the exam; it's about genuinely understanding cloud architecture. He meticulously breaks down complex topics, often starting from the very basics (like explaining networking fundamentals) and building up to intricate, multi-service designs.

The hands-on labs were a game-changer. I wasn't just passively watching; I was actively building, configuring, and troubleshooting. Since I was already familiar with services like EC2, Lambda, and DynamoDB, I could accelerate through some sections. However, for areas I rarely touched at work, such as complex networking (VPC peering, Transit Gateway, Direct Connect) or specialized database options, Adrian's detailed explanations and diagrams were indispensable.

My Takeaway: Invest the time in this course. Its depth, real-world relevance, and extensive labs provide an unparalleled learning experience that goes far beyond just passing the exam.

3. The Reality Check: Tutorials Dojo Practice Exams

After months of learning, it was time to test my knowledge in an exam-like environment. The Tutorials Dojo practice exams are legendary for a reason—they accurately mirror the difficulty, question style, and breadth of topics found on the actual AWS exam.

I started by taking an exam in "Timed Mode" to simulate the pressure and identify my initial score. The real gold, however, is in the detailed explanations provided for every single answer. I meticulously reviewed all questions, not just the ones I got wrong. This process allowed me to understand why an answer was correct (or incorrect), often pointing me to specific AWS documentation for further reading. This step was crucial for shoring up my weaker areas, especially those concerning subjects I don't use daily, like on-premise migrations and the nuances of AWS Organizations and user management beyond basic IAM.

My Takeaway: These practice exams are non-negotiable. Use them to identify knowledge gaps, get comfortable with the exam format, and leverage the explanations for targeted learning.

4. The Final Polish: Tutorials Dojo Study Guide eBook & Cheat Sheets

In the last few weeks leading up to my exam, I shifted gears from intensive learning to consolidation and review. The Tutorials Dojo Study Guide eBook (often bundled with the practice exams) and their online cheat sheets became my go-to resources.

These materials offer incredibly concise summaries of services, key concepts, and, most importantly, comparative tables. Struggling to remember when to use which S3 storage class or which database is best for a specific workload? These resources condense vast amounts of information into easily digestible formats, perfect for quick, effective revision. They helped me connect the dots and solidify the information for those less familiar topics like on-premise connectivity options.

My Takeaway: Leverage these resources for last-minute review, reinforcing key facts, and internalizing the differences between similar services.

Summary: A Journey of Growth and New Skills

Passing the AWS Certified Solutions Architect – Associate exam with a score of 903 was incredibly rewarding. Setting it as a yearly goal provided the perfect motivation to stay consistent over nine months. While my existing experience as a Web Engineer with services like DynamoDB, Lambda, and API Gateway gave me a strong foundation, the certification journey pushed me to explore far beyond my comfort zone. I delved into complex networking, different migration strategies, and the intricacies of AWS Organizations—areas I rarely touched in my daily work.

This structured preparation not only earned me a certification but genuinely deepened my understanding of cloud architecture. I feel much more confident in designing robust, scalable, and secure solutions. It was a significant learning experience that I believe will benefit my work for years to come.

If you're considering this certification, embrace the process. It's a significant investment of time, but the knowledge gained is invaluable. Good luck!

Comments

Post a Comment

Popular posts from this blog

Modern API Development with TypeSpec and OpenAPI

Designing robust and well-documented web APIs is a crucial part of modern software development. One of the most widely adopted standards for describing RESTful APIs is OpenAPI. It provides a machine-readable format—typically written in JSON or YAML—that defines the structure, endpoints, request/response formats, and other aspects of an API. This schema becomes a single source of truth, powering everything from interactive documentation to client libraries and server stubs. However, writing and maintaining OpenAPI specifications by hand can quickly become a chore. The syntax is verbose, and small mistakes in the structure can lead to frustrating bugs or inconsistencies across different parts of the system. This is where TypeSpec comes in. TypeSpec is a language developed by Microsoft for describing APIs in a more developer-friendly way. Instead of wrestling with raw OpenAPI YAML, you write a TypeSpec file that feels more like TypeScript: concise, expressive, and modular. From this s...
Read more

Introducing a Baby Chaos Monkey for Our Microservices

In complex systems built on a microservice architecture, resilience isn’t just a nice-to-have, it’s essential. One common approach to testing system robustness is Chaos Engineering, where you intentionally introduce failures to see how well your system recovers. Netflix’s Chaos Monkey is a famous example: it randomly kills services in production to ensure systems can handle failure gracefully. While that level of chaos might be overkill for most teams (especially outside of production), the core idea, testing your system’s response to failure, is invaluable. Inspired by this, we recently added a small but effective piece of middleware to one of our services: a manually triggered route-level failure tool that acts like a “baby Chaos Monkey.” Our infrastructure is composed of many interdependent microservices. Even small changes can have surprising ripple effects, especially when services rely on each other in subtle ways. This middleware gives us a lightweight, controlled way to simul...
Read more

Enabling TypeScript Strict Mode in a Legacy React Project—A Gradual Approach

Our App was created in 2017. It is a React application written in TypeScript. At the time, TypeScript was gaining popularity, but strict type safety wasn’t a major concern for most teams. Our knowledge of TypeScript was limited, and the primary goal was to use it for basic type annotations rather than enforcing a fully type-safe codebase. As a result, TypeScript’s strict mode was not enabled. This meant that the codebase lacked certain safeguards, such as strict null checks, no implicit any, and more rigorous type inferences. Over time, as the project grew in size and complexity, the lack of strict typing introduced subtle bugs and made refactoring riskier. Fast forward to today, the project has grown significantly. It now consists of approximately 2270 TypeScript files, making it a massive undertaking to migrate to strict mode. However, the benefits of enabling strict mode—better type safety, easier maintenance, and fewer runtime errors—outweighed the challenges. This blog post docu...
Read more