How can the user achieve this?

A user has launched 10 instances from the same AMI ID using Auto Scaling. The user is trying to
see the
average CPU utilization across all instances of the last 2 weeks under the CloudWatch console.
How can the user achieve this?

A user has launched 10 instances from the same AMI ID using Auto Scaling. The user is trying to
see the
average CPU utilization across all instances of the last 2 weeks under the CloudWatch console.
How can the user achieve this?

A.
View the Auto Scaling CPU metrics

B.
Aggregate the data over the instance AMI ID

C.
The user has to use the CloudWatchanalyser to find the average data across instances

D.
It is not possible to see the average CPU utilization of the same AMI ID since the instance ID is
different

Explanation:
Amazon CloudWatch is basically a metrics repository. Either the user can send the custom data or
an AWS product can put metrics into the repository, and the user can retrieve the statistics based
on those metrics. The statistics are metric data aggregations over specified periods of time.
Aggregations are made using the namespace, metric name, dimensions, and the data point unit of
measure, within the time period that is specified by the user. To aggregate the data across
instances launched with AMI, the user should select the AMI ID under EC2 metrics and select the
aggregate average to view the data.



Leave a Reply 9

Your email address will not be published. Required fields are marked *


Mohit Gadkari

Mohit Gadkari

CloudAcademy says its B

Harsh

Harsh

I see the point here. You can get CloudWatch metrics at AMI ID level and also at Auto Scale Group level. However, I would go with A as AMI ID is a subset of Auto Scaling service where it would account for not only AMI ID but Instance Type as well.

Stan

Stan

Answer is A to pass exam