I walked out of the testing center thinking I'd passed. I'd been working with AWS for two years. I knew EC2. I knew S3. I'd shipped Lambda functions in production. Surely 130 minutes and 65 questions couldn't catch me off guard.
My score: 671. The pass mark is 720.
That number sat with me for a week. Not out of embarrassment — I've shipped code with bugs, I've had deploys go sideways at 2am — but because I couldn't immediately identify where I'd gone wrong. That gap between "I use AWS at work" and "I can pass SAA-C03" turned out to be real, and wider than I expected.
Here's what I learned the hard way, and what I changed to score 756 on the retake six weeks later.
Where I Went Wrong the First Time
My first mistake was assuming that hands-on experience would carry me. It won't — at least not alone. The SAA-C03 isn't testing whether you can write a CloudFormation template. It's testing whether you can read a scenario and pick the most appropriate architecture given specific constraints: cost, availability, recovery time, compliance. Those are subtly different skills.
The exam covers four domains:
- Design Secure Architectures — 30% of your score
- Design Resilient Architectures — 26%
- Design High-Performing Architectures — 24%
- Design Cost-Optimized Architectures — 20%
Security and resilience together make up 56% of the exam. I had treated them as roughly equal to the rest. They're not.
My second mistake: I'd never done timed practice under exam conditions. I'd read whitepapers. I'd watched videos. But reading and watching is passive. The actual exam gives you an average of 2 minutes per question, and some scenarios run 150+ words before you even get to the options. Speed matters.
What I Changed for the Retake
1. I Started Doing SAA-C03 Practice Exams Seriously
This was the single biggest shift. Not watching more videos — actually sitting down and doing timed SAA-C03 practice exams with full question sets, reviewing every wrong answer, and understanding why the correct answer was correct.
I used ExamCert's SAA-C03 practice tests for a chunk of my prep. The questions are scenario-based in a way that matches the real exam's style — you're not getting "what does S3 stand for," you're getting "a company needs to store 10TB of infrequently accessed compliance data with legal hold requirements, which storage class and which feature should they use." That's the kind of question where you need to know the difference between S3 Glacier Instant Retrieval, Glacier Flexible Retrieval, and S3 Object Lock — not just that Glacier is "cold storage."
If you want to test yourself before committing to a study plan, the free AWS SAA practice test is worth doing first. It'll quickly surface the domains where you're actually weak.
2. I Got Specific About the Services That Appear Constantly
The exam hits a core set of services hard. These aren't edge cases — they're the backbone of most questions:
Networking and security:
- VPC: subnets (public vs private), route tables, NAT gateways, VPC peering, Transit Gateway, PrivateLink
- Security groups vs NACLs — stateful vs stateless, which one blocks by default
- IAM: roles vs policies, resource-based vs identity-based, SCP scope in AWS Organizations
Compute:
- EC2: instance types matter less than placement groups (cluster, partition, spread) and when to use Reserved vs Spot vs On-Demand
- Auto Scaling: cooldown periods, target tracking vs step scaling, lifecycle hooks
- ELB: ALB vs NLB vs GWLB — not the same, and the exam will make you choose
Storage:
- S3: storage classes and their retrieval times/costs, lifecycle policies, versioning, replication (CRR vs SRR), Transfer Acceleration
- EBS: gp3 vs io2, RAID configurations, snapshots across regions
- EFS vs FSx — when you need shared filesystem access vs Windows workloads
Databases:
- RDS Multi-AZ vs Read Replicas — Multi-AZ is for failover, Read Replicas are for read scaling. Confusing these will cost you points.
- Aurora: global databases, serverless v2, backtrack feature
- DynamoDB: on-demand vs provisioned, DAX for caching, Global Tables for multi-region
Application integration:
- SQS: standard vs FIFO, visibility timeout, dead-letter queues
- SNS: fan-out pattern with SQS
- EventBridge for event-driven architectures
- Lambda: concurrency limits, reserved concurrency, layers, destinations
Content delivery and DNS:
- CloudFront: origin groups for failover, signed URLs vs signed cookies, Lambda@Edge
- Route 53: routing policies — simple, weighted, latency-based, failover, geolocation, geoproximity
3. I Built Mental Frameworks for Common Question Patterns
SAA-C03 questions often follow recognizable patterns. Once you've seen enough of them, you start spotting the cues:
- "Minimum operational overhead" — usually points toward managed services (RDS over self-managed MySQL, SQS over custom queue, Aurora Serverless over provisioned Aurora)
- "Most cost-effective" — think Reserved Instances, Spot for fault-tolerant workloads, S3 Intelligent-Tiering, rightsizing
- "Highly available across Availability Zones" — multi-AZ RDS, ALB across AZs, Auto Scaling groups spanning multiple AZs
- "Disaster recovery" — know your RPO/RTO tradeoffs: backup/restore vs pilot light vs warm standby vs multi-site active/active
The question is almost always asking you to balance two of these. A solution might be highly available but not cost-optimized. Your job is to pick the one that satisfies the stated constraint, not the one that satisfies all constraints simultaneously.
4. I Stopped Cramming and Started Reviewing
After each practice set, I spent more time on wrong answers than on new questions. For every question I missed, I wrote down:
- What I thought the answer was and why
- What the correct answer was and why
- The specific AWS feature or behavior I'd misunderstood
That review log became more valuable than any study guide. By week four, patterns in my mistakes were obvious — I kept confusing NLB and ALB use cases, and I kept underweighting the "lowest cost" requirement in cost-optimization questions.
The Retake
Six weeks after the first attempt, I sat back down. The questions felt different — not because they were easier, but because I was reading them differently. I was looking for the key constraint first, then eliminating answers that violated it, rather than trying to find the "best" answer in the abstract.
Final score: 756.
The exam costs $150, and you don't want to sit it twice if you can avoid it. The prep investment is worth front-loading. Do the free SAA-C03 practice questions early, figure out where your gaps actually are, and then go deep on those domains specifically.
If you're already working with AWS professionally, you have more foundation than you think. You just need to close the gap between "I've used this service" and "I understand exactly when and why to use it over the alternative." That's what the SAA-C03 is actually testing.
Good luck. The 720 pass mark isn't a high bar — it just requires genuine preparation.
Top comments (0)