Exam AWS-SysOps topic 1 question 779 discussion

I will go with C and E. Enabling Detailed Monitoring does nothing but give you granular visibility on metrics already collected. Memory metrics are custom metrics that are not available whether you use Basic Monitoring or Detail Monitoring. A Custom Metric will require either a CloudWatch Agent or Scripts. When launching the Cloudwatch Agent, you are given an option to determine the granularity with the default being 60 seconds. The metrics_collection_interval field specifies the time interval for the metrics collected, in seconds. By specifying a value of less than 60 for this field, the metrics are collected as high-resolution metrics.

A & C Memory metrics must be published from the agent as it is a custom metric

A. Enable detailed monitoring on the instance within Amazon CloudWatch. Enabling detailed monitoring allows Amazon CloudWatch to collect metrics at a higher frequency, in this case, every minute. By default, CloudWatch collects metrics at a 5-minute frequency, but enabling detailed monitoring increases the frequency to 1 minute. C. Publish the memory metrics using the Amazon CloudWatch agent. The Amazon CloudWatch agent allows you to collect and publish custom metrics from your EC2 instances to CloudWatch. By configuring the agent to collect memory metrics and publish them to CloudWatch, you can achieve the desired monitoring frequency of 1 minute.

A and C

C & E are correct

AC are the correct https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/mon-scripts.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cloudwatch-new.html#enable-detailed-monitoring

C,E Enabling detailed monitoring is for non-custom metric .. and won't affect custom metric collected by unified agent .. for custom metric default is 60 seconds yes , no need to specify it , but still it's the correct answer

C & E, no need for A, is Memory is a custom metric, and custom metric default duration is 1 Minute.

Why not C and D? C is no problem. D is because the question asks for "the memory utilization metrics of EC2 Linux instances must be monitored", CloudWatch Events could trigger alarm, but CloudWatch Logs cannot. So I think D but not E.

I'll go with A,C

I go with CE. The question is 'how to publish metric', focus on the cloudwatch agent setting.

Enable detailed monitoring on the instance within Amazon CloudWatch. I think it can not monitor RAM on EC2. I go with C & E

A. Enable detailed monitoring on the instance within Amazon CloudWatch C. Publish the memory metrics using the Amazon CloudWatch agent - Reason being that its a custom metric

A because it needs to be monitored every minute. C because it's a custom metric

Per my understanding, Custom metric has nothing to do with Detailed monitoring. Why ans A?

AC as for E, the The default value is 60. metrics_collection_interval – Optional. Specifies how often all metrics specified in this configuration file are to be collected. You can override this value for specific types of metrics. This value is specified in seconds. For example, specifying 10 sets metrics to be collected every 10 seconds, and setting it to 300 specifies metrics to be collected every 5 minutes. If you set this value below 60 seconds, each metric is collected as a high-resolution metric. For more information about high-resolution metrics, see High-Resolution Metrics. The default value is 60.

I'm with A & C.