Examkin

Question

Difficulty: MediumAWS Compute Optimizer and Right-Sizing

A SysOps Administrator is managing resource optimization across a multi-account organization using AWS Organizations. The administrator notices that AWS Compute Optimizer is generating EC2 rightsizing recommendations based only on CPU and network metrics, failing to analyze memory utilization. Additionally, several member accounts are running gp2 EBS volumes that are overprovisioned for size just to achieve higher throughput. Which TWO actions should the SysOps Administrator take to resolve these issues?

  1. Deploy the Amazon CloudWatch agent to the EC2 instances in the member accounts to collect and report memory utilization metrics.Answer
  2. B
    Enable CloudWatch detailed monitoring on the EC2 instances in the member accounts to expose memory metrics to AWS Compute Optimizer.
  3. Modify the EBS volumes from gp2 to gp3 to allow independent scaling of throughput and size while reducing storage costs.Answer
  4. D
    Configure AWS Budgets alerts to monitor EC2 memory utilization metrics and automatically downsize underutilized instances.
  5. E
    Purchase Compute Savings Plans to automatically implement rightsizing recommendations for the EC2 instances and EBS volumes.

Answer

Deploy the Amazon CloudWatch agent to the EC2 instances in the member accounts to collect and report memory utilization metrics, and modify the EBS volumes from gp2 to gp3 to allow independent scaling of throughput and size while reducing storage costs.
Deploying the Amazon CloudWatch agent is correct because memory is an operating system-level metric that is not visible to the hypervisor. AWS Compute Optimizer requires the agent to be configured to receive these metrics. Modifying gp2 volumes to gp3 is correct because gp3 volumes decouple throughput and IOPS from storage capacity, enabling cost savings and rightsizing without overprovisioning storage size.

Step-by-Step Solution

1
Identify the cause of missing memory metrics in AWS Compute Optimizer.
Realize that memory metrics are OS-level metrics and require the Amazon CloudWatch agent to be installed on the EC2 instances.
AWS Compute Optimizer cannot access memory utilization metrics by default because they are not monitored at the hypervisor level.
2
Identify the optimization strategy for gp2 volumes overprovisioned for throughput.
Choose gp3 volumes as the target class, which allows independent provisioning of IOPS and throughput without scaling volume size.
Migrating to gp3 directly solves the issue of overprovisioning storage size solely to get higher throughput.

Key Concept

AWS Compute Optimizer rightsizing requirements and EBS volume performance optimization.
Rate this question

Topics

AWS Compute Optimizer and Right-Sizing

More questions from this topic