AWS Certified SysOps Administrator – Associate (SOA-C02): Status, Scope, and Preparation Decisions
AWS Certified SysOps Administrator – Associate (SOA-C02) validated operational AWS skills: monitoring workloads, applying security and networking controls, supporting continuity, and improving cost and performance. It suited administrators with hands-on AWS responsibilities, especially candidates with experience deploying and managing services. The key decision now is not how to book SOA-C02: AWS replaced it with SOA-C03, so this guide helps former SOA-C02 candidates transfer useful study work to the current CloudOps Engineer path.
Can you still take SOA-C02?
No. AWS states that SOA-C02 was replaced by AWS Certified CloudOps Engineer – Associate (SOA-C03) beginning September 30, 2025, and that September 29, 2025 was the last day to take SOA-C02. Do not build a schedule, purchase preparation material, or set a booking target around an SOA-C02 attempt.
If you arrived with a partly completed SOA-C02 plan, retain the operational knowledge rather than treating the work as lost. The AWS comparison identifies substantial continuity in monitoring, reliability, deployment, security, and networking. However, the current exam has its own content outline and weighting, so transfer the concepts and then rebuild your checklist against the current AWS guide before deciding that a topic is complete.
This distinction matters when selecting resources. A course, practice set, or article carrying only the SOA-C02 code may be useful for background but cannot by itself establish readiness for the active certification. Check that every resource identifies its exam code and compare its stated scope with AWS documentation.
What SOA-C02 was designed to validate
SOA-C02 was an Associate-level AWS certification focused on operating workloads, not merely recognizing AWS service names. AWS described the validated skills as monitoring and maintaining workloads, implementing security controls and networking concepts, performing business-continuity procedures, and optimizing cost and performance.
That focus made the credential relevant to people whose work involved keeping AWS environments observable, available, controlled, and efficient. The useful mental model is an operations scenario: identify a condition, gather evidence, choose an appropriate control or corrective action, and consider the effect on reliability, security, network behavior, and cost.
For study purposes, avoid organizing notes as disconnected product definitions. Instead, use operational prompts. For example: What signal would reveal a problem? What configuration should be checked? What recovery or remediation goal is being served? Which constraint—security, availability, latency, or cost—changes the best choice? This approach builds decision-making discipline without relying on recalled exam items.
Who the certification fit best
AWS described the ideal SOA-C02 candidate as having one year of experience with deployment, management, networking, and security on AWS. That is a practical benchmark for deciding whether to study directly for an operations-focused Associate exam or first close gaps through structured AWS practice.
Candidates who are strongest in a single area should diagnose their blind spots early. A systems administrator may be comfortable with monitoring and day-to-day changes but need more practice connecting controls to compliance and continuity. A networking-focused candidate may need to spend more time on workload operations, logging, remediation, and cost-performance decisions. A developer can use the objective as an operations complement, but should not assume application deployment experience covers administration responsibilities.
Prior training was recommended by AWS but was not mandatory for an AWS Certification exam. Treat training as one possible learning vehicle, not evidence of readiness. A more useful readiness signal is whether you can explain why an operational choice fits a stated condition and can identify what evidence would make you reconsider it.
How the SOA-C02 blueprint was weighted
The former blueprint concentrated most scored coverage in operations domains, with monitoring receiving the largest stated share. Use these weights only to understand the historical SOA-C02 emphasis; candidates pursuing certification now should use the current SOA-C03 blueprint for final planning.
Monitoring, Logging, and Remediation accounted for 20% of SOA-C02. Reliability and Business Continuity accounted for 16% of SOA-C02. Deployment, Provisioning, and Automation accounted for 18% of SOA-C02. Security and Compliance accounted for 16% of SOA-C02. Networking and Content Delivery accounted for 18% of SOA-C02. Cost and Performance Optimization accounted for 12% of SOA-C02.
A sound historical study sequence follows operational dependency rather than attempting to memorize in weighting order. Start with observation and remediation, then move into reliability decisions and automated deployment. Add security and networking as controls and connectivity constraints around those workloads. Finish by revisiting cost and performance optimization across the earlier scenarios, because optimization decisions are more meaningful once the operational baseline is clear.
A common planning error is to give the smallest domain almost no attention. Cost and Performance Optimization was 12% of SOA-C02, but the underlying judgment appears throughout real operations: an apparently cheap option can create an availability, security, or observability problem, while an overbuilt option can add unjustified cost. Study each domain to functional competence before allocating revision time by weighting.
What changed when AWS moved to SOA-C03
The successor is not simply a renamed SOA-C02 exam. AWS documents additions, a deletion, and moved content, so candidates should use the change list to identify which older notes need expansion or reassessment.
For SOA-C03, AWS added creating and managing resource stacks with CloudFormation and the AWS CDK in Task 3.1. AWS also added enforcement of compliance requirements, including Region and service selections, in Task 4.1. These additions are a clear reason not to rely exclusively on an older automation or security study plan.
AWS added configuration and analysis of CloudWatch network monitoring services in Task 5.3. It removed configuration of S3 static website hosting from Task 5.2. VPNs moved from Task 4.2 to Task 5.1, and former SOA-C02 Tasks 6.1 and 6.2 moved to Task 1.3 in SOA-C03. Moving content does not make the capability irrelevant; it changes the operational context in which AWS organizes it.
Make a two-column transition inventory. In the first column, record each SOA-C02 topic you have actually studied or practiced. In the second, mark it as retained, expanded, moved, removed, or unknown under the current outline. “Unknown” is valuable: it prevents an old course outline from silently becoming your current blueprint.
Build preparation around operational decisions
Use scenario-based practice that requires diagnosis, trade-off reasoning, and verification, because the certification objective concerns running AWS workloads. The aim is to connect monitoring, security, networking, continuity, deployment, and optimization into a coherent operating model.
Create a small set of recurring scenario cards rather than a large unstructured notebook. One card might describe a workload with an unexplained service condition and ask for the monitoring evidence, remediation objective, and follow-up check. Another might present a deployment change and require you to identify the automation, security, network, and continuity questions that should be resolved before and after the change. Write your own answers in complete sentences, then correct them using official documentation.
For each topic, maintain three fields: the operational goal, the AWS capability or configuration category involved, and the proof that the intended state is being achieved. This reduces a common mistake: knowing that a service exists without being able to say what problem it solves or how an administrator would confirm its result.
Hands-on work should have a deliberately narrow purpose. Choose a configuration or workflow, set a desired observable outcome, make the change, and record what you checked afterward. Do not confuse clicking through a console path once with operational competence. The useful learning occurs when you explain the state before the change, the intended state after it, and the signal that distinguishes success from failure.
A practical study roadmap
Start with a diagnostic and progress through connected operations scenarios, then reserve the final phase for current-exam alignment and weak-area repair. The schedule length should reflect prior AWS experience and available study time, not an arbitrary calendar target.
First, map your baseline against the former six SOA-C02 domains and the current SOA-C03 outline. Mark each item as confident, partly understood, or untested. “Confident” should mean you can explain the operational outcome and a verification method; it should not mean you recognize the terminology. Place the untested items into a separate backlog so they are not hidden by familiar material.
Next, study Monitoring, Logging, and Remediation alongside Reliability and Business Continuity. Practice translating a vague operational symptom into the evidence you would seek, the remediation aim, and the continuity consequence. This gives later security, networking, and automation topics a real workload context instead of leaving them as isolated configuration exercises.
Then work through Deployment, Provisioning, and Automation with Security and Compliance. Ask what a repeatable deployment should preserve, what controls constrain it, and how a change can be verified after release. For the current exam path, explicitly include the SOA-C03 addition covering resource stacks through CloudFormation and the AWS CDK and the addition concerning compliance requirements.
Follow with Networking and Content Delivery, including the SOA-C03 addition involving CloudWatch network monitoring services. Tie networking decisions back to observable behavior and workload outcomes. Also revisit the AWS reorganization of VPN content rather than assuming that a topic’s prior SOA-C02 location represents its current context.
Use the final review stage for Cost and Performance Optimization and cross-domain scenarios. Review missed questions or failed explanations by cause: missing concept, misread requirement, weak comparison of options, or inability to identify verification evidence. Repair the cause, then redo a similar scenario from scratch. Repeating an answer until it looks familiar is not the same as being able to reason through a new condition.
Before scheduling the active exam, conduct a final source audit. Confirm the exam code, current content outline, registration information, and any policies directly through AWS. This step is particularly important for candidates who began studying under SOA-C02 because the successor’s additions and reorganized content change what a complete plan requires.
Avoid common preparation mistakes
The highest-value correction is to stop treating an obsolete code as a bookable target. A strong study routine can still fail as a certification plan if it is matched to the wrong exam version.
Do not use the historical SOA-C02 domain percentages as the current exam’s scoring model. AWS published those percentages for SOA-C02, while the comparison documentation identifies a revised SOA-C03 structure. Historical weights can guide what older material emphasized, but they cannot replace the current guide.
Avoid collecting practice questions without an error-review system. A wrong answer is useful only when you identify the decision point you missed. Write down the requirement that mattered, the assumption that led you astray, and the evidence that should have changed your decision. If you cannot explain that chain, more question volume is unlikely to fix the gap.
Do not depend on exam dumps, purported leaked material, or answer memorization. They do not build operational judgment, may be inaccurate or outdated, and are especially unsuitable when the published exam content has changed. Use legitimate practice to test reasoning against the current scope, then return to authoritative material when an explanation is uncertain.
Finally, do not schedule solely because a course is complete. Schedule when your current-outline checklist has no unexamined gaps, you can work through cross-domain operational decisions without relying on prompts from notes, and your administrative plan has been confirmed in the AWS Certification account.
Historical SOA-C02 delivery details
These details describe the retired SOA-C02 exam and should not be assumed to apply to the current successor. AWS listed SOA-C02 as 65 multiple-choice or multiple-response questions with a duration of 130 minutes.
AWS listed the SOA-C02 exam cost as USD 150. Its listed languages were English, Japanese, Korean, and Simplified Chinese. AWS listed a Pearson VUE testing center and an online-proctored exam as testing options. AWS also states that most online-proctored appointments are available 24 hours a day, seven days a week, subject to the scheduling process and availability.
For any live booking, verify all delivery details on AWS rather than using this historical information. Exam formats, languages, prices, appointments, and policies can change, and SOA-C02 itself is no longer the active exam. The practical action is simple: locate the current SOA-C03 certification page and read the current registration and testing information before choosing a date or location.
How scheduling and retake rules affect planning
Plan certification administration separately from technical study. AWS directs candidates to sign in to aws.training, open the AWS Certification Account, select Schedule New Exam, and choose Schedule at Pearson VUE; use that workflow for the active certification rather than attempting to locate an SOA-C02 appointment.
AWS states that a candidate who fails a certification exam must wait 14 calendar days before retaking it. AWS also states that there is no limit on attempts, but the full registration fee must be paid for each attempt. These rules make a diagnosis-led first attempt more sensible than a rushed attempt based on partial coverage.
Before selecting an appointment, confirm that the active exam code appears in your account and that the appointment mode fits your circumstances. If considering online proctoring, review AWS and Pearson VUE requirements directly during scheduling rather than assuming that a prior online exam setup will be sufficient. If using a testing center, verify the available location and appointment details at the time of booking.
Set a final decision checkpoint before payment: current exam code confirmed, current outline reviewed, gaps documented, intended testing option checked, and contingency time reserved in case a retake is needed. This checklist is more useful than setting a date first and forcing the study plan to fit it.
Choose your next action
Candidates who intended to take SOA-C02 should now pivot to AWS Certified CloudOps Engineer – Associate (SOA-C03), preserving relevant operational study while replacing the retired blueprint with the active one. The immediate next action is to download or review the current AWS exam guide and make a transition inventory.
If you are early in your AWS learning, use the former SOA-C02 scope as a map of operational responsibilities and build experience across deployment, management, networking, and security. If you already have that foundation, focus on the documented SOA-C03 additions and content reorganizations before testing yourself with current, legitimate preparation material.
Keep the final decision evidence-based. AWS’s historical SOA-C02 page explains the skills that credential validated, while the comparison guide explains why an older plan needs updating. The current exam guide and AWS Certification Account should be the sources that determine what you study next and what you schedule.
Conclusion
SOA-C02 remains useful as a description of AWS operations skills, but it is no longer an exam to schedule. Carry forward its monitoring, reliability, automation, security, networking, and optimization foundations, then align every remaining study decision to SOA-C03. Verify the active exam information with AWS before committing time or an exam fee, and use scenario-based practice to build operational judgment rather than memorizing isolated answers.
