The AWS SysOps Administrator (SOA-C02) is the operations cert. It's the one that asks whether you can keep things running, not just stand them up. That focus makes it different from the other associate exams, and it's why people who breeze through Solutions Architect sometimes stumble here.
I'll walk through what's actually on it, who should take it, and where people lose points.
What this cert is
SysOps is an associate-level cert aimed at people who operate and monitor workloads on AWS. Think deployment, monitoring, logging, automation, cost control, and fixing things when they break.
The framing matters. Solutions Architect asks "how would you design this." SysOps asks "it's running and something's wrong, what do you do." A lot of the questions are written from the point of view of someone on call.
The exam is 65 questions, 130 minutes, multiple choice and multiple response. You need roughly 720 out of 1000 to pass, and the score is scaled, so don't count exact questions.
The thing that makes SOA-C02 different
SOA-C02 has historically included exam labs - hands-on tasks in a live AWS console where you actually do the work. AWS has paused and resumed these over the cert's life, so check the current exam guide on the AWS site before you book. If labs are active, plan for them. They're the part people are least ready for, because you can't memorize your way through clicking around a real console under time pressure.
Even if labs aren't active when you sit it, study as if they are. Doing the tasks by hand is the best way to learn this material anyway.
What's actually on it
The domains shift slightly between exam versions, but the weight lands on these areas:
- Monitoring, logging, and remediation. CloudWatch is the heavy hitter here. Metrics, alarms, dashboards, Logs, and the difference between a metric, a log, and an event. CloudTrail for audit history. Knowing when to use CloudWatch Alarms versus EventBridge rules to trigger an action.
- Reliability and continuity. Auto Scaling groups, health checks, multi-AZ versus multi-region, RDS read replicas and failover, backups, and snapshots. Expect questions where the answer is "the simplest thing that survives one AZ going down."
- Deployment and automation. CloudFormation is core - reading templates, understanding stacks, change sets, drift, and what happens on rollback. Systems Manager shows up a lot too: Parameter Store, Session Manager, Run Command, Patch Manager.
- Security and compliance. IAM policies and roles, the difference between identity and resource policies, KMS basics, security groups versus network ACLs, and how to investigate "why can't this thing talk to that thing."
- Networking and content delivery. VPC fundamentals, subnets, route tables, NAT, VPC endpoints, and enough Route 53 and CloudFront to answer routing and caching questions.
- Cost and performance. Reading Cost Explorer, budgets and alerts, right-sizing instances, and picking storage tiers.
If I had to name the single most tested service, it's CloudWatch. The second is probably Systems Manager. Both reward hands-on time far more than reading.
Who should take it
SysOps is the right cert if you:
- Run things in production - DevOps, SRE, platform, or a developer who's also on call.
- Already have Solutions Architect Associate and want to round out the operations side.
- Spend your day in the console fixing alarms, scaling groups, and broken deploys.
It's the wrong first cert if you've never touched AWS. Start with Cloud Practitioner for the mental map, then come here once you've actually operated something.
Where people lose points
A few patterns show up again and again:
- They study like it's Solutions Architect. SysOps wants the operational fix, not the elegant design. Read each question asking "what's the fastest, safest action," not "what's the best architecture."
- They're shaky on CloudFormation internals. Knowing what a template is isn't enough. You need to know what drift is, what a change set shows you, and what gets rolled back on failure.
- They've never used Systems Manager. It's underrated and overtested. Spend an afternoon in Session Manager and Parameter Store. It pays off.
- They skip the hands-on. This is the cert where reading slides the night before genuinely doesn't work. The labs and the scenario questions both punish people who haven't done the tasks.
How I'd study for it
Give it four to eight weeks depending on your experience. A rough plan:
- Read the official exam guide first and note whether labs are active.
- Get a free-tier account and build a small live setup: a couple of EC2 instances behind an Auto Scaling group, a CloudWatch alarm that triggers something, a CloudFormation stack you can update and watch roll back.
- Break things on purpose and fix them. Stop an instance, fail a health check, deny a permission, then trace it.
- Do practice questions for coverage, but treat your console time as the real study.
That console-and-break-things loop is the whole game. If you can calmly diagnose a broken setup under a little time pressure, you're ready - and that's a skill worth practicing out loud, the same way you'd rehearse for an interview.
SysOps won't make you a better architect. It'll make you the person who's trusted when something is on fire at 2am. For a lot of teams, that's the more valuable reputation.