Topic 1 Question 262
A SysOps administrator needs to create alerts that are based on the read and write metrics of Amazon Elastic Block Store (Amazon EBS) volumes that are attached to an Amazon EC2 instance. The SysOps administrator creates and enables Amazon CloudWatch alarms for the DiskReadBytes metric and the DiskWriteBytes metric.
A custom monitoring tool that is installed on the EC2 instance with the same alarm configuration indicates that the volume metrics have exceeded the threshold. However, the CloudWatch alarms were not in ALARM state.
Which action will ensure that the CloudWatch alarms function correctly?
Install and configure the CloudWatch agent on the EC2 instance to capture the desired metrics.
Install and configure AWS Systems Manager Agent on the EC2 instance to capture the desired metrics.
Reconfigure the CloudWatch alarms to use the VolumeReadBytes metric and the VolumeWriteBytes metric for the EBS volumes.
Reconfigure the CloudWatch alarms to use the VolumeReadBytes metric and the VolumeWriteBytes metric for the EC2 instance.
ユーザの投票
コメント(4)
- 正解だと思う選択肢: A
A.
The question states "a custom monitoring tool has been installed", therefore the Cloudwatch agent has not been installed and is required to send the metrics.
👍 1Domdom1202023/03/07 - 正解だと思う選択肢: C
For starters, I believe it's a very tricky question and unclear.
Although A looks plausible, I believe the right answer is C. In the question it says
"A SysOps administrator needs to create alerts that are based on the read and write metrics of Amazon Elastic Block Store (Amazon EBS) volumes that are attached to an Amazon EC2 instance."
The key take away here is "EBS volumes". DiskReadBytes, DiskWriteBytes refer to instance store volumes (see, https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html). Instance store volumes are physically attached disks and not EBS volumes (which are network attached drives).
Thus, the metrics we monitor look wrong to me. Also, looks like that the metrics we want to monitor are VolumeReadBytes & VolumeWriteBytes. These metrics are included in the AWS/EBS namespace (so it's definitely not D) by default and the CloudWatch agent is not required to monitor them.
Finally, SSM agent is irrelevant in this case.
👍 1csG132023/03/09 - 正解だと思う選択肢: C
The CloudWatch alarms are based on the DiskReadBytes metric and the DiskWriteBytes metric, which are not valid metrics for EBS volumes. The correct metrics for monitoring EBS volumes are the VolumeReadBytes metric and the VolumeWriteBytes metric. Therefore, option C is the correct solution.
Option A is incorrect because installing and configuring the CloudWatch agent will not fix the issue. The CloudWatch agent only captures EC2 instance metrics, not EBS volume metrics.
👍 1Vivec2023/03/09
シャッフルモード