Free AWS Certified CloudOps Engineer - Associate SOA-C03 Exam Braindumps
AWS Certified CloudOps Engineer - Associate Questions 41–45 (page: 10)

Updated On: 12-Mar-2026

Optimization]

An AWS Lambda function is intermittently failing several times a day. A CloudOps engineer must find out how often this error occurred in the last 7 days.

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

  1. Use Amazon Athena to query the Amazon CloudWatch logs that are associated with the Lambda function.
  2. Use Amazon Athena to query the AWS CloudTrail logs that are associated with the Lambda function.
  3. Use Amazon CloudWatch Logs Insights to query the associated Lambda function logs.
  4. Use Amazon OpenSearch Service to stream the Amazon CloudWatch logs for the Lambda function.

Answer(s): C

Explanation:

The AWS Cloud Operations and Monitoring documentation states that Amazon CloudWatch Logs

Insights provides a purpose-built query engine for analyzing and visualizing log data directly within CloudWatch. For Lambda, all invocation results (including errors) are automatically logged to CloudWatch Logs.

By querying these logs with CloudWatch Logs Insights, the CloudOps engineer can efficiently count the number of "ERROR" or "Exception" occurrences over the past 7 days using simple SQL-like commands. This method is serverless, cost-efficient, and real-time.

Athena (Options A and B) would require exporting data to Amazon S3, and OpenSearch (Option D) adds unnecessary operational complexity.

Thus, Option C provides the most efficient and native AWS CloudOps approach for rapid Lambda error analysis.


Reference:

AWS Cloud Operations & Monitoring Guide ­ Analyzing Lambda Logs with CloudWatch Logs Insights



A company uses AWS Organizations to manage multiple AWS accounts. A CloudOps engineer must identify all IPv4 ports open to 0.0.0.0/0 across the organization's accounts.

Which solution will meet this requirement with the LEAST operational effort?

  1. Use the AWS CLI to print all security group rules for review.
  2. Review AWS Trusted Advisor findings in an organizational view for the Security Groups ­ Specific Ports Unrestricted check.
  3. Create an AWS Lambda function to gather security group rules from all accounts. Aggregate the findings in an Amazon S3 bucket.
  4. Enable Amazon Inspector in each account. Run an automated workload discovery job.

Answer(s): B

Explanation:

According to AWS Cloud Operations and Governance documentation, AWS Trusted Advisor provides automated checks for security group rules across all accounts, including identifying ports open to 0.0.0.0/0.

When viewed in organizational mode, Trusted Advisor integrates with AWS Organizations, allowing administrators to access organization-wide security findings from a central management account. This approach requires no custom code, additional infrastructure, or manual inspection, providing immediate visibility and the lowest operational overhead.

AWS CLI scripts (Option A) or Lambda automation (Option C) introduce additional maintenance, and Amazon Inspector (Option D) is focused on instance-level vulnerabilities, not network access rules.

Therefore, Option B is the AWS-recommended CloudOps best practice for centralized and low-effort open-port auditing.


Reference:

AWS Cloud Operations & Governance Guide ­ Using Trusted Advisor Organizational View for Security Group Port Checks



A company hosts a static website in an Amazon S3 bucket, accessed globally via Amazon CloudFront. The Cache-Control max-age header is set to 1 hour, and Maximum TTL is set to 5 minutes. The CloudOps engineer observes that CloudFront is not caching objects for the expected duration.

What is the reason for this issue?

  1. The Expires header has been set to 3 hours.
  2. Cached assets are not expiring in the edge location.
  3. Cache invalidation is missing in the CloudFront configuration.
  4. Cache-duration settings conflict with each other.

Answer(s): D

Explanation:

As per the AWS Cloud Operations and Content Delivery documentation, CloudFront determines cache behavior by evaluating both origin headers (e.g., Cache-Control and Expires) and distribution- level TTL settings.

When Cache-Control max-age conflicts with the Maximum TTL configured in CloudFront, the shorter TTL value takes precedence. This results in CloudFront caching content for only 5 minutes instead of 1 hour, despite the origin headers suggesting a longer duration.

AWS documentation explicitly states: "When both origin cache headers and CloudFront TTL settings are defined, CloudFront uses the most restrictive caching period." This mismatch causes the perceived performance drop, as CloudFront frequently revalidates content.

Therefore, Option D is correct -- cache-duration settings conflict with each other, leading to unexpected caching behavior.


Reference:

AWS Cloud Operations & Content Delivery Guide ­ Interaction Between Cache-Control Headers and CloudFront TTL Settings



A company runs applications on Amazon EC2 instances. The company wants to ensure that SSH ports on the EC2 instances are never open. The company has enabled AWS Config and has set up the restricted-ssh AWS managed rule.

A CloudOps engineer must implement a solution to remediate SSH port access for noncompliant security groups.

What should the engineer do to meet this requirement with the MOST operational efficiency?

  1. Configure the AWS Config rule to identify noncompliant security groups. Configure the rule to use the AWS-PublishSNSNotification AWS Systems Manager Automation runbook to send notifications about noncompliant resources.
  2. Configure the AWS Config rule to identify noncompliant security groups. Configure the rule to use the AWS-DisableIncomingSSHOnPort22 AWS Systems Manager Automation runbook to remediate noncompliant resources.
  3. Make an AWS Config API call to search for noncompliant security groups. Disable SSH access for noncompliant security groups by using a Deny rule.
  4. Configure the AWS Config rule to identify noncompliant security groups. Manually update each noncompliant security group to remove the Allow rule.

Answer(s): B

Explanation:

The AWS Cloud Operations and Governance documentation specifies that AWS Config can be paired with AWS Systems Manager Automation runbooks for automatic remediation of noncompliant resources.

For SSH restrictions, the restricted-ssh managed rule detects any security group allowing inbound traffic on port 22. To automatically remediate these findings, AWS provides the AWS- DisableIncomingSSHOnPort22 runbook. This runbook programmatically removes inbound rules that allow port 22 traffic from affected security groups.

This approach achieves continuous compliance with minimal human intervention. By contrast, sending notifications (Option A) does not enforce remediation, API-based scripts (Option C) add operational overhead, and manual remediation (Option D) violates automation best practices.

Therefore, the most efficient CloudOps solution is Option B, using AWS Config with the AWS- DisableIncomingSSHOnPort22 automation runbook for automatic, scalable enforcement.


Reference:

AWS Cloud Operations & Governance Guide ­ Automated Security Remediation Using Config Managed Rules and Systems Manager Runbooks



A CloudOps engineer created a VPC with a private subnet, a security group allowing all outbound traffic, and an endpoint for EC2 Instance Connect in the private subnet. The EC2 instance was launched without an SSH key pair, using the same subnet and security group. However, the engineer cannot connect via EC2 Instance Connect endpoint.

How can the CloudOps engineer connect to the instance?

  1. Create an inbound rule in the security group to allow HTTPS traffic on port 443 from the private subnet.
  2. Create an inbound rule in the security group to allow SSH traffic on port 22 from the private subnet.
  3. Create an IAM instance profile that allows AWS Systems Manager Session Manager to access the EC2 instance. Associate the instance profile with the instance.
  4. Recreate the EC2 instance. Associate an SSH key pair with the instance.

Answer(s): C

Explanation:

According to the AWS Cloud Operations and EC2 Connectivity documentation, EC2 Instance Connect Endpoint allows access to instances without internet exposure or open SSH ports. However, for successful connectivity, the EC2 instance must have Systems Manager permissions through an IAM instance profile.

If no IAM instance profile is attached, the instance cannot establish a control channel with the Systems Manager service, and EC2 Instance Connect cannot authenticate the session.

Opening port 22 (Option B) is unnecessary and contradicts the private subnet design. HTTPS rules (Option A) are irrelevant because EC2 Instance Connect communicates through AWS APIs, not direct HTTPS connections. Recreating the instance with a key pair (Option D) bypasses the intended keyless connection mechanism.

Therefore, Option C -- attaching an IAM instance profile with Systems Manager permissions -- enables secure, private access through EC2 Instance Connect Endpoint.


Reference:

AWS Cloud Operations & EC2 Connectivity Guide ­ Enabling EC2 Instance Connect Endpoint Access via Systems Manager Permissions



Viewing page 10 of 34
Viewing questions 46 - 50 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!