Question 480:
<span dir="LTR">You are a DevOps consultant. One client uses AWS CLI </span><span dir="LTR">put-metric-data</span><span dir="LTR"> to publish the metric data of an application to CloudWatch every second. The CloudWatch metric stores the data with a resolution of 1 minute. The client worries about the cost of the </span><span dir="LTR">put-metric-data</span><span dir="LTR"> requests and wants to reduce the number of calls to </span><span dir="LTR">put-metric-data</span><span dir="LTR">. In the meantime, the client does not want to lose the data points. Which of the following options would you suggest to address this concern?</span>
Answer options:
A.Aggregate the data in the application and publish the data in one get-metric-statistics call. The AWS CLI call put-metric-data is not needed. B.Aggregate the data before publishing to CloudWatch and put the data into a statistic set that you publish with one put-metric-data call, using the --statistic-values option. C.Put multiple data values in a single put-metric-data call such as --value 2,5,2,7,9. D.No actions are required as CloudWatch metrics are charged based on the number of metrics instead of API requests. There is no need to reduce the number of put-metric-data calls.