You failed. The score report says something below 720. Here’s exactly what that means and what you do next.
What Your Score Actually Means
The AWS SysOps Administrator (SOA-C02) exam uses a scaled score between 100 and 1000. Passing is 720. If you scored 680, that’s 40 points away. If you scored 710, that’s 10 points away. Both feel bad. Both mean the same thing: you weren’t ready yet.
A scaled score doesn’t directly map to percentage of questions correct. AWS doesn’t tell you that you got 65% right. What they tell you is: you demonstrated insufficient competency in one or more of the five domains tested on this exam.
Those domains are:
- Monitoring, logging, and remediation (26% of the exam)
- Reliability and business continuity (20%)
- Deployment, provisioning, and productivity (18%)
- Account and network management (18%)
- Security and compliance (18%)
Your score report shows which domains pulled you down. If you scored well in monitoring but poorly in account and network management, that’s your signal. Not “I failed the whole exam.” You failed specific topics.
Most candidates who retake SOA-C02 and pass scored between 750 and 850 on their second attempt. That’s a 30–130 point swing. It happens because they stop studying everything and start drilling what actually broke them.
The Real Reason You Failed AWS SysOps Administrator (SOA-C02)
You know the concepts. You probably do this work or something close to it. So why didn’t it translate to the exam?
Three reasons show up in almost every retake candidate.
First: You studied AWS services, not exam questions. There’s a difference. AWS SysOps tests you on CloudWatch alarms, Systems Manager, VPC configurations, and IAM policies. But the questions don’t ask “What is CloudWatch?” They ask “An application is throwing errors every 15 minutes. You need to be notified within 2 minutes. Which alarm configuration works?” The specifics matter. The threshold, the evaluation periods, the statistic type—you need all of it right.
Second: You didn’t practice under exam conditions. Exam questions don’t let you Google halfway through. You see a scenario about an EC2 instance failing health checks, and you have 90 seconds to pick the right answer from four plausible options. If your study method was “read the AWS docs,” your brain never learned the speed or the multiple-choice trap format.
Third: You skipped the weak domains. The score report told you what didn’t work. But instead of drilling those domains for three weeks straight, you probably went back to the topics you already knew. Easier. Faster. Wrong.
What To Do In The Next 48 Hours
Don’t retake the exam for at least 14 days. That sounds wrong when you’re frustrated, but it’s not.
Do this instead:
Get your score report in front of you. Write down the five domains and your estimated performance in each. AWS doesn’t give you exact percentages by domain, but the report usually indicates where you were weak. Put a star next to the bottom two.
Those two domains are your focus for the next two weeks. Not all five. Not the ones you’re comfortable with. The weak ones.
Next, buy or access one full practice exam platform. The best options are:
- Whizlabs (most detailed explanations, closest to real exam)
- Neal Davis’s A Cloud Guru course (includes 50+ scenario-based questions)
- TutorialsDojo (focused on tricky answer combinations)
Don’t buy all three. Pick one and commit. Sign up tonight.
Then identify exactly what you don’t know. Take a practice test in your weakest domain. If account and network management is your problem, run a 50-question practice test on VPC, IAM, and Route 53 only. Score it. Write down every question you got wrong and why.
That’s your next 48 hours. Score report + weak domains identified + one practice platform purchased + first focused practice test scheduled for day 3.
Your Retake Plan
You have 14 days. Here’s the structure.
Days 1–3: Take your first focused practice test in your weakest domain. Spend 4 hours minimum. Don’t rush. Read the explanations for every answer, even the ones you got right. Note patterns. Example: if three questions about Systems Manager Session Manager tripped you up, you have a Session Manager gap.
Days 4–7: Study only the topics that broke you. Not the whole service. The specific features and configurations that show up on the exam. If you failed questions on CloudWatch composite alarms, spend an hour on composite alarms—how they work, the JSON syntax, when to use them. Then take 20 targeted practice questions on that topic. Repeat for each gap.
Days 8–11: Take a second full practice exam in your weak domains. You should see improvement. If you don’t, go back to that specific topic and drill it harder.
Days 12–13: Take a full-length SOA-C02 practice exam under real conditions. 130 minutes, no breaks, no distractions. Score it. Review only wrong answers. If you’re hitting 750+, you’re ready. If you’re 720–745, take one more day and drill that weakest subdomain again.
Day 14: Rest. Don’t study. Your brain needs sleep more than it needs more information.
Day 15: Take the exam.
This plan works because it’s not about learning AWS again. It’s about closing the 40 points between you and passing.
One Thing To Do Right Now
Pull up your AWS SysOps Administrator (SOA-C02) score report right now. If you haven’t saved it, log into your Pearson Vue account and download the PDF.
Find the section that breaks down your performance by domain. Write the domains on a piece of paper. Circle the two lowest ones.
That’s your retake focus. Not “I need to study more.” Not “I need to read the docs again.” Your next two weeks are about mastering those two domains at the question level.
Do that now. Spend 10 minutes on it. It changes everything about how you study next.
You didn’t fail because you’re not capable. You failed because your study method didn’t match the exam format. That’s fixable in 14 days.