What should the SysOps administrator do to meet these requirements in the MOST operationally efficient way?
Use the monitoring graphs in the EC2 console to view metrics for EBS volumes. Review the consumed space against the provisioned space on each volume. Identify any volumes that have low utilization.
Stop the EC2 instances from the EC2 console. Change the EC2 instance type for Amazon EBS-optimized. Start the EC2 instances.
Opt in to AWS Compute Optimizer. Allow sufficient time for metrics to be gathered. Review the Compute Optimizer findings for EBS volumes.
Install the fio tool onto the EC2 instances and create a .cfg file to approximate the required workloads. Use the benchmark results to gauge whether the provisioned EBS volumes are of the most appropriate type.
Explanations:
Monitoring graphs in the EC2 console provide basic metrics but do not offer a comprehensive cost optimization solution. They focus on space usage, not IOPS or throughput.
Changing the EC2 instance type to EBS-optimized does not directly address cost optimization for EBS volumes. EBS-optimized instances are already standard for performance.
AWS Compute Optimizer provides a detailed analysis of EBS volumes’ performance. It helps identify underused resources and offers recommendations for cost savings.
Using the fio tool is more complex and less operationally efficient than using AWS Compute Optimizer. It requires manual configuration and doesn’t scale as easily.
If memory serves me right, the answer is:
Opt in to AWS Compute Optimizer. Allow sufficient time for metrics to be gathered. Review the Compute Optimizer findings for EBS volumes.