Examkin

Question

Difficulty: MediumAWS Compute Optimizer and Right-Sizing

A SysOps Administrator is managing an application running on an Amazon EC2 instance. The application has been experiencing performance degradation, and AWS Compute Optimizer categorizes the instance as underprovisioned. The administrator observes that the CPU utilization regularly peaks at 95%95\%, while the memory utilization remains below 30%30\%. The memory utilization metrics are currently visible in Compute Optimizer because the Unified CloudWatch Agent is installed on the instance. Which actions should the SysOps Administrator take to right-size the instance and ensure future memory utilization metrics continue to be collected? (Select TWO.)

  1. Resize the EC2 instance to a compute-optimized instance family, such as c5, or a larger instance size in the same family.Answer
  2. Verify that the IAM role attached to the EC2 instance includes the CloudWatchAgentServerPolicy managed policy.Answer
  3. C
    Change the instance type to a memory-optimized instance family, such as r5, to address the performance degradation.
  4. D
    Enable detailed monitoring for the EC2 instance in the Amazon CloudWatch console to permit the ingestion of memory utilization metrics.
  5. E
    Configure an AWS Budgets alert to automatically scale the EC2 instance to a larger size when CPU utilization exceeds 90%90\%.

Answer

Resize the EC2 instance to a compute-optimized instance family (such as c5) or a larger instance size in the same family, and verify that the IAM role attached to the EC2 instance includes the CloudWatchAgentServerPolicy managed policy.
The correct options are resizing the EC2 instance to a compute-optimized instance family (such as c5) or a larger instance size in the same family, and verifying that the IAM role attached to the EC2 instance includes the CloudWatchAgentServerPolicy managed policy. The high CPU utilization (95%95\%) combined with low memory utilization (30%30\%) indicates that the instance is CPU-bound, making a compute-optimized instance family the correct right-sizing choice. Because memory is an OS-level metric, AWS Compute Optimizer requires the Unified CloudWatch Agent to report these metrics. For the agent to successfully send metrics to CloudWatch, the EC2 instance's IAM role must contain the CloudWatchAgentServerPolicy policy.

Step-by-Step Solution

1
Analyze the resource utilization metrics reported by AWS Compute Optimizer.
Identify that the CPU utilization is at 95%95\% (underprovisioned) and memory utilization is at 30%30\% (overprovisioned).
This determines that the workload is CPU-bound, meaning a compute-optimized instance type (c5) or a larger size is required to resolve the bottleneck.
2
Determine the requirement for memory metrics collection by AWS Compute Optimizer.
Identify that memory utilization is an OS-level metric not collected by default EC2 metrics, requiring the Unified CloudWatch Agent.
AWS Compute Optimizer needs these memory metrics to make accurate right-sizing recommendations.
3
Verify IAM permissions for the Unified CloudWatch Agent.
Ensure the IAM role attached to the EC2 instance includes the CloudWatchAgentServerPolicy managed policy.
Without this policy, the agent cannot write the custom memory metrics to CloudWatch, causing Compute Optimizer to lose visibility into memory utilization after the resize.

Key Concept

AWS Compute Optimizer rightsizing recommendations for EC2 instances require memory metrics from the Unified CloudWatch Agent, which relies on the CloudWatchAgentServerPolicy IAM policy. The instance type must match the specific bottleneck (CPU-bound vs. memory-bound).
Estimated Time:1m 30s
Rate this question

Topics

AWS Compute Optimizer and Right-Sizing

More questions from this topic