An application that you are managing has EC2 instances & Dynamo OB tables deployed to several AWS Regions
In order to monitor the performance of the application globally, you would like to see two graphs 1) Avg CPU
Utilization across all EC2 instances and 2) Number of Throttled Requests for all DynamoDB tables.
How can you accomplish this?
A.
Tag your resources with the application name, and select the tag name as the dimension in the Cloudwatch
Management console to view the respective graphs
B.
Use the Cloud Watch CLI tools to pull the respective metrics from each regional endpoint Aggregate the
data offline & store it for graphing in CloudWatch.
C.
Add SNMP traps to each instance and DynamoDB table Leverage a central monitoring server to capture data
from each instance and table Put the aggregate data into Cloud Watch for graphing.
D.
Add a CloudWatch agent to each instance and attach one to each DynamoDB table. When configuring the
agent set the appropriate application name & view the graphs in CloudWatch.
Correct answer should be A. When you turn on detailed monitoring in Cloudwatch, you can get 1) Avg CPU Utilization across all EC2 instances and 2) Number of Throttled Requests for all DynamoDB tables
Reference: http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/GetSingleMetricAllDimensions.html
1
0
I think answer is B.
The questions states “deployed to several regions”. In the GetSingleMetricAllDimensions link, it states “Amazon CloudWatch does not aggregate data across regions. Therefore, metrics are completely separate between regions”.
So we can use CLI and API to get the metrics from each regional endpoint.
0
0
I agree ,the answer is B.
0
0
Stuart is right. B is the answer.
Because:
A) is out – CW metrics are per region
C) You can’t add SNMP to DynamoDB as it’s a managed service and you have no system level access to install or configure SNMP
D) is the same as (C) – you can’t add a CloudWatch agent to DynamoDB.
0
0
A
https://d0.awsstatic.com/aws-answers/AWS_Tagging_Strategies.pdf
Tags for AWS Console Organization
Using this tool, customers can consolidate and view data for applications that consist of multiple services, resources, and regions in one place.
0
0
A
0
0
Cross region dashboard is possible with cloudwatch.
Ans is A
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cross_region_dashboard.html
0
0
A still don’t look correct.
Reason being, that although you can create dashboard for multiple region, but that just showing that from multiple regions in one dashboard, you can’t still aggregate the data.
Question says ‘1) Avg CPU
Utilization across all EC2 instances and 2) Number of Throttled Requests for all DynamoDB tables.’
Now you can can’t have average CPU across EC2 instances and DynamoDB tables spread across regions using CloudWatch.
So for above reasons, the B looks the closest match to the correct answer as your only options appear to be collecting the information first and then plotting it afterwards .
Also issue with B is probably ‘Aggregate the data offline’ , don’t know what offline would mean here, but still B is the best possible match for stated requirement in the question.
0
0
c
0
0
I think A is suitable for this case.
The goal is monitor application globally. It could get via tags resources on multiple regions.
0
0
b should be the right ans
0
0
Seems A is invalidated by http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/GetSingleMetricAllDimensions.html
“You can aggregate the metrics for AWS resources across multiple resources. Note that Amazon CloudWatch cannot aggregate data across regions. Metrics are completely separate between regions.
For example, you can aggregate statistics for your EC2 instances that have detailed monitoring enabled. Instances that use basic monitoring are not included. Therefore, you must enable detailed monitoring (at an additional charge), which provides data in 1-minute periods. For more information, see Enable or Disable Detailed Monitoring for Your Instances in the Amazon EC2 User Guide for Linux Instances.”
That leaves B as the only suitable option, I guess.
0
0
Answer is B. http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tools.CLI.html
0
0
A: – not correct because resources are in different regions. CW work separately for each region.
B:- Correct, aggregate the data off-line.
c:- CW dont use SNMP.
D: -We use CW agent for log transfer from ec2 instances. Also, DynamoDB dont use agent.
0
0
B
0
0
Answer – B
Option A is incorrect because CloudWatch metrics are regional.
Option C is incorrect because we can’t add SNMP traps to DynamoDB since it is a managed service.
Option D incorrect because we can’t add agents to DynamoDB since it is a managed service.
CloudWatch allows publishing custom metrics with put-metric-data CLI command
Data can also be aggregated before being published to CloudWatch
Aggregating data minimizes the number of calls reducing it to a single call per minute with the statistic set of data
Statistics include Sum, Average, Minimum, Maximum, Data Sample
1
0