AWS Certified CloudOps Engineer - Associate (SOA-C03)
Study another certificationProgress0%
Recent accuracy0%
Review due0questions
Answered0 / 172questions
Practice by topic
1 Monitoring, logging, analysis, remediation, and performance optimizationMetrics, alarms, log analysis, incident remediation, and performance improvement.
2 Reliability and business continuityBackups, recovery, failover, and scaling.
3 Deployment, provisioning, and automationCloudFormation, Systems Manager, CI/CD, and operational automation.
4 Security and complianceIAM, vulnerabilities, detection, encryption, and compliance assessment.
5 Networking and content deliveryVPC, connectivity, DNS, load balancing, and CloudFront.
Practice by topic
Practice settings
Question count
10questions1172questions
This session: 10questions / eligible: 172 questions
Learning modes
Quick practice
Start quick practice
Question count
10questions1172questions
This session: 10 questions / pool: 172 questions
Review
Start review
Question count
0questions00questions
This session: 0 questions / pool: 0 questions
Browse questions by objective
Choose a topic to read an individual question, its hints, and explanations. No session setup is required.
1.1 Implement monitoring, logging, and remediation17 questions
- Notify operators when EC2 CPU remains high
- Extract and aggregate errors from many log groups
- Audit S3 object-level operations
- Collect memory and disk utilization from EC2
- Alarm on an application queue length
- Combine alarms into one incident notification
- Turn authentication failures in logs into an alarm
- Find the DynamoDB keys that contribute most to traffic
- Collect operational metrics for ECS tasks and clusters
- Detect Lambda concurrency approaching its limit
- Distinguish ALB-generated errors from target errors
- Detect unusual load with daily and weekly patterns
- Review multiple services in a shared operational view
- Continuously deliver new logs to an analysis stream
- Apply EC2 file-log collection settings
- Investigate OpenSearch shard search latency and resources
- Monitor metrics from multiple accounts in one dashboard
1.2 Identify and remediate issues by using monitoring and availability metrics6 questions
1.3 Remediate issues and optimize performance15 questions
- Identify the SQL causing high RDS database load
- Investigate declining performance of a burstable EC2 instance
- Detect messages waiting too long in SQS
- Compare pending EBS I/O with completed operations
- Warn on RDS free storage with the correct unit
- Interpret Lambda p95 execution duration
- Identify the DynamoDB resource and throttling limit
- Investigate memory-related ECS container stops
- Place nodes for low-latency node-to-node traffic
- Evaluate EC2 right-sizing candidates from utilization
- Absorb bursts of short-lived database connections with RDS Proxy
- Clean up incomplete S3 multipart uploads
- Accelerate S3 transfers from distant clients
- Tune EBS throughput from measured limits
- Handle unpredictable EFS throughput spikes
3.2 Automate the management of existing resources11 questions
- Stop unused EC2 instances overnight
- Deploy an EC2 application with a rollback path
- Deploy automatically after a source change
- Roll back a failed deployment automatically
- Pass the same build artifact to later stages
- Run scripts before and after an EC2 deployment
- Require approval before production deployment
- Move a new ECS version to users gradually
- Shorten build time by reusing dependencies
- Share private packages across build projects
- Start Systems Manager Automation from an S3 event
2.3 Implement backup and restore strategies10 questions
- Manage backups for several AWS services centrally
- Prepare AWS Backup copies in another Region
- Prepare to restore S3 overwrites and simple deletes
- Prepare DynamoDB point-in-time recovery before incorrect updates
- Prepare FSx daily backup retention and restoration
- Automate backups across several AWS services
- Choose a near-current restore for an RDS database
- Recover an overwritten S3 object
- Choose a disaster recovery design with a short RTO
- Choose a disaster recovery strategy from RPO, RTO, and cost
2.2 Implement highly available and resilient environments13 questions
- Fail over an RDS database after an Availability Zone failure
- Use ALB target health to decide DNS failover
- Prepare shared Linux file access through an Availability Zone failure
- Protect backups from deletion by administrators
- Regularly verify restore capability and RTO
- Restore RDS to a recent point in time
- Fail over to a backup origin after an error
- Schedule EBS snapshots with tag-based retention
- Automatically recover an EC2 host failure
- Connect tasks in multiple AZs to the same EFS file system
- Reprocess messages moved to a dead-letter queue
- Validate application recovery after Aurora failover
- Monitor S3 replication delay
2.1 Implement scalability and elasticity13 questions
- Scale EC2 capacity toward a CPU target
- Manage Aurora reader count and distribution of new connections
- Initialize an EC2 instance before adding it to service
- Reserve concurrency for a critical Lambda function
- Maintain four running tasks in an ECS service
- Keep DynamoDB available in multiple Regions
- Stop sending traffic to unhealthy targets
- Apply a new AMI to all instances gradually
- Scale Lambda from SQS without overloading a database
- Automatically expand RDS storage
- Adjust provisioned DynamoDB capacity automatically
- Reduce empty SQS receive responses
- Reduce database load with a cache during a read spike
3.1 Provision and maintain resources19 questions
- Create the same resource stack in every environment
- Review the impact of a production stack update
- Define infrastructure with a programming language
- Apply configuration to EC2 instances on a schedule
- Apply approved OS patches during a maintenance window
- Remove old container images automatically
- Detect a manual change to a CloudFormation stack
- Reuse a shared network across separate stacks
- Reference environment-specific settings without embedding secrets
- Declare CPU and memory for an ECS task
- Restore a stack after an update failure
- Inventory installed software on EC2
- Deploy the same baseline to multiple accounts and Regions
- Protect a production resource from accidental deletion
- Check container images for vulnerabilities
- Bring an existing resource under CloudFormation management
- Manage Terraform history and state safely
- Automate golden AMI creation and distribution
- Resolve subnet IP exhaustion for ECS tasks
3.3 Automate manual or repeatable processes5 questions
4.1 Manage security and compliance controls16 questions
- Preview the effect of an IAM policy change
- Detect resources reachable by external principals
- Continuously detect public S3 buckets
- Centralize security findings
- Detect suspicious AWS API activity
- Continuously assess EC2 and ECR vulnerabilities
- List nodes missing approved patches
- Aggregate findings from multiple accounts
- Automatically remediate the correct security group with Config
- Separate trust and operating permissions for an EC2 role
- Restrict already-authorized S3 reads to the selected endpoint
- Separate CloudTrail digest delivery from actual integrity validation
- Prioritize vulnerability findings
- Remediate a Trusted Advisor security finding
- Continuously evaluate a standard configuration across accounts
- Provide console users with MFA-protected temporary permissions
4.2 Protect data and infrastructure9 questions
- Restrict who can use a KMS key
- Encrypt S3 objects with a customer managed key
- Rotate an RDS password automatically
- Start an EC2 containment procedure from a GuardDuty finding
- Manage the scope and termination of a KMS grant
- Connect to EC2 without exposing SSH
- Rotate a customer managed KMS key
- Classify stored data before selecting controls
- Investigate an ALB certificate name mismatch
5.1 Implement and optimize networking and connectivity21 questions
- Allow private-subnet instances to call an external API
- Allow a VPC endpoint to access only one S3 bucket
- Restrict an EC2 instance's outbound destinations
- Deny a CIDR at the subnet boundary
- Connect many VPCs through a central hub
- Create a dedicated connection from on-premises to AWS
- Fail over a VPN tunnel when one path fails
- Route requests to services by URL path
- Publish a TCP service with a fixed address
- Investigate allowed and rejected network traffic
- Manage overlapping VPC CIDR allocations
- Provide outbound IPv6 access without allowing inbound initiation
- Resolve EC2 public DNS names to private IPs across peered VPCs
- Provide resilient NAT access for private subnets
- Use the AWS-provided DNS resolver inside a VPC
- Notify operators when a VPN tunnel fails
- Distribute corporate DNS settings to VPC instances
- Resolve an AWS service name through an interface endpoint
- Inspect traffic between VPCs centrally
- Audit network protection services
- Reduce NAT cost for AWS service traffic
5.2 Configure domains, DNS, and content delivery12 questions
- Resolve private names only inside a VPC
- Resolve on-premises DNS names from a VPC
- Improve static-content cache efficiency
- Automatically renew a public certificate on an ALB
- Route clients to a healthy Region through fixed Anycast addresses
- Rate-limit excessive HTTP requests from one IP
- Allow only CloudFront to read an S3 origin
- Point a domain name at an ALB without tracking its IPs
- Deliver an updated CSS file before its TTL expires
- Redirect HTTP requests to HTTPS at an ALB
- Analyze requests served by a CloudFront distribution
- Audit Route 53 Resolver queries