How to Actually Prepare from Marek’s Course for AWS SAA – A Realistic Guide

If you’re reading this, you’ve probably already bought Stephane Maarek’s Ultimate AWS Certified Solutions Architect Associate course — or you’re about to. It’s the highest-rated and most-recommended resource for the SAA-C03 exam, and for good reason. The course is dense, clear, and packed with the exact mental models you need to think like an architect.

But “I watched all the videos” is **not** a study strategy. Over on Reddit’s r/AWSCertifications, the most common post-exam regret is: *“I rushed through Marek’s course and bombed the practice tests.”*

The exam doesn’t test recall; it tests trade-off thinking. So here’s how to **actually** use Marek’s course to become exam-ready — the way the people who pass do it.

The Architecture of a Study Plan

Before you hit play, understand the anatomy of the SAA exam:

65 questions (50 scored, 15 unscored)

Multiple choice and multi-response

130 minutes

Pass mark ≈ 720 / 1000

Marek’s course (as of early 2025, with 500,000+ students and a 4.7 rating on Udemy) gives you **~28 hours of video**, 3 full-length practice exams, code demos, and a downloadable slides. Its structure maps to the AWS exam domains:

1. Design Secure Architectures (30%)

2. Design Resilient Architectures (26%)

3. Design High-Performing Architectures (24%)

4. Design Cost-Optimized Architectures (20%)

So a real preparation isn’t a linear watch-through. It’s a **three-phase loop**.

The Three-Phase Preparation Model

Phase 1: Layering Knowledge with the Video Course

Goal: Build a mental map of AWS services, not memorize bullet points.

Watch sections in order, but never more than **2 hours a day** (attention fatigue will sandbag your retention).

After every 3–4 lectures, **take 10 minutes and reproduce the architecture on paper** (VPC with public/private subnets, CloudFront with OAI, etc.). Active recall > re-watching.

Use Marek’s “Exam Tips” slides as your daily flashcard stack.

For high-weight services (EC2, S3, RDS, DynamoDB, Lambda, IAM, VPC, Route 53, Auto Scaling, CloudFront, SQS, SNS, Step Functions), **build a mini-cheatsheet** that captures limits, features, and integration points.

Real-world citation: Many Redditors who scored 900+ reported doing **at least one full pass of the course at 1.25–1.5x speed**, but only after they’d taken a diagnostic practice exam first to calibrate what they didn’t know.

Phase 2: Drill and Associate Services

Goal: Move from “what is this service?” to “which service for which scenario?”

Run through Marek’s hands-on demos. **Don’t just watch — break them.** Create an S3 bucket with a bad bucket policy and deliberately trigger an Access Denied. Launch an EC2 instance in a public subnet without an Internet Gateway and debug why you can’t SSH. Painful mistakes turn into exam intuition.

Create **comparison tables** for sibling services: SQS Standard vs. FIFO, EBS volume types, Encryption options (SSE-S3, SSE-KMS, SSE-C), etc. Marek’s course shows the differences; you need to internalize them.

Start interleaving: spend 20 minutes on a domain, then switch to a different domain (e.g., networking -> storage -> security). The exam is a context switcher’s nightmare, so train your brain to pivot fast.

Phase 3: Practice Exam Gauntlet and Review

Goal: Simulate exam pressure and close knowledge gaps.

**Take Marek’s first practice exam after you’ve watched 100% of the course.** Score doesn’t matter; gaps do.

For every wrong answer, open the corresponding lecture and watch the **specific 2–3 minute clip** that explains the concept. Don’t re-watch whole sections.

Supplement with **Tutorials Dojo / Jon Bonso’s practice tests** — the consensus on r/AWSCertifications is that Marek’s tests are good for comprehension, but Bonso’s are closer to the actual exam’s tricky wording and long-winded scenarios.

Space your practice exams: one every 3–4 days. Review in between. Your scores should trend upward; if they plateau, you’re memorizing answers, not understanding the *why*.

A day before the exam, take one last full practice test under realistic conditions (no pausing, no phone). Then stop. Night-before cramming is a myth for an exam this broad.

Common Pitfalls and Reddit-Wisdom

**The “I’ll just take it and see” trap:** The SAA-C03 is $150 per attempt. Treat it like an architect would treat a production launch — don’t guess at readiness.

**Ignoring the “Cost-Optimized” domain:** It’s easy to feel confident about designing highly available systems with unlimited budget. But the exam won’t let you ignore reserved instances, S3 Intelligent-Tiering, or Compute Savings Plans. Marek’s cost sections are short; dig deeper into the AWS Cost Explorer and Budgets if you’re weak here.

**Neglecting the “Wrong Answers” analysis:** The SAA is a reading-comprehension exam disguised as a cloud test. Two answers are often technically correct. You must pick the one that satisfies the requirements *and* the constraints (most secure, least operational overhead, most cost-effective). Review Marek’s *explanation* of why answers are wrong, not just the correct one.

**Not using the official AWS exam guide:** Marek’s course is comprehensive, but AWS occasionally adds new service questions (e.g., AWS Outposts family, AWS DataSync, more AWS Organizations scenarios). Cross-reference the [official SAA-C03 guide](https://aws.amazon.com/certification/certified-solutions-architect-associate/) in your final two weeks.

What Success Looks Like

When you can look at a scenario and immediately discard services that don’t fit the well-architected pillars — *“No, EFS won’t work here because we need multi-AZ shared block storage; that’s FSx for Windows File Server”* — you’re ready. Marek’s course gives you the vocabulary; your deliberate practice builds the fluency.

After passing, you’ll notice something interesting: the habits you developed (active recall, error budget thinking, and cost-first design) are exactly what make you a better cloud engineer. That’s the real certification.

If you need a place to test your architectures before deploying to AWS, [sign up for Sapior’s early access](https://sapior.com) — we help developers iterate on cloud-native apps without provisioning real infrastructure until you’re confident.

*The best AWS architects aren’t the ones who know all the services. They’re the ones who know which 3 services actually solve the problem. Marek’s course makes that clarity possible — if you do the work.*