You failed. Your score report landed at 672. The AWS SysOps Administrator (SOA-C02) exam requires 720 to pass. You’re 48 points short. That gap is real, it’s fixable, and here’s exactly what it means and what you do next.
What Your Score Actually Means
That 672 isn’t just a number. It’s a percentile representation. The exam scores between 100 and 1000, but don’t think of it like a percentage. A 672 means you answered roughly 67-68% of the exam correctly. You’re competent in some areas. You’re weak in others. The score report you received breaks this down into domains.
The AWS SysOps Administrator (SOA-C02) exam has five domains:
- Monitoring, Logging, and Remediation (22% of exam weight)
- Reliability and Business Continuity (16%)
- Deployment, Provisioning, and Automation (18%)
- Security and Compliance (16%)
- Networking and Content Delivery (28%)
Your score report should list your performance in each domain as “Below Competency,” “Near Competency,” or “Competency Met.” If you scored 672 overall, you likely have domains where you’re “Near Competency”—meaning you’re in the 60-79% range for that section. That’s where the 48-point gap lives.
The 720 threshold exists because AWS tested this exam against real sysops professionals. They set the bar at a point where passing candidates can actually handle production systems. You’re not far away. You’re just not there yet.
The Real Reason You Failed AWS SysOps Administrator (SOA-C02)
You didn’t fail because you’re incompetent. You failed because you prepared for a different version of the exam than the one you took.
Here’s what happens: Candidates study broad AWS concepts. They memorize EC2 instance types. They learn about CloudWatch. They review IAM. Then they take the exam and face questions like this one:
Your company runs a critical application on EC2 instances across three availability zones in us-east-1. You implement CloudWatch alarms to monitor CPU utilization. An alarm triggers at 2 AM showing all three instances spiked to 95% CPU simultaneously. When you check the application logs, there’s no error. When you check the AWS Personal Health Dashboard, there’s a scheduled maintenance event starting in 30 minutes. What is the most likely cause, and what should you do in the next 15 minutes?
The correct answer isn’t “increase instance size.” It’s understanding that AWS maintenance can cause CPU spikes without application errors, and you should check the health dashboard first, then prepare failover to another region or AZ if needed. You need to think like someone running production systems under pressure—not someone memorizing definitions.
That’s domain-specific thinking. That’s what separates 672 from 720.
Most candidates who fail the AWS SysOps Administrator (SOA-C02) exam fail because:
- They didn’t practice with realistic scenario-based questions. They used flash cards instead of exam questions that simulate real incidents.
- They overlooked Networking and Content Delivery domain. This is 28% of the exam weight. If you scored “Below Competency” here, that’s your 48-point gap right there. VPC routing, security groups, NACLs, CloudFront, Route 53—these aren’t just concepts. The exam tests your ability to troubleshoot them under time pressure.
- They didn’t deeply understand the remediation part. Monitoring, Logging, and Remediation is 22% of the exam. The questions don’t just ask you to identify a problem. They ask what you do about it immediately. Can you use Systems Manager to patch 500 instances? Can you use OpsWorks or CloudFormation to roll back a bad deployment? Do you know when to use EventBridge versus SNS for remediation?
- They ran out of time or second-guessed themselves. The exam is 130 minutes for 50-65 questions. That’s roughly 2 minutes per question. If you spent 3 minutes on 10 questions, you rushed through the last 15.
Look at your score report again. Which domains show “Below Competency”? Start there.
What To Do In The Next 48 Hours
Don’t schedule your retake yet. Don’t buy another study guide. Do this:
Step 1: Get your score report breakdown (1 hour) Log into your AWS Certification Account. Download your score report PDF. It lists which domains you struggled with. If you don’t have this, you’re guessing. Stop guessing.
Step 2: Identify your weakest domain (30 minutes) You have five domains. One or two of them are dragging down your score. Write them down. This is your retake focus.
Step 3: Take a domain-specific practice test (2-3 hours) Use your existing study platform (Udemy, A Cloud Guru, Linux Academy, Whizlabs—whichever you used). Find practice tests that filter by domain. Take a full practice test focusing only on your weakest domain. Do it timed. Do it seriously. Write down every question you miss and why.
Step 4: Identify the gap (1 hour) Look at the questions you got wrong. Are they:
- Scenario-based problems where you didn’t know the right AWS service to use?
- Questions about specific configurations (security group rules, NACLs, VPC flow logs)?
- Questions about remediation steps you’ve never actually performed?
- Questions you rushed through because you ran out of time?
One pattern will emerge. That’s your actual problem. Not knowledge gaps. A specific type of thinking gap.
Your Retake Plan
You have 48 points to recover. That’s roughly 5-7 additional questions you need to get right. Not much. Here’s how to get there:
Week 1-2: Deep-dive your weakest domain If it’s Networking and Content Delivery, spend 10 hours studying VPC design, routing, security groups, and NACLs from an operational perspective. Use hands-on labs. Actually build a VPC. Actually create a security group and watch traffic fail, then fix it. Reading about it isn’t enough.
If it’s Reliability and Business Continuity, focus on RTO/RPO scenarios, backup strategies, and disaster recovery patterns. Study real failures on the AWS forums and understand what went wrong.
Week 2-3: Scenario-based drilling Stop taking full-length practice tests. Take 10-15 domain-specific scenario questions per day. Focus on:
- Questions where you had to choose between similar AWS services
- Questions about troubleshooting steps in a specific order
- Questions about configuration details that tripped you up
Week 3-4: Full practice tests Take two full-length practice tests under exam conditions. 130 minutes, no breaks except water. Use a timer. Track your time per question. If you’re averaging 3+ minutes per question, you need to practice speed without sacrificing accuracy.
Retake date: 28-35 days after your failed exam This gives you enough time to fix the gap without information decay. Don’t wait two months. The material will fade.
One Thing To Do Right Now
Stop what you’re doing. Log into your AWS Certification Account. Download your score report. Open it. Find the domain where you scored lowest. Write that domain name down.
Close this page. Open your study platform. Search for practice questions in that domain only. Take 5 questions right now, timed, like they’re real exam questions. Don’t look up answers as you go. Finish all 5, then check them.
See what you missed? That’s your starting point. Your retake isn’t in 30 days. It starts in the next 30 minutes.
You’re 48 points away. That’s not far. Get to work.