AWS Solutions Architect Professional Study Plan 30 Days: Week by Week

Let's get one thing straight before you read another word of this AWS Solutions Architect Professional study plan 30 days guide: 30 days is aggressive, not insane, and only works if you're not starting from zero. If you've already got a year or two of hands-on AWS and passed the Associate exam, this timeline is realistic at 2-3 hours on weekdays and 4-5 on weekends. If you're brand new to AWS, close this tab and go do SAA-C03 first. I'm not going to pretend otherwise.

Here's the exam you're prepping for, in plain numbers (full breakdown on the AWS Solutions Architect Professional exam page if you want to bookmark it): 75 questions, 180 minutes, passing score 750 out of 1000, and it'll run you $300 to sit. Reddit threads put the first-attempt pass rate somewhere in the 35-45% range across all comers, with well-prepared candidates doing meaningfully better, closer to 55-65%. Translation: the people who fail mostly failed on prep, not luck.

Four domains carry the exam:

• Domain 1: Design Solutions for Organizational Complexity (26%)
• Domain 2: Design for New Solutions (29%)
• Domain 3: Continuous Improvement for Existing Solutions (25%)
• Domain 4: Accelerate Workload Migration and Modernization (20%)

Notice Domain 2 is the biggest single chunk. That's your priority week.

Week 1: Rebuild your foundation (10-12 hrs)

You're not learning AWS from scratch, you're re-anchoring services you already know into professional-level thinking: multi-account, org-wide, cost-and-governance-aware.

Mon-Fri (2 hrs/day):

• [ ] Re-read AWS Organizations, SCPs, Control Tower, and multi-account landing zone patterns
• [ ] Go deep on AWS Transit Gateway, Direct Connect, VPN, and hybrid connectivity. This shows up constantly
• [ ] Review IAM at scale: permission boundaries, resource-based policies, cross-account roles
• [ ] Skim the official SAP-C02 exam guide domain-by-domain, mark what's unfamiliar

Weekend (4-5 hrs each):

• [ ] Build a small multi-account sandbox if you can (even 2 free-tier accounts under an Org)
• [ ] Do a domain-1 practice set, don't worry about your score yet, just get the question rhythm

By Sunday you should be able to sketch a landing zone diagram from memory. If you can't, that's fine. That's what week 2 is for.

Week 2: Design for New Solutions, the biggest domain (12-14 hrs)

This is 29% of your score, so it gets the most hours. Domain 2 is where AWS tests whether you can architect from a blank slate: high availability, resilience, security, and performance for greenfield systems.

Mon-Fri (2.5 hrs/day):

• [ ] Multi-region active-active vs active-passive tradeoffs, and when each is actually justified
• [ ] Database architecture: Aurora Global Database, DynamoDB Global Tables, read replicas, when RDS vs DynamoDB vs Redshift
• [ ] Event-driven architecture: EventBridge, SQS, SNS, Step Functions, and how they compose
• [ ] Serverless-at-scale patterns: Lambda concurrency, API Gateway throttling, cold start mitigation

Weekend:

• [ ] Take a full 75-question timed practice exam. Don't review yet, just get the exam-length stamina.
• [ ] Then go back through every wrong answer and write down WHY the correct option won, not just what it was

That second step matters more than the score itself. If you're only tracking your percentage, you're not learning the exam, you're just anxious about it.

Week 3: Split between Continuous Improvement and Migration (12-14 hrs)

Domains 3 and 4 combined are 45% of the exam, so don't shortchange this week just because they sound less exciting than "design new solutions."

Mon-Wed: Domain 3, Continuous Improvement (25%)

• [ ] Cost optimization at scale: Savings Plans vs Reserved Instances, Compute Optimizer, rightsizing
• [ ] Operational excellence: CloudWatch, X-Ray, AWS Config, automated remediation
• [ ] Reliability improvements to existing workloads: chaos-style failure testing, DR strategies (backup/restore, pilot light, warm standby, multi-site)

Thu-Fri: Domain 4, Migration and Modernization (20%)

• [ ] Migration strategies: the 6 R's (rehost, replatform, refactor, repurchase, retire, retain)
• [ ] AWS Migration Hub, Application Migration Service, Database Migration Service
• [ ] Modernizing monoliths toward containers/serverless, and what triggers each choice

Weekend:

• [ ] Second full practice exam. Compare your domain-by-domain breakdown to week 2's exam. You should see Domain 3 and 4 scores climbing
• [ ] Rebuild your weakest domain's notes from scratch, don't just reread old notes, write new ones cold

Week 4: Mixed review, weak-spot triage, and exam logistics (10-12 hrs)

No new material this week unless a practice test exposes a real gap. This week is about pattern recognition under time pressure, not content acquisition.

Mon-Wed:

• [ ] Two more timed practice sets, mixed-domain, review every wrong answer same-day while it's fresh
• [ ] Build yourself a one-page cheat sheet of the patterns you keep confusing (Aurora Global vs DynamoDB Global Tables trips up almost everyone at this stage)

Thu-Fri:

• [ ] Light review only, no new content, no cramming a fifth full exam
• [ ] Confirm exam logistics: online proctoring rules or testing center ID requirements, since SAP-C02 has stricter check-in than the associate exams

Weekend before exam:

• [ ] One final lighter review pass, half a day max
• [ ] Rest. Seriously. A tired brain reads distractors wrong more than an underprepared one does.

The reality check on cost

You're already paying $300 just to sit this thing, so don't blow another few hundred on practice material bundles that overlap 80% with what you covered in Associate-level prep. I lean on ExamCert for the professional-level question bank specifically because it's $4.99 for lifetime access with a money-back guarantee instead of the usual $300 competitor pricing for what's basically the same content repackaged.

If you want to gut-check where you actually stand before committing to this whole 30-day plan, run a free SAP-C02 practice test first. If you're scoring under 50% cold, budget for 6 weeks instead of 4. There's no prize for rushing a $300 exam you're not ready for.

Quick reference: hours by week

Week	Focus	Hours
1	Foundation, multi-account, networking	10-12
2	Design for New Solutions (29%)	12-14
3	Continuous Improvement + Migration	12-14
4	Mixed review, weak-spot triage	10-12
Total		~46-52 hrs

That lines up with what most people report needing on top of existing AWS experience. If you're starting cold, double it and stretch the plan to 8 weeks instead of forcing 30 days that won't stick.

Good luck. Read the ask in every question, not just the scenario, and you'll be fine.