IT Cert Ready

AWS

AWS Certified CloudOps Engineer – Associate

Exam code: SOA-C03

Start practicing

About this certification

AWS Certified CloudOps Engineer – Associate is a AWS certification. Exam code SOA-C03. IT Cert Ready offers 1,206 practice questions with domain quizzes, full mock exams, and detailed explanations. Practice by official domain with 6 blueprint-aligned domains.

Official exam domain weights

Verified blueprint weights from the official exam outline.

  • Domain 1 · Monitoring, Logging, and Remediation · 20%
  • Domain 2 · Reliability and Business Continuity · 16%
  • Domain 3 · Deployment, Provisioning, and Automation · 18%
  • Domain 4 · Security and Compliance · 16%
  • Domain 5 · Networking and Content Delivery · 18%
  • Domain 6 · Cost and Performance Optimization · 12%

Sample AWS Certified CloudOps Engineer – Associate practice questions

Preview realistic multiple-choice items from the IT Cert Ready question bank. Expand each answer for the correct choice and explanation—the same format used in domain quizzes and mock exams.

  1. Sample question 1 · Cost and Performance Optimization (12%)

    Meridian Content Studios, a small independent film production company based in Southeast Asia, recently migrated its post-production rendering workload to AWS. The workload runs on a single on-demand r5.4xlarge instance and uses Amazon ElastiCache for Redis to cache frequently accessed scene metadata. The Head of Technology has observed that render job completion times have not improved despite the caching layer, and cache hit ratios reported in CloudWatch are consistently below 15%. A security awareness initiative at the studio has also surfaced concerns from the finance team about unpredictable monthly AWS bills. The Head of Technology must present a root-cause analysis and corrective action plan to both the technical team and the finance committee within one week. Which operational action best addresses the low cache hit ratio and allows the CloudOps engineer to present a credible, governance-aligned corrective action plan to both technical and finance stakeholders?

    • A. Increase the ElastiCache node size from cache.r6g.large to cache.r6g.4xlarge to provide more memory for caching scene metadata, and report to the finance committee that the larger node will reduce render times by storing more data in memory.
    • B. Audit the application's cache key design and TTL configuration using ElastiCache slow logs and CloudWatch cache hit/miss metrics to identify why metadata is not being retrieved from cache; remediate by correcting key naming inconsistencies or extending TTLs, and present the root-cause findings with before/after hit ratio targets as the governance deliverable for both stakeholder groups.
    • C. Replace the ElastiCache for Redis cluster with an Amazon DynamoDB Accelerator (DAX) layer and migrate scene metadata storage to DynamoDB, presenting the architectural change as a caching modernization initiative to the finance committee.
    • D. Switch the rendering workload from the r5.4xlarge instance to a p3.2xlarge GPU-accelerated instance to reduce render times, and inform the finance committee that faster renders will lower the total compute hours billed each month.
    View answer & explanation

    Correct answer: B. Audit the application's cache key design and TTL configuration using ElastiCache slow logs and CloudWatch cache hit/miss metrics to identify why metadata is not being retrieved from cache; remediate by correcting key naming inconsistencies or extending TTLs, and present the root-cause findings with before/after hit ratio targets as the governance deliverable for both stakeholder groups.

    [Domain 6 - Cost and Performance Optimization, Subtopic 6 - Cost and Performance - Area 1 - Instance types] Core Concept: Optimize performance for operational workloads. centers on instance types as defined in the official (ISC)² exam outline. Correct Answer (B): Audit the application's cache key design and TTL configuration using ElastiCache slow logs and CloudWatch cache hit/miss metrics to identify why metadata is not being retrieved from cache; remediate by correcting key naming inconsistencies or extending TTLs, and present the root-cause findings with before/after hit ratio targets as the governance deliverable for both stakeholder groups. Why the other options are incorrect: Option A: Upgrading the ElastiCache node size increases memory capacity but does not resolve a hit ratio problem caused by key design flaws or TTL misconfiguration; a larger node will cache more data that is never retrieved correctly, wasting cost without improving performance. Option C: Migrating to DynamoDB and DAX is a significant architectural change that introduces new data modeling requirements and costs; it does not address the root cause of the existing Redis misconfiguration and would be difficult to justify to a finance committee without evidence that the current caching approach is fundamentally unsuitable. Option D: Switching to a GPU-accelerated p3.2xlarge instance may improve raw render computation speed but does not address the caching layer's low hit ratio, which is the identified performance problem; additionally, GPU instances are significantly more expensive and would likely increase the finance committee's billing concerns rather than resolve them.

  2. Sample question 2 · Networking and Content Delivery (18%)

    Meridian Assurance Group, a mid-sized regional insurance provider, is conducting a BCP/DR tabletop exercise. During the exercise, the team simulates a full primary-region failure affecting their policyholder self-service portal. The portal is served through a CloudFront distribution backed by an Application Load Balancer (ALB) origin in us-east-1. The DR plan calls for failover to a standby ALB in us-west-2. During validation, the team discovers that CloudFront continues routing all requests to the failed primary origin even after the standby ALB is healthy, because the distribution has only one origin configured with no origin failover group. The team must identify the correct operational remediation to implement before the next DR cycle. Which operational action best resolves the CloudFront origin failover gap identified during Meridian Assurance Group's DR tabletop exercise?

    • A. Create a Route 53 latency-based routing policy between the two ALBs and update the CloudFront distribution's origin domain to point to the Route 53 DNS name, relying on DNS TTL expiry to redirect traffic during a regional failure.
    • B. Configure a CloudFront origin group containing both the primary ALB in us-east-1 and the standby ALB in us-west-2, set the primary origin, and enable origin failover by specifying HTTP 5xx status codes as failover criteria so CloudFront automatically retries requests against the secondary origin.
    • C. Enable CloudFront geo-restriction to block traffic from us-east-1 during a failure event, then manually update the distribution's single origin domain name to the us-west-2 ALB endpoint and wait for the configuration change to propagate globally.
    • D. Deploy an AWS Global Accelerator endpoint group pointing to both ALBs and replace the CloudFront distribution entirely, since CloudFront does not natively support multi-origin failover for ALB origins.
    View answer & explanation

    Correct answer: B. Configure a CloudFront origin group containing both the primary ALB in us-east-1 and the standby ALB in us-west-2, set the primary origin, and enable origin failover by specifying HTTP 5xx status codes as failover criteria so CloudFront automatically retries requests against the secondary origin.

    [Domain 5 - Networking and Content Delivery, Subtopic 5 - Networking - Area 1 - CloudFront] Core Concept: Implement content delivery and DNS. requires applying cloudfront in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (B): Configure a CloudFront origin group containing both the primary ALB in us-east-1 and the standby ALB in us-west-2, set the primary origin, and enable origin failover by specifying HTTP 5xx status codes as failover criteria so CloudFront automatically retries requests against the secondary origin. Why the other options are incorrect: Option A: Route 53 latency-based routing can complement DR architectures but does not provide automatic CloudFront-layer failover; DNS TTL expiry introduces minutes of delay and does not trigger on HTTP error codes, leaving the gap unresolved during the critical failover window. Option C: Manually updating the CloudFront origin domain during an incident is an error-prone, slow process that violates BCP automation requirements; geo-restriction blocks end-user traffic by geography and has no mechanism to detect or respond to origin health status. Option D: AWS Global Accelerator is a valid multi-region routing tool but does not replace CloudFront's caching and content delivery capabilities; CloudFront natively supports multi-origin failover through origin groups, making this claim factually incorrect and operationally disruptive.

  3. Sample question 3 · Cost and Performance Optimization (12%)

    Pennington Gallagher LLP is a large international law firm with 1,500 users across North America and Europe. The firm operates a case management portal backed by an ElastiCache for Redis cluster and an RDS PostgreSQL database. Attorneys access the portal from BYOD devices managed through the firm's MDM platform. A recent performance audit flagged that the Redis cache hit ratio has dropped from 92% to 61% over the past 60 days, coinciding with a 40% increase in attorney headcount following a merger. The RDS instance is now experiencing read replica lag exceeding 8 seconds during peak hours. The audit team requires sampling of CloudWatch metrics at 1-minute granularity for the past 30 days as documented evidence before the infrastructure review board approves remediation spending. Which operational action BEST addresses the degraded cache hit ratio, reduces read replica lag, and satisfies the audit team's requirement for granular, documented performance evidence?

    • A. Increase the ElastiCache Redis node type to a memory-optimized instance with higher RAM, enable ElastiCache slow log export to CloudWatch Logs, add a second RDS read replica, and use CloudWatch Metrics Insights queries with 1-minute period statistics exported to S3 to fulfill the audit documentation requirement.
    • B. Replace ElastiCache Redis with an in-process application cache on each EC2 web server to eliminate network latency, promote the existing read replica to a standalone RDS instance, and use AWS Cost Explorer reports as the audit evidence for the infrastructure review board.
    • C. Enable RDS Proxy in front of the primary RDS instance to pool connections and reduce replica lag, disable the ElastiCache cluster to simplify the architecture, and capture AWS X-Ray traces as the sole performance baseline for the audit team.
    • D. Migrate the RDS PostgreSQL database to DynamoDB to eliminate replica lag entirely, retain the existing ElastiCache node size, and use AWS Trusted Advisor performance checks as the documented evidence for the audit review board.
    View answer & explanation

    Correct answer: A. Increase the ElastiCache Redis node type to a memory-optimized instance with higher RAM, enable ElastiCache slow log export to CloudWatch Logs, add a second RDS read replica, and use CloudWatch Metrics Insights queries with 1-minute period statistics exported to S3 to fulfill the audit documentation requirement.

    [Domain 6 - Cost and Performance Optimization, Subtopic 6 - Cost and Performance - Area 1 - Instance types] Core Concept: Optimize performance for operational workloads. centers on instance types as defined in the official (ISC)² exam outline. Correct Answer (A): Increase the ElastiCache Redis node type to a memory-optimized instance with higher RAM, enable ElastiCache slow log export to CloudWatch Logs, add a second RDS read replica, and use CloudWatch Metrics Insights queries with 1-minute period statistics exported to S3 to fulfill the audit documentation requirement. Why the other options are incorrect: Option B: Replacing a distributed Redis cluster with per-server in-process caches eliminates cache coherence across the web tier, causing inconsistent data for attorneys on different servers, and AWS Cost Explorer is a cost analysis tool, not a performance monitoring artifact suitable for an infrastructure audit. Option C: RDS Proxy reduces connection overhead but does not directly address read replica lag caused by replication throughput; disabling ElastiCache would force all reads to hit the already-overloaded database, dramatically worsening performance rather than improving it. Option D: Migrating PostgreSQL to DynamoDB is a major architectural change requiring application refactoring and is not an operational optimization action; Trusted Advisor performance checks provide high-level recommendations, not the granular 1-minute metric time-series data the audit team explicitly requires.

  4. Sample question 4 · Cost and Performance Optimization (12%)

    Luminary Broadcasting Network, a large streaming media company headquartered in Europe with regulatory obligations under GDPR, operates a real-time audience analytics platform. The platform ingests clickstream events into an EC2-hosted processing tier backed by Amazon EBS gp2 volumes. During live broadcast events, the analytics dashboard used by advertising sales executives experiences severe latency—query response times exceed 8 seconds. A performance audit commissioned by the VP of Engineering reveals that EBS volume queue depth consistently reaches its limit during broadcast windows, while CPU and memory remain underutilized. The VP has requested a written performance improvement proposal with measurable SLOs before any infrastructure change is approved. Which operational action should the CloudOps engineer recommend to resolve the I/O bottleneck and satisfy the VP's governance requirement for a measurable SLO-backed proposal?

    • A. Replace the existing m5.xlarge instances with r6i.2xlarge memory-optimized instances to increase the in-memory buffer for clickstream events, and propose a memory utilization SLO of less than 70% as the performance target.
    • B. Migrate the EBS volumes from gp2 to gp3, explicitly provisioning higher IOPS (up to 16,000) and throughput (up to 1,000 MB/s) independent of volume size, and define an SLO of EBS queue depth remaining below 1 during broadcast windows as the measurable governance target.
    • C. Enable Amazon CloudFront in front of the analytics dashboard to cache query results at edge locations, and present a cache hit ratio SLO of greater than 80% as the performance commitment to the VP.
    • D. Increase the EBS gp2 volume size from 500 GB to 2 TB to leverage the volume's baseline IOPS scaling with size, and document a storage utilization SLO of less than 60% for the governance proposal.
    View answer & explanation

    Correct answer: B. Migrate the EBS volumes from gp2 to gp3, explicitly provisioning higher IOPS (up to 16,000) and throughput (up to 1,000 MB/s) independent of volume size, and define an SLO of EBS queue depth remaining below 1 during broadcast windows as the measurable governance target.

    [Domain 6 - Cost and Performance Optimization, Subtopic 6 - Cost and Performance - Area 1 - Instance types] Core Concept: Optimize performance for operational workloads. centers on instance types as defined in the official (ISC)² exam outline. Correct Answer (B): Migrate the EBS volumes from gp2 to gp3, explicitly provisioning higher IOPS (up to 16,000) and throughput (up to 1,000 MB/s) independent of volume size, and define an SLO of EBS queue depth remaining below 1 during broadcast windows as the measurable governance target. Why the other options are incorrect: Option A: The audit confirms CPU and memory are underutilized, so switching to memory-optimized r6i instances does not address the root cause of I/O queue depth saturation; a memory utilization SLO is irrelevant to the confirmed bottleneck. Option C: CloudFront edge caching is appropriate for static or cacheable content delivery, but real-time clickstream analytics queries are dynamic and personalized, making a cache hit ratio SLO impractical and the solution ineffective for the identified I/O bottleneck. Option D: Increasing a gp2 volume from 500 GB to 2 TB does raise the baseline IOPS from 1,500 to 6,000, but this approach is cost-inefficient compared to gp3 migration, does not provide throughput control, and a storage utilization SLO does not measure the actual performance problem of queue depth saturation.

  5. Sample question 5 · Cost and Performance Optimization (12%)

    Hartwell & Crane LLP, a mid-sized law firm with 200 attorneys across three regional offices, runs a document review platform on AWS. The platform uses a fleet of compute-optimized EC2 instances to process large volumes of scanned legal documents uploaded from attorney mobile devices enrolled in the firm's MDM solution. During a quarterly performance audit, the CloudOps team discovers that CPU utilization on the document-processing instances consistently peaks at 95–100% during morning hours when attorneys sync overnight uploads, while average daily utilization remains below 30%. The audit also reveals that EBS volumes attached to these instances are provisioned at 3,000 IOPS but CloudWatch metrics show actual IOPS consumed rarely exceeds 400. The firm's compliance officer requires documented evidence of resource utilization trends before any infrastructure changes are approved. The CloudOps engineer must recommend an operationally sound change that resolves the morning CPU saturation, right-sizes the EBS provisioning, and produces auditable evidence of the performance baseline. Which combination of actions BEST satisfies all three requirements?

    • A. Switch the document-processing instances to memory-optimized instance types to absorb burst workloads, retain the existing 3,000-IOPS gp3 volumes unchanged, and export CloudWatch metric statistics to an S3 bucket using a scheduled AWS CLI script for audit documentation.
    • B. Replace the compute-optimized instances with burstable T4g instances to handle variable CPU demand, downgrade EBS volumes from 3,000 IOPS to 500 IOPS on gp3, and enable AWS Compute Optimizer recommendations export to S3 to serve as the auditable performance baseline.
    • C. Retain the compute-optimized instance family but implement an Auto Scaling group with scheduled scale-out before the morning sync window and scale-in afterward, reduce provisioned EBS IOPS to 500 on gp3 volumes, and use CloudWatch Contributor Insights with metric math to generate a documented utilization baseline report stored in S3.
    • D. Migrate the document-processing workload to AWS Lambda functions triggered by S3 upload events to eliminate instance-level CPU saturation, keep EBS volumes at 3,000 IOPS for compatibility, and use AWS Trusted Advisor cost reports as the audit evidence for the compliance officer.
    View answer & explanation

    Correct answer: C. Retain the compute-optimized instance family but implement an Auto Scaling group with scheduled scale-out before the morning sync window and scale-in afterward, reduce provisioned EBS IOPS to 500 on gp3 volumes, and use CloudWatch Contributor Insights with metric math to generate a documented utilization baseline report stored in S3.

    [Domain 6 - Cost and Performance Optimization, Subtopic 6 - Cost and Performance - Area 1 - Instance types] Core Concept: Optimize performance for operational workloads. centers on instance types as defined in the official (ISC)² exam outline. Correct Answer (C): Retain the compute-optimized instance family but implement an Auto Scaling group with scheduled scale-out before the morning sync window and scale-in afterward, reduce provisioned EBS IOPS to 500 on gp3 volumes, and use CloudWatch Contributor Insights with metric math to generate a documented utilization baseline report stored in S3. Why the other options are incorrect: Option A: Memory-optimized instances are designed for in-memory databases and large dataset caching workloads, not CPU-bound document processing; switching instance families without addressing the burst pattern would not resolve peak saturation and introduces unnecessary cost. Option B: Burstable T4g instances use CPU credits and are unsuitable for sustained high-CPU batch workloads; once credits are exhausted during the morning burst, performance would degrade further rather than improve, making this choice operationally risky. Option D: Migrating a stateful document-processing fleet to Lambda is a significant architectural refactor that falls outside operational optimization scope, and Lambda functions do not use EBS volumes, making the instruction to retain 3,000-IOPS EBS volumes contradictory and technically invalid.

AWS Certified CloudOps Engineer – Associate exam prep FAQ

What is the passing score for the AWS Certified CloudOps Engineer – Associate exam?
Passing scores for AWS Certified CloudOps Engineer – Associate are set by AWS and can change between exam versions. Check the latest official exam outline on the AWS website for the current passing standard.
How many questions are on the AWS Certified CloudOps Engineer – Associate certification exam?
Official AWS Certified CloudOps Engineer – Associate exam length and item types are defined by AWS. Review the current exam blueprint for the latest question counts and timing.
How do domain quizzes help with AWS Certified CloudOps Engineer – Associate exam prep?
Domain quizzes on IT Cert Ready let you practice AWS Certified CloudOps Engineer – Associate one blueprint domain at a time across 6 official exam domains. You get immediate feedback, detailed explanations, and can revisit weak areas before taking a full timed mock exam.
How many AWS Certified CloudOps Engineer – Associate practice questions are on IT Cert Ready?
IT Cert Ready includes 1,206 published AWS Certified CloudOps Engineer – Associate practice questions with domain quizzes, full-length mock exams, and answer explanations mapped to the official outline.