Examkin

Question

Difficulty: MediumAWS Compute Optimizer and Right-Sizing

A SysOps Administrator is optimizing the performance and cost of a transactional database hosted on an Amazon EC2 instance. The database is currently backed by a 1 TiB1\text{ TiB} Amazon EBS io2\text{io2} volume configured with 10,00010,000 Provisioned IOPS. Over the past 1414 days, Amazon CloudWatch metrics indicate that the volume's IOPS utilization consistently peaks at 2,2002,200 IOPS, and throughput peaks at 150 MiB/s150\text{ MiB/s}. AWS Compute Optimizer flags this volume as 'Overprovisioned'.

Which action should the administrator take to implement Compute Optimizer's recommendation and optimize costs without impacting application performance?

  1. Modify the EBS volume in-place to change the volume type to gp3, configuring the volume with 3,000 IOPS and 150 MiB/s throughput.Answer
  2. B
    Purchase an EC2 Instance Savings Plan to apply discounted rates to the EBS io2 volume while maintaining the current configuration.
  3. C
    Configure an AWS Budgets cost alert to trigger an automation that dynamically scales the provisioned IOPS of the io2 volume.
  4. D
    Activate cost allocation tags on the EBS volume in the AWS Billing Console to automatically apply the rightsizing configuration.

Answer

Modify the EBS volume in-place to change the volume type to gp3, configuring the volume with 3,000 IOPS and 150 MiB/s throughput.
Modifying the EBS volume in-place to change the volume type to gp3 with 3,000 IOPS and 150 MiB/s throughput is correct because it aligns with Compute Optimizer's recommendation. A gp3 volume offers 3,000 baseline IOPS and 125 MiB/s throughput for free. Increasing the throughput to 150 MiB/s satisfies the database's peak performance demands (2,200 IOPS and 150 MiB/s) while significantly reducing provisioned costs compared to the expensive io2 volume.

Step-by-Step Solution

1
Analyze the peak workload metrics from the past 1414 days, identifying that the database requires a maximum of 2,2002,200 IOPS and 150 MiB/s150\text{ MiB/s} throughput.
The requirements are within the capabilities of a gp3 volume, which offers 3,0003,000 baseline IOPS and customizable throughput.
This establishes the minimum performance target needed to maintain database performance without overprovisioning.
2
Determine the optimal configuration for a gp3 volume to meet these metrics.
A gp3 volume configured with 3,0003,000 baseline IOPS (included) and 150 MiB/s150\text{ MiB/s} throughput (25 MiB/s25\text{ MiB/s} provisioned above the baseline 125 MiB/s125\text{ MiB/s}).
This configuration satisfies both the peak IOPS and peak throughput requirements while avoiding excess provisioned resources.
3
Perform an in-place EBS volume modification to change the volume type from io2 to gp3 with the determined settings.
The volume type is modified online without performance degradation or downtime.
EBS elastic volumes allow live modification of volume types, size, IOPS, and throughput.

Key Concept

AWS Compute Optimizer helps right-size EBS volumes by analyzing performance metrics and suggesting cost-effective alternatives like gp3 for overprovisioned io1/io2 volumes.
Rate this question

Topics

AWS Compute Optimizer and Right-Sizing

More questions from this topic