Free AWS Certified CloudOps Engineer - Associate SOA-C03 Exam Braindumps
AWS Certified CloudOps Engineer - Associate Questions 46–50 (page: 11)

Updated On: 12-Mar-2026

A company needs to upload gigabytes of files daily to Amazon S3 and requires higher throughput and faster upload speeds.

Which action should a CloudOps engineer take?

  1. Create an Amazon CloudFront distribution with the GET HTTP method allowed and the S3 bucket as an origin.
  2. Create an Amazon ElastiCache cluster and enable caching for the S3 bucket.
  3. Set up AWS Global Accelerator and configure it with the S3 bucket.
  4. Enable S3 Transfer Acceleration and use the acceleration endpoint when uploading files.

Answer(s): D

Explanation:

The AWS Cloud Operations and Storage documentation confirms that S3 Transfer Acceleration is designed to increase upload speed for objects transferred to S3 buckets over long distances.

It uses AWS Global Edge Network and Amazon CloudFront edge locations to route data through optimized network paths, reducing latency and achieving higher throughput compared to standard S3 uploads.

After enabling Transfer Acceleration on the bucket, users upload files to the accelerated endpoint (e.g., bucketname.s3-accelerate.amazonaws.com). This feature requires no changes to application logic besides endpoint modification and provides immediate performance improvement.

CloudFront (Option A) is for content delivery, not uploads. ElastiCache (Option B) and Global Accelerator (Option C) are unrelated to S3 upload performance.

Thus, Option D is correct -- enable S3 Transfer Acceleration for faster, optimized file uploads.


Reference:

AWS Cloud Operations & Storage Guide ­ Enhancing Upload Speed with Amazon S3 Transfer Acceleration



Optimization]

An ecommerce company uses Amazon ElastiCache (Redis OSS) for caching product queries. The CloudOps engineer observes a large number of cache evictions in Amazon CloudWatch metrics and needs to reduce evictions while retaining popular data in cache.

Which solution meets these requirements with the least operational overhead?

  1. Add another node to the ElastiCache cluster.
  2. Increase the ElastiCache TTL value.
  3. Decrease the ElastiCache TTL value.
  4. Migrate to a new ElastiCache cluster with larger nodes.

Answer(s): D

Explanation:

According to the AWS Cloud Operations and ElastiCache documentation, cache evictions occur when the cache runs out of memory and must remove items to make space for new data.

To reduce evictions and retain frequently accessed items, AWS recommends increasing the total available memory -- either by scaling up to larger node types or scaling out by adding shards/nodes. Migrating to a cluster with larger nodes is the simplest and most efficient solution because it immediately expands capacity without architectural changes.

Adjusting TTL (Options B and C) controls expiration timing, not memory allocation. Adding a single node (Option A) may help, but redistributing data requires resharding, introducing more complexity.

Thus, Option D provides the lowest operational overhead and ensures high cache hit rates by increasing total cache memory.


Reference:

AWS Cloud Operations & Performance Optimization Guide ­ Reducing Evictions and Scaling Amazon ElastiCache Clusters



A company's application servers in AWS account 111122223333 use a security group sg-1234abcd. They need to access a database hosted in account 444455556666. The VPCs are connected using a VPC peering connection (pcx-b04deed9).

A CloudOps engineer must configure the database's security group to allow new connections only from the application servers.

What should the engineer do?

  1. Add an inbound rule to the database's security group. Reference 111122223333/sg-1234abcd as the source.
  2. Add an inbound rule to the database's security group. Reference pcx-b04deed9/sg-1234abcd as the source.
  3. Add an inbound rule to the database's security group. Reference sg-1234abcd as the source.
  4. Add an inbound rule to the database's security group. Reference 444455556666/sg-1234abcd as the source.

Answer(s): C

Explanation:

According to AWS Cloud Operations and VPC Networking documentation, when VPCs are peered, security groups can reference peer account security groups directly to restrict traffic between them.

This feature allows specifying the security group ID (sg-1234abcd) from the source account (111122223333) in the target database's security group inbound rule. AWS automatically validates that the VPCs are connected through an existing VPC peering connection and that mutual permissions are properly configured.

You do not prefix the security group ID with the account or peering connection (Options A and B), and using the destination account ID (Option D) is incorrect because it represents the database side, not the source.
Hence, the correct configuration is Option C, which references the application servers' security group directly for precise, least-privilege access control.


Reference:

AWS Cloud Operations & Networking Guide ­ Using Security Group Reference Across VPC Peering Connections



A company's developers manually install software modules on Amazon EC2 instances to deploy new versions of a service. A security audit finds that instances contain inconsistent and unapproved modules.

A CloudOps engineer must create a new instance image that contains only approved software.

Which solution will meet these requirements?

  1. Use Amazon Detective to continuously find and uninstall unauthorized modules from the instances.
  2. Use Amazon GuardDuty to create and deploy an Amazon Machine Image (AMI) that includes only the approved modules.
  3. Use AWS Systems Manager Run Command to install the approved modules on all running instances during an in-place update.
  4. Use EC2 Image Builder to create and test an Amazon Machine Image (AMI) that includes only the approved modules. Update the deployment workflow to use the new AMI.

Answer(s): D

Explanation:

According to the AWS Cloud Operations and Deployment documentation, EC2 Image Builder is the AWS-managed service for automating the creation, maintenance, validation, and deployment of secure and compliant Amazon Machine Images (AMIs).

It allows CloudOps teams to define image pipelines that include only approved software modules and configuration scripts. EC2 Image Builder automatically tests and verifies these AMIs for compliance before deployment.

This process ensures configuration consistency, eliminates manual installation errors, and simplifies ongoing patch management. The service integrates with AWS Systems Manager, Amazon Inspector, and AWS CloudFormation for end-to-end automation.

In contrast:

Amazon Detective and GuardDuty (Options A & B) are security monitoring tools, not image management solutions.

Run Command (Option C) applies ad-hoc updates but does not create standard, reusable AMIs.

Therefore, Option D is correct--EC2 Image Builder provides the most operationally efficient and compliant way to create an approved baseline AMI for future deployments.


Reference:

AWS Cloud Operations & Deployment Guide ­ Building Secure, Consistent AMIs Using EC2 Image Builder



A company with millions of subscribers needs to automatically send notifications every Saturday. The company already uses Amazon SNS to send messages but has historically sent them manually.

Which solution will meet these requirements in the MOST operationally efficient way?

  1. Launch a new Amazon EC2 instance. Configure a cron job to use the AWS SDK to send an SNS notification to subscribers every Saturday.
  2. Create a rule in Amazon EventBridge that triggers every Saturday. Configure the rule to publish a notification to an SNS topic.
  3. Create an SNS subscription to a message fanout that sends notifications to subscribers every Saturday.
  4. Use AWS Step Functions scheduling to run a step every Saturday. Configure the step to publish a message to an SNS topic.

Answer(s): B

Explanation:

Per the AWS Cloud Operations and Event Management documentation, Amazon EventBridge provides native scheduling capabilities that can trigger events at defined intervals--such as weekly, daily, or cron-based schedules.

Creating an EventBridge rule that runs every Saturday and publishes a message to an SNS topic fully automates the notification process without maintaining servers or manual jobs. This approach is serverless, highly reliable, and fully managed by AWS.

By contrast:

EC2 cron jobs (Option A) require instance management, patching, and cost overhead.

SNS subscriptions (Option C) handle message delivery, not scheduling.

Step Functions (Option D) are designed for complex workflows, not simple scheduled triggers.

Thus, Option B provides the most operationally efficient CloudOps solution by integrating EventBridge scheduled events with SNS topics for automated, recurring notifications.


Reference:

AWS Cloud Operations & Event Automation Guide ­ Scheduling Tasks and Notifications Using EventBridge and SNS



Viewing page 11 of 34
Viewing questions 51 - 55 out of 165 questions


Post your Comments and Discuss Amazon AWS Certified CloudOps Engineer - Associate SOA-C03 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!