(A cloud engineer needs to notify the response team whenever a high-security web server responds with a 403 Forbidden error. Which two steps can enable this functionality? Choose 2 answers.)
Correct Answer: A, C
Explanation:
To notify a response team when a high-security web server returns a 403 Forbidden error, two key steps are required. First, define a metric filter for Apache logs in CloudWatch to detect the 403 error code within the log data. This involves setting up a filter pattern to match "403" in the Apache access logs. Second, create an alarm for the metric filter and configure it to deliver alerts using Amazon SNS, which supports email or other notifications to the response team. The WGU Cloud Deployment and Operations Study Guide (Section 4.2, CloudWatch Logs and Alarms) confirms that metric filters and SNS-integrated alarms are the standard approach for monitoring and alerting on log-based events. Options B and D are incorrect as they involve unnecessary or unsupported configurations (e.g., binding Lambda to Apache or using SQS for alarms).
Question 2
(Which action must be used to create a metric filter in the Amazon CloudWatch console?)
Correct Answer: C
Explanation:
To create a metric filter in the Amazon CloudWatch console, the first step is to select a log group from which the log data will be analyzed. A log group contains log streams, and metric filters are applied to the log data within these groups to extract metrics based on patterns. The WGU Cloud Deployment and Operations Study Guide (Section 4.2, CloudWatch Logs) specifies that the process begins by navigating to the CloudWatch console, selecting a log group, and then defining the filter pattern. Actions like enabling an alarm, defining a trace, or specifying a stream are subsequent or unrelated steps.
Question 3
(How are custom metrics grouped in CloudWatch?)
Correct Answer: A
Explanation:
In Amazon CloudWatch, custom metrics are organized and grouped using namespaces. A namespace is a container for CloudWatch metrics that allows you to isolate and categorize metrics from different applications or services. According to the WGU Cloud Deployment and Operations Study Guide (Section 4.1, CloudWatch Metrics), each custom metric must be assigned to a namespace, which acts as a unique identifier to prevent naming collisions and facilitate metric management. Options like Service, Date, and Value are not used for grouping metrics in this context
Demo Practice Mode
You are viewing only the questions marked as Demo.