C90.03 Exam Guide: AWS Certified CloudOps Engineer – Associate (SOA-C03)
The closest official match for “C90.03” is AWS Certified CloudOps Engineer – Associate, exam code SOA-C03, formerly AWS Certified SysOps Administrator – Associate. It validates the ability to deploy, manage, and operate AWS workloads for CloudOps-focused work. This guide helps administrators and operations professionals decide whether their current experience is sufficient, what to practice first, and when they are ready to schedule the current AWS exam.
Confirm that C90.03 means SOA-C03 before you study
AWS does not identify the certification as “C90.03” in the supplied official material. The closest official designation is AWS Certified CloudOps Engineer – Associate (SOA-C03), so candidates should verify the exam code in their AWS Certification account and on their booking page before buying training or setting a test date.
That distinction matters because “SOA” can refer to unrelated technologies in other vendor documentation. Oracle, for example, uses SOA for its application-integration platform, and Microsoft uses SOA in identity-management guidance. Neither is evidence of the AWS CloudOps certification. Keep your notes, practice resources, and registration material tied to the full AWS title and the SOA-C03 code.
AWS states that SOA-C03 began being used on September 30, 2025, replacing SOA-C02 as the current version. Candidates who have older SysOps Administrator materials should treat them as background only, then reconcile every topic against the SOA-C03 exam guide and comparison document. The updated blueprint is the decision-maker when a course and the current guide disagree.
What the certification validates
SOA-C03 validates operational capability on AWS: deploying, managing, and operating workloads rather than designing every aspect of a cloud estate from first principles. AWS frames the credential around practical CloudOps responsibilities, including maintenance, monitoring, security controls, incident handling, continuity, and operational networking.
The official guide says the exam assesses support and maintenance of AWS workloads according to the AWS Well-Architected Framework. It also covers operations performed with the AWS Management Console and the AWS Command Line Interface. A useful preparation standard is therefore simple: for each topic, be able to explain the operational objective, select an appropriate AWS mechanism, and recognize what evidence would confirm that the mechanism is working.
The stated task areas include monitoring, logging, and troubleshooting systems; applying networking concepts such as DNS, TCP, IP, and firewalls; implementing requirements related to high availability, performance, and capacity; carrying out business continuity and disaster recovery procedures; and identifying, classifying, and remediating incidents. Security controls that meet compliance requirements are part of the stated scope as well.
Do not turn this into a broad architecture-design or software-development study plan. AWS lists designing distributed architectures, designing CI/CD pipelines, designing hybrid and multi-VPC networking, developing software, defining governance requirements, developing ransomware-defense strategies, assessing and planning resource capacity, and analyzing costs and total cost of ownership among tasks outside the target candidate’s expected role. Operational understanding of adjacent areas can still help, but it should not displace the published objectives.
Who should take SOA-C03
SOA-C03 is intended for CloudOps engineers and is best suited to people who already work with AWS operational tasks or are building toward that role. It is not positioned in the official guide as a first exposure to computing, networking, or cloud administration.
AWS says the target candidate should have 1 year of experience with AWS deployment, management, troubleshooting, networking, and security. It also says the candidate should have at least 1 year in a related operations role, such as system administrator. These are target-candidate recommendations, not a stated prerequisite in the supplied material.
A candidate with less experience can still make a rational preparation decision by measuring gaps against the job tasks rather than against a calendar. If you can already investigate a service symptom, work through access and network boundaries, use both the console and CLI, and explain how an operational change is deployed or reversed, your study can focus on AWS-specific patterns. If those activities are unfamiliar, build the operational foundations before relying on question practice.
The official recommendations also point to general IT experience: monitoring and troubleshooting techniques, networking fundamentals, familiarity with an operating system and a scripting language, cloud-computing knowledge, and basics of containers, orchestration, CI/CD, and Git. Treat these as a diagnostic checklist. A gap in one area is not proof that you cannot test, but it identifies where hands-on practice is likely to be more productive than memorizing service descriptions.
Use the blueprint to allocate study time
The five SOA-C03 domains should determine the order and depth of your study. Three domains each represent 22% of scored content, so a plan that spends most of its time on a favorite service family is poorly aligned with the official outline.
Content Domain 1, Monitoring, Logging, Analysis, Remediation, and Performance Optimization, represents 22% of scored content. Content Domain 2, Reliability and Business Continuity, represents 22% of scored content. Content Domain 3, Deployment, Provisioning, and Automation, represents 22% of scored content.
Content Domain 4, Security and Compliance, represents 16% of scored content. Content Domain 5, Networking and Content Delivery, represents 18% of scored content. The percentages describe scored content, not a guarantee of a fixed number of questions from each domain on an individual attempt.
Start by creating a one-page matrix with the five domain names, each task statement from the official exam guide, and three columns: “can explain,” “can perform,” and “need evidence.” Add a short scenario beside every weak item. For monitoring, the scenario might be an application symptom that requires metrics, logs, and a remediation decision. For continuity, it might be an availability event that requires a recovery-oriented response. This converts a content list into observable skills.
Avoid a common mistake: using blueprint weight as permission to ignore the smaller domains. Security and Compliance and Networking and Content Delivery still comprise meaningful portions of scored content, and operations scenarios often require more than one domain. A network symptom can affect monitoring; an automation change can create a security-control problem; a reliability decision may require sound deployment practice. Revise the boundaries between domains, not only the labels.
Give special attention to SOA-C03 updates
Candidates moving from SOA-C02 materials should deliberately study the SOA-C03 additions and content moves. The comparison page identifies changes that can be missed when preparation relies on an older course, a legacy note set, or a generic SysOps question bank.
For monitoring, AWS added configuration and management of the CloudWatch agent to collect metrics and logs from EC2 instances, Amazon ECS clusters, or Amazon EKS clusters. It also added configuring and analyzing CloudWatch network monitoring services in Task 5.3. Build a practice exercise around the flow of operational information: what is collected, where it is viewed, what signal indicates a problem, and what response is appropriate.
For deployment and automation, Task 3.1 added creating and managing stacks of resources by using CloudFormation and the AWS CDK. The productive study choice is to understand the operational lifecycle of a stack: representing resources, applying a managed change, checking the resulting state, and investigating a failure. Do not reduce infrastructure as code to a list of product names.
For security and compliance, Task 4.1 added enforcement of compliance requirements, with Region and service selections given as examples. Review this as an operations-control question: identify the requirement, determine the control boundary, and distinguish enforcement from merely documenting a preference.
The comparison also says VPNs moved to Task 5.1, while former SOA-C02 Tasks 6.1 and 6.2 moved to SOA-C03 Task 1.3. S3 static website hosting configuration was removed from Task 5.2. Do not infer that an AWS service is irrelevant just because one specific configuration task was removed; instead, use the current task statements to decide what must be mastered.
Build operational skill, not a service glossary
The strongest preparation links AWS services to an operational decision: observe a condition, identify a likely cause, apply a safe response, and confirm the outcome. Reading definitions alone leaves a candidate unprepared for questions that combine symptoms, constraints, and a requested outcome.
Create a small personal lab plan only from topics named by the official guide. Work with the AWS Management Console and AWS CLI because both are explicitly in scope. Practice monitoring and logging workflows, operational deployment and provisioning workflows, security-control workflows, and networking troubleshooting workflows. Keep a record of commands, console paths, expected outputs, failure signs, and rollback or remediation choices in your own words.
The official guide recommends familiarity with AWS storage and container solutions, monitoring tools, infrastructure as code and CloudFormation, networking and security services, cloud financial management, hybrid and multi-VPC operations, database services including Amazon RDS, Amazon DynamoDB, and Amazon ElastiCache, and compute services including Amazon EC2, AWS Lambda, and Amazon ECS. Use that list to recognize the service context in a scenario, but prioritize the CloudOps action being tested over exhaustive feature recall.
A practical drill is to take one operational event and answer five questions: What should be observed? Which control or configuration is relevant? What is the least disruptive next action? What result would validate the response? What related dependency could produce a similar symptom? This method develops analysis without claiming access to live exam content.
Avoid collecting unverified recalled questions or “dumps.” They can be inaccurate, outdated, and disconnected from the current blueprint. More importantly, they do not build the troubleshooting judgment required for a scenario-based operations role. Use the official guide to set scope, then test yourself with original scenarios, documentation-based labs, and notes that explain why alternatives do or do not fit the stated requirement.
Follow a staged study roadmap
A staged roadmap prevents early practice scores from being mistaken for operational readiness. Move from scope and foundations to domain practice, then to timed review only after you can explain the reasoning behind your choices.
Stage 1 is orientation. Confirm that your target is SOA-C03, download or review the official exam guide, map the five domains, and mark each task as familiar, partly familiar, or unknown. Review the stated candidate knowledge in networking, monitoring, operating systems, scripting, cloud computing, containers, orchestration, CI/CD, and Git. This stage should end with a written gap list, not a test date chosen by optimism.
Stage 2 is monitoring and reliability. Work through Monitoring, Logging, Analysis, Remediation, and Performance Optimization alongside Reliability and Business Continuity. Pairing them is practical because operational detection and operational recovery are closely connected. Practice articulating the distinction between seeing a condition, diagnosing it, remediating it, and restoring an expected service outcome.
Stage 3 is change operations. Study Deployment, Provisioning, and Automation with CloudFormation and AWS CDK included in the current scope. Focus on repeatable resource changes and how an operator verifies them. Add Security and Compliance as a control layer: ask what permissions, constraints, or compliance requirements must remain true when infrastructure changes.
Stage 4 is connectivity and consolidation. Study Networking and Content Delivery as a troubleshooting discipline, including DNS, TCP, IP, and firewalls from the official guide. Then mix scenarios across domains. A well-designed mixed review should force you to decide whether a reported issue is primarily a monitoring, reliability, deployment, security, or network problem before selecting an action.
Stage 5 is readiness review. Revisit every task marked unknown in Stage 1. For each one, produce a concise explanation, a command-line or console-oriented action where relevant, and a validation step. If you cannot justify why an answer fits the requirement, return to the underlying task rather than repeating questions until a pattern feels familiar.
Use practice results without misreading them
Practice is valuable when it reveals weak reasoning, but it is unreliable when used as a prediction machine. The official guide specifically advises caution when interpreting section-level feedback, so a narrow score should trigger investigation rather than an automatic conclusion about one isolated skill.
After a practice session, classify each miss by cause: misunderstood requirement, unfamiliar service context, weak networking or operations foundation, confused terminology, or poor time management. Then repair the cause with a small action. For example, a misunderstanding about an operational signal calls for a monitoring exercise; a confused access-control choice calls for a security-control review; a network mistake calls for a DNS, TCP, IP, or firewall refresher.
Keep an error log that records the domain, the decision you made, the evidence you overlooked, and the principle you will use next time. Do not simply record the selected answer. The aim is to create a reusable decision rule, such as identifying whether a scenario requests detection, remediation, compliance enforcement, continuity, or connectivity diagnosis.
Schedule only after your errors have become specific and repairable across all five domains. This is a practical recommendation, not an AWS scheduling requirement. A candidate who can explain a correct choice, reject plausible alternatives, and work steadily under a timed format has a more defensible basis for booking than someone relying on a single aggregate practice score.
Know the tested format and score reporting
The official exam information gives candidates a concrete planning baseline: SOA-C03 contains 65 questions in multiple-choice or multiple-response formats and has a 130 minutes exam duration. Build familiarity with both selecting one answer and evaluating several possible answers.
AWS states that 50 questions affect the score and 15 questions are unscored. Because candidates are not told which questions are unscored, treat every question as a scored question and apply the same care throughout the exam. Do not try to identify unscored items from difficulty, wording, or topic.
Results are reported on a scaled score of 100–1,000, and the minimum passing score is 720. A scaled score should not be treated as a simple percentage-correct calculation. Use it only as the official reporting framework, not as a basis for reverse-engineering how many questions can be missed.
For practice, rehearse a calm sequence: read the requested outcome, identify constraints, eliminate choices that address a different operational problem, select every response required by the question format, and reserve time to revisit flagged items. This is a study technique rather than an official test-taking instruction, but it is particularly useful for multiple-response questions where a partially suitable option may still fail the full requirement.
Choose a delivery option and book deliberately
SOA-C03 is offered through Pearson VUE testing centers or as an online-proctored exam. Choose based on the environment in which you can concentrate and meet the applicable provider requirements, then confirm current booking instructions directly in the AWS Certification process.
AWS lists the exam cost as 150 USD and notes that additional pricing information, such as foreign-exchange rates, may apply. Confirm the price and any local details at the point of registration rather than relying on a copied amount from an older study resource.
The listed exam languages are English, Japanese, Korean, and Simplified Chinese. Select the language that best supports accurate interpretation of technical constraints, not merely recognition of service names. If you normally study documentation in one language but plan to test in another, include terminology comparison in your review rather than discovering language friction during the exam.
Before booking, make a short decision record: chosen delivery option, intended language, domains still requiring review, and the next three hands-on tasks. This prevents scheduling from becoming a substitute for preparation. After booking, protect the final review period for the current blueprint, error-log repair, and concise operational notes rather than beginning unrelated AWS topics.
Plan for the credential after a pass
AWS certification credentials are valid for three years from the date earned, after which recertification is required to keep them active. Treat that policy as part of the credential decision, especially if an employer expects an active certification rather than a one-time pass.
The best long-term use of SOA-C03 preparation is to retain the operational habits behind it. Keep a personal reference organized around symptoms, observability, recovery, changes, controls, and network dependencies. As AWS services and operational procedures change, return to the official exam guide and AWS Certification policy pages rather than assuming an older course remains current.
Your immediate next step is to compare your experience with the official target-candidate description and create the five-domain matrix. If the gaps are mostly AWS-specific, begin staged hands-on study. If the gaps are fundamentals such as troubleshooting, networking, scripting, or systems administration, address those first; that choice is likely to make the AWS material more understandable and your later practice more meaningful.
Conclusion
For the exam commonly searched as C90.03, verify that you are preparing for AWS Certified CloudOps Engineer – Associate (SOA-C03). Use the current five-domain outline to direct study, give the revised CloudWatch, infrastructure-as-code, compliance, and networking material deliberate attention, and build answers around operational decisions rather than isolated facts. Book only after you can explain, perform, and validate the major CloudOps tasks across the blueprint.
