AWS Certified CloudOps Engineer - Associate cheat sheet
Amazon Web Services
Free to share. Examworthy is not affiliated with or endorsed by Amazon Web Services; SOA-C03 and related marks belong to their respective owners.
At a glance
Format: Multiple choice and multiple response
Domain weight map
Heaviest first - spend your time hereHow this exam thinks
SOA-C03 is an operate-it-correctly exam: almost every question is a scenario with a monitoring, remediation, recovery, security or networking constraint, and the right answer is the AWS operations service or setting that meets it with the least manual effort.
Spot the trap
Tempting wrong answers, and why they failCommon misconception
That turning on detailed monitoring adds memory and disk metrics. It only raises the publishing rate of the existing hypervisor metrics to one minute.
Monitoring, Logging, Analysis, Remediation, and Performance Optimization
Common misconception
That a launch configuration can mix instance types and Spot capacity. It is immutable, carries a single instance type, and cannot express a mixed instances policy at all.
Reliability and Business Continuity
Common misconception
That basic ECR scanning keeps images under continuous watch. It runs only on push or on demand and reports operating system packages alone.
Deployment, Provisioning, and Automation
Common misconception
That a route to an internet gateway gives a private subnet outbound-only access. It works in both directions, so those instances become reachable from the internet.
Networking and Content Delivery
Common misconception
That encrypting the credentials file removes the danger of static keys. The long-lived key still sits on every host and works for anyone who can read the file.
Security and Compliance
Common misconception
That calling PutMetricData more often is enough for a ten second alarm. Resolution is fixed by StorageResolution when the metric is published.
Monitoring, Logging, Analysis, Remediation, and Performance Optimization
Common misconception
That an Aurora Multi-AZ standby absorbs read traffic. The standby exists to take over on failover and serves no application reads, so it adds no read throughput.
Reliability and Business Continuity
Common misconception
That a DeletionPolicy of Retain protects a resource from every destructive stack action. It applies to removal from the template and to stack delete, not to an update that replaces it.
Deployment, Provisioning, and Automation
Key terms
Exam-day rules
- Read the scenario for its operational constraint first. The automation, recovery, security or cost limit named in the question is what picks the answer, so find it before you judge the options.
- When two services both work, default to the managed, automated, least-overhead one. AWS prefers managed automation; reach for the manual option only when the scenario names a reason such as an engine or tool to preserve.
- For remediation that needs no human, choose the automated chain. An alarm or EventBridge rule invoking a Systems Manager runbook or Lambda beats an SNS email to on-call whenever the requirement is to fix it automatically.
- Remember EC2 publishes no memory or disk metric by default. When a question needs in-guest signals, the CloudWatch agent is the answer, not detailed monitoring, which only changes frequency.
- Match the disaster-recovery tier to the stated RTO and RPO. A few-minute RTO at low steady cost points to pilot light or warm standby; relaxed targets allow backup and restore; a few-minute RPO needs point-in-time restore, not a nightly snapshot.
Revision schedule
- Day 1Map the blueprint and book a date
- Week 1Build the operations decision maps
- Weeks 1 to 3Go deep on monitoring, remediation and continuity (Domains 1 and 2)
- Weeks 3 to 4Lock provisioning and automation (Domain 3)
- Week 4Cover security operations and networking (Domains 4 and 5)