<span dir="LTR">You are developing a web application in AWS. You need to create a CloudWatch custom metric for the application and publish the metric data to AWS via AWS CLI. You know that for metrics produced by AWS, the metrics data have a one-minute granularity. However, this standard resolution is not enough for your custom metric as you wish to get more immediate insight into the application`s sub-minute activity. A high resolution with a granularity of one second is required for the metric. How would you implement this?</span>

Answer options:

A.No action is required as AWS CLI put-metric-data publishes the metric data with a resolution of 1 second by default.
B.In the CloudWatch metric graph, modify the resolution setting to 1 second interval and zoom in to see the metric in detail.
C.Add the --dimensions=1 option in the AWS CLI put-metric-data to specify the metric as a high-resolution metric.
D.When using the AWS CLI put-metric-data to publish the metric data, set the StorageResolution option to 1 second to specify the metric as a high-resolution metric.

Correct Answer : D
Option A is incorrect because by default, AWS CLI put-metric-data sets the resolution to 60 seconds and the metric has a one-minute granularity.
Option B is incorrect because you need to modify the AWS CLI put-metric-data for the high resolution. You cannot set the resolution in the CloudWatch metric graph.
Option C is incorrect because the “--dimensions” argument expands on the identity of a metric using a Name=Value pair, separated by commas. It does not specify the granularity.
Option D is CORRECT because the StorageResolution option is used to specify the resolution. When this option is set to 1, CloudWatch stores the metric at 1-second resolution.
Reference:
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html
https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/put-metric-data.html