Free AWS Certified CloudOps Engineer - Associate SOA-C03 Exam Braindumps
AWS Certified CloudOps Engineer - Associate Questions 66–70 (page: 15)

Updated On: 12-Mar-2026

To comply with regulations, a SysOps administrator needs to back up an Amazon EC2 Amazon Machine Image (AMI) to an Amazon S3 bucket. If the SysOps administrator restores the AMI from the bucket in the future, the AMI must use the same AMI image ID as the original AMI.

Which solution will meet this requirement?

  1. Create a copy of the AMI. Specify the destination S3 bucket. Set the launch permissions to implicit.
  2. Archive the snapshot that is associated with the AMI. Specify the S3 bucket as the archive destination.
  3. Create a store image task. Specify the image ID and the destination S3 bucket.
  4. Use the AWS CLI copy-image command. Specify the image ID and the destination S3 bucket.

Answer(s): C

Explanation:

Comprehensive and Detailed Explanation From Exact Extract of AWS CloudOps Documents:

The correct answer is C. Create a store image task. Specify the image ID and the destination S3 bucket, because this is the only AWS-supported solution that allows an AMI to be backed up to Amazon S3 and later restored while preserving the original AMI ID. This capability is essential for regulatory and compliance requirements where immutable identifiers must be retained.

According to AWS CloudOps documentation for Amazon EC2 AMI lifecycle management, the AMI store and restore feature is specifically designed for long-term retention, audit, and compliance scenarios.
When an AMI is stored using a store image task, AWS packages the AMI's configuration, metadata, and associated snapshots and saves them as encrypted objects in an Amazon S3 bucket.
When the AMI is restored, AWS explicitly states that the restored AMI retains the same AMI ID as the original image, ensuring continuity for compliance tracking and operational dependencies.

Option A is incorrect because copying an AMI always results in a new AMI ID, even when copied within the same AWS Region. Option B is incorrect because archiving snapshots to Amazon S3 does not preserve AMI metadata or identity; restoring from snapshots requires creating a new AMI with a different ID. Option D is incorrect because the copy-image command is intended for cross-Region or cross-account AMI duplication and also generates a new AMI ID.

AWS CloudOps best practices clearly identify store image tasks as the correct mechanism when AMI identity preservation is required for governance, auditability, and compliance controls.


Reference:

Amazon EC2 User Guide ­ AMI Store and Restore

AWS SysOps Administrator Study Guide ­ AMI Management and Compliance

AWS Well-Architected Framework ­ Operational Excellence and Governance



Optimization]

A company runs a high performance computing (HPC) data-processing application on Amazon EC2 instances in one Availability Zone within a development environment. The application uses a dataset that the company stores on an Amazon S3 general purpose bucket in the same AWS Region as the EC2 instances.

A SysOps administrator must improve the application's performance for retrieval of objects from Amazon S3.

Which solution will meet these requirements?

  1. Enable S3 Transfer Acceleration for the S3 bucket. Create an S3 access point for the bucket. Update the application to use the access point.
  2. Create an S3 Lifecycle configuration for the S3 bucket to move all objects to the S3 Express One Zone storage class. Update the application to use an S3 Regional endpoint.
  3. Create a second general purpose S3 bucket in the same Region. Copy the objects from the original bucket to the new bucket. Use the S3 Express One Zone storage class to store the objects in the new bucket. Update the application to use an S3 Regional endpoint.
  4. Create an S3 directory bucket in the same Availability Zone. Import objects from the original bucket to the new bucket. Use the S3 Express One Zone storage class to store the objects in the new bucket. Update the application to use an S3 Zonal endpoint.

Answer(s): D

Explanation:

Comprehensive and Detailed Explanation From Exact Extract of AWS CloudOps Documents:

The correct answer is D because Amazon S3 Express One Zone with directory buckets and zonal endpoints is specifically designed for single­Availability Zone, high-performance workloads such as HPC, machine learning, and analytics applications running on Amazon EC2. AWS CloudOps documentation states that S3 Express One Zone delivers single-digit millisecond latency and up to 10x higher request performance compared to general purpose S3 buckets when data is accessed from the same Availability Zone.

An S3 directory bucket is required to use the S3 Express One Zone storage class. These buckets are explicitly associated with a single Availability Zone and use zonal endpoints, which eliminate cross-AZ network hops and significantly reduce latency. Importing the data from the existing general purpose bucket ensures compatibility while achieving maximum throughput and lowest latency.

Option A is incorrect because S3 Transfer Acceleration is optimized for long-distance, internet-based transfers, not for in-Region HPC workloads. Option B is incorrect because lifecycle policies cannot move objects into S3 Express One Zone, and S3 Express One Zone does not use Regional endpoints. Option C is incorrect because general purpose buckets do not support zonal endpoints and therefore cannot achieve the same performance benefits.

AWS CloudOps performance optimization guidance clearly identifies S3 directory buckets with S3 Express One Zone and zonal endpoints as the optimal architecture for high-throughput, low-latency workloads in a single Availability Zone.


Reference:

Amazon S3 User Guide ­ S3 Express One Zone and Directory Buckets

AWS SysOps Administrator Study Guide ­ Storage Performance Optimization

AWS Well-Architected Framework ­ Performance Efficiency Pillar



A company has a new security policy that requires all Amazon Elastic Block Store (Amazon EBS) volumes to be encrypted at rest. The company needs to use a custom key policy to manage access to the encryption keys. The company must rotate the keys once each year.

Which solution will meet these requirements with the LEAST operational overhead?

  1. Create AWS KMS symmetric customer managed keys. Enable automatic key rotation.
  2. Use AWS owned AWS KMS keys across the company's AWS environment.
  3. Create AWS KMS asymmetric customer managed keys. Enable automatic key rotation.
  4. Create AWS KMS symmetric customer managed keys by using imported key material. Rotate the keys on a yearly basis.

Answer(s): A

Explanation:

Comprehensive and Detailed Explanation From Exact Extract of AWS CloudOps Documents:

The correct answer is A because AWS KMS symmetric customer managed keys with automatic key rotation provide encryption, access control, and compliance with minimal operational effort. AWS CloudOps documentation states that Amazon EBS encryption supports AWS KMS symmetric keys only, and customer managed keys allow administrators to define custom key policies to control access.

Automatic key rotation is supported for symmetric customer managed keys and rotates the backing key material once every year, fully satisfying the company's rotation requirement without manual intervention. This approach minimizes operational overhead while maintaining strong security controls and auditability.

Option B is incorrect because AWS owned keys do not allow custom key policies and therefore cannot meet the access control requirement. Option C is incorrect because asymmetric KMS keys are not supported for EBS encryption. Option D is incorrect because imported key material requires manual rotation and re-import, increasing operational complexity and risk.

AWS CloudOps security best practices strongly recommend customer managed symmetric keys with automatic rotation when organizations need fine-grained access control, regulatory compliance, and low maintenance overhead.


Reference:

AWS KMS Developer Guide ­ Customer Managed Keys and Rotation

Amazon EBS User Guide ­ Encryption at Rest

AWS SysOps Administrator Study Guide ­ Security and Key Management



A SysOps administrator is configuring an Auto Scaling group of Amazon EC2 instances for an application. The average CPU utilization of the instances in the Auto Scaling group must remain at approximately 40% when the load on the application changes.

Which solution will meet this requirement in the MOST operationally efficient manner?

  1. Create a scheduled scaling action. Configure the action to run at times when the application typically experiences an increase in traffic.
  2. Configure a simple scaling policy. Create an Amazon CloudWatch alarm that enters ALARM state when CPU utilization is greater than 40%. Associate the alarm with the scaling policy.
  3. Configure a step scaling policy. Create an Amazon CloudWatch alarm that enters ALARM state when CPU utilization is greater than 40%. Associate the alarm with the scaling policy.
  4. Configure a target tracking scaling policy. Specify a target value of 40 for average CPU utilization.

Answer(s): D

Explanation:

Comprehensive and Detailed Explanation From Exact Extract of AWS CloudOps Documents:

The correct answer is D because target tracking scaling policies are designed to automatically maintain a specific metric at a desired target value with the least administrative effort. AWS CloudOps documentation states that target tracking works like a thermostat, continuously adjusting capacity to keep the selected metric close to the defined target.

By specifying a target value of 40% average CPU utilization, the Auto Scaling group automatically scales out or in based on real-time demand without requiring manual thresholds, multiple alarms, or predefined scaling steps. This approach is fully managed by AWS and is the most operationally efficient option.

Option A is incorrect because scheduled scaling is based on predictable traffic patterns and cannot respond dynamically to real-time load changes. Option B is incorrect because simple scaling reacts only after an alarm is triggered and does not continuously maintain a target value. Option C is less efficient because step scaling requires additional configuration and tuning of scaling steps.

AWS CloudOps best practices clearly recommend target tracking scaling policies for maintaining steady performance metrics with minimal operational overhead.


Reference:

Amazon EC2 Auto Scaling User Guide ­ Target Tracking Policies

AWS SysOps Administrator Study Guide ­ Auto Scaling and Automation

AWS Well-Architected Framework ­ Operational Excellence and Performance Efficiency



A company runs applications on Amazon EC2 instances. Many of the instances are not patched. The company has a tagging policy. All the instances are tagged with details about the owners, application, and environment. AWS Systems Manager Agent (SSM Agent) is installed on all the instances.

A SysOps administrator must implement a solution to automatically patch all existing and future instances that have "Prod" in the environment tag. The SysOps administrator plans to create a patch policy in Systems Manager Patch Manager.

Which solution will meet the patching requirements with the LEAST operational overhead?

  1. Define targets of the patch policy by specifying node tags that match the company's tagging strategy.
  2. Configure an AWS Lambda function to scan for new instances and to add the instances to the targets of the patch policy.
  3. Create resource groups. Add the existing instances to the resource groups. Configure an AWS Lambda function to scan for new instances and to add the instances to the resource groups at regular intervals. Attach the resource groups to the patch policy.
  4. Create resource groups. Add the existing instances to the resource groups. Create an Amazon EventBridge rule that uses an appropriately defined filter to add new instances to the resource groups. Attach the resource groups to the patch policy.

Answer(s): A

Explanation:

Comprehensive and Detailed Explanation From Exact Extract of AWS CloudOps Documents:

The correct answer is A because AWS Systems Manager Patch Manager natively supports tag-based targeting, which automatically includes both existing and future instances that match specified tag criteria. AWS CloudOps documentation states that patch policies can target managed nodes by instance tags, allowing administrators to dynamically scope patching operations without additional automation.

By defining the patch policy target as instances with an environment tag value of "Prod," Patch Manager automatically applies patch baselines to all matching instances. Any new EC2 instance launched with the same tag is included automatically, requiring no manual intervention or additional services. This approach delivers the least operational overhead while remaining fully scalable and compliant.

Options B, C, and D are incorrect because they introduce unnecessary complexity by adding AWS Lambda functions, resource groups, or EventBridge rules. AWS CloudOps best practices emphasize using native Systems Manager capabilities whenever possible to reduce operational burden and failure points.


Reference:

AWS Systems Manager User Guide ­ Patch Manager Tag-Based Targeting

AWS SysOps Administrator Study Guide ­ Automation and Patch Management

AWS Well-Architected Framework ­ Operational Excellence



Viewing page 15 of 34
Viewing questions 71 - 75 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!