Q64 — AWS SAA-C03 Ch.1

Question 64 of 65 | ← Chapter 1

Q64. A company observes an increase in Amazon EC2 costs in its most recent bill. The billing team notices unwanted vertical scaling of instance types for a couple of EC2 instances. A solutions architect needs to create a graph comparing the last 2 months of EC2 costs and perform an in- depth analysis to identity the root cause of the vertical scaling. How should the solutions architect generate the information with the LEAST operational overhead?

Correct Answer: B. Use Cost Explorer's granular filtering feature to perform an in-depth analysis of EC2 costs based on instance types.

Explanation

To generate the information with the least operational overhead and perform an in-depth analysis of EC2 costs based on instance types, the solutions architect should choose option B: Use Cost Explorer's granular filtering feature. Here's why option B is the best choice: B. Use Cost Explorer's granular filtering feature to perform an in-depth analysis of EC2 costs based on instance types.- Cost Explorer provides a powerful set of tools for analyzing your AWS costs and usage. It allows you to filter and group costs based on various dimensions, including instance types. By utilizing the granular filtering feature, you can specifically isolate and analyze EC2 costs based on instance types, which will help identify the instances that have experienced vertical scaling.- Cost Explorer provides visualizations and graphs that can help you compare costs over different time periods, such as the last 2 months. This will enable you to identify any cost increases and pinpoint the instances that have undergone vertical scaling.- Cost Explorer is built-in within the AWS Management Console, making it easily accessible and reducing the need for additional setup or operational overhead. Options A, C, and D are not the most efficient choices for this scenario: A. Using AWS Budgets to create a budget report and compare costs based on instance types may provide high-level cost insights, but it may not offer the level of granularity required for an in-depth analysis of EC2 costs based on instance types. C. Using graphs from the AWS Billing and Cost Management dashboard may give a general overview of EC2 costs but may lack the necessary filtering and granularity to perform a detailed analysis based on instance types. D. Using AWS Cost and Usage Report to create a report and send it to an Amazon S3 bucket and then using Amazon QuickSight with S3 as a source can be a valid approach, but it involves additional steps and configuration. It may introduce more operational overhead compared to using Cost Explorer directly.