Suggested Answer:B🗳️
The user is allowed to send data up to one-thousandth of a second. CloudWatch aggregates the data by each minute and generates a metric for that. Reference: http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/publishingMetrics.html
When sending custom data metrics to CloudWatch, the allowed time stamp granularity for each data point published for the custom metric is 1 minute.
CloudWatch organizes and aggregates data at one-minute intervals for custom metrics. This means that you can publish data points with a timestamp at one-minute intervals, and CloudWatch will store and display the data based on these one-minute intervals.
Change to D
Standard resolution, with data having a one-minute granularity
High resolution, with data at a granularity of one second
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html
D. 1 second
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html
Metrics produced by AWS services are standard resolution by default. When you publish a custom metric, you can define it as either standard resolution or high resolution. When you publish a high-resolution metric, CloudWatch stores it with a resolution of 1 second, and you can read and retrieve it with a period of 1 second, 5 seconds, 10 seconds, 30 seconds, or any multiple of 60 seconds.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
albert_kuo
10 months, 1 week agoalbert_kuo
6 months, 3 weeks agodballopes
2 years, 4 months agofilipov1
2 years, 6 months agoImranR
2 years, 5 months agojohnyjohny1
2 years, 4 months agoawscertified
2 years, 6 months ago