DOP-C02 · Question #361
A DevOps team supports an application that runs on a large number of Amazon EC2 instances in an Auto Scaling group. The DevOps team uses AWS CloudFormation to deploy the EC2 instances. The…
The correct answer is A. Create a CloudWatch Contributor Insights rule that groups logs from the CloudWatch application D. Create a CloudWatch alarm that uses the INSIGHT_RULE_METRIC function to determine. Using a CloudWatch Contributor Insights rule to group logs based on instance ID and error frequency allows the team to pinpoint which instance is contributing to errors, providing detailed insights without additional custom logic. The INSIGHT_RULE_METRIC function in CloudWatch…
Question
A DevOps team supports an application that runs on a large number of Amazon EC2 instances in an Auto Scaling group. The DevOps team uses AWS CloudFormation to deploy the EC2 instances. The application recently experienced an issue. A single instance returned errors to a large percentage of requests. The EC2 instance responded as healthy to both Amazon EC2 and Elastic Load Balancing health checks. The DevOps team collects application logs in Amazon CloudWatch by using the embedded metric format. The DevOps team needs to receive an alert if any EC2 instance is responsible for more than half of all errors. Which combination of steps will meet these requirements with the LEAST operational overhead? (Choose two.)
Options
- ACreate a CloudWatch Contributor Insights rule that groups logs from the CloudWatch application
- BCreate a resource group in AWS Resource Groups. Use the CloudFormation stack to group the
- CCreate a metric filter for the application logs to count the occurrence of the term "Error.'' Create a
- DCreate a CloudWatch alarm that uses the INSIGHT_RULE_METRIC function to determine
- ECreate a CloudWatch subscription filter for the application logs that filters for errors and invokes
How the community answered
(33 responses)- A67% (22)
- B18% (6)
- C9% (3)
- E6% (2)
Explanation
Using a CloudWatch Contributor Insights rule to group logs based on instance ID and error frequency allows the team to pinpoint which instance is contributing to errors, providing detailed insights without additional custom logic. The INSIGHT_RULE_METRIC function in CloudWatch can be used to evaluate the Contributor Insights data to determine if any instance is responsible for more than half of all errors. This approach enables automated monitoring and alerts based on specific error patterns.
Topics
Community Discussion
No community discussion yet for this question.