Management has reported an increase in the monthly bill from Amazon Web Services, and they are extremely concerned with this increased cost.
Management has asked you to determine the exact cause of this increase.
After reviewing the billing report, you notice an increase in the data transfer cost.
How can you provide management with a better insight into data transfer use?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - C.
You can publish your own metrics to CloudWatch using the AWS CLI or an API.
You can view statistical graphs of your published metrics with the AWS Management Console.
CloudWatch stores data about a metric as a series of data points.
Each data point has an associated time stamp.
You can even publish an aggregated set of data points called a statistic set.
If you have custom metrics specific to your application, you can give a breakdown to the management on the exact issue.
Option A won't be sufficient to provide better insights.
Option B is an overhead when you can make the application publish custom metrics.
Option D is invalid because just the ELB metrics will not give the entire picture.
For more information on custom metrics, please refer to the below document link: from AWS.
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.htmlWhen faced with an increased AWS bill, it's important to identify the specific cause of the increase to take the necessary steps to address the issue. In this case, the cause of the increase is an increase in data transfer costs.
To provide management with a better insight into data transfer use, there are several options available, including:
A. Update your Amazon CloudWatch metrics to use five-second granularity, which will give better detailed metrics that can be combined with your billing data to pinpoint anomalies.
This option involves updating the Amazon CloudWatch metrics to use a more granular level of detail, allowing for more detailed metrics. By doing this, you can identify specific anomalies in your data transfer usage that may be causing the increased costs.
B. Use Amazon CloudWatch Logs to run a map-reduce on your logs to determine high usage and data transfer.
Amazon CloudWatch Logs provides a central location to store and analyze logs from your applications and services. By running a map-reduce on your logs, you can identify areas of high usage and data transfer, providing insight into where the increased costs are coming from.
C. Deliver custom metrics to Amazon CloudWatch per application that breaks down application data transfer into multiple, more specific data points.
This option involves delivering custom metrics to Amazon CloudWatch that break down data transfer usage by application, providing more specific data points. By doing this, you can identify which applications are using the most data transfer and take appropriate action to address the issue.
D. Using Amazon CloudWatch metrics, pull your Elastic Load Balancing outbound data transfer metrics monthly and include them with your billing report to show which application is causing higher bandwidth usage.
This option involves using Amazon CloudWatch metrics to pull Elastic Load Balancing outbound data transfer metrics monthly and including them with your billing report. By doing this, you can identify which applications are causing higher bandwidth usage and take appropriate action to address the issue.
In conclusion, to provide management with a better insight into data transfer use, you can use any of the options mentioned above, depending on your specific situation. Each option provides a unique set of benefits and can help you identify the specific cause of the increased costs, allowing you to take appropriate action to address the issue.