Courses and Certificates Cloud-Deployment-and-Operations Syllabus Exam Questions Answers

A metric filter in Amazon CloudWatch Logs can be used to search for specific terms in log data and create metrics based on the matches. To include log events with the word "ERROR" and exclude those with the word "WARNING," the correct syntax involves using a filter pattern with a positive match for "ERROR" and a negation for "WARNING." The correct pattern is "ERROR -WARN," where the minus sign (-) indicates exclusion of log events containing "WARN." According to the WGU Cloud Deployment and Operations Study Guide (Section 4.2, CloudWatch Logs), metric filters use a pattern-based syntax where terms are included or excluded using positive matches and the negation operator (-). This ensures that only logs with "ERROR" and without "WARN" are processed into the metric.

The Wait event view in Amazon RDS Performance Insights provides information on hardware resources (e.g., CPU, I/O, memory) that may be causing bottlenecks by showing wait times for database operations. The WGU Cloud Deployment and Operations Study Guide (Section 7.2, Performance Insights) states, "The Wait event view in Performance Insights identifies resource bottlenecks (e.g., I/O wait times) by analyzing wait states, helping optimize database performance on hardware resources." Users, Hosts, and Statement views focus on different aspects and do not directly address hardware bottlenecks.

The latency routing policy in Amazon Route 53 should be used to direct customer requests to the website with the shortest round-trip time (RTT). This policy routes traffic to the AWS region with the lowest latency based on the user's location, optimizing performance. The WGU Cloud Deployment and Operations Study Guide (Section 3.1, Route 53 Routing Policies) states, "The latency-based routing policy in Route 53 measures RTT to direct users to the region with the lowest latency, improving user experience across multiple websites." Geolocation, geoproximity, and weighted policies do not prioritize RTT in this manner.

To ensure the route table with a default outbound route via an internet gateway takes effect, the administrator must create a subnet association, linking the route table to specific subnets within the VPC. This association applies the routing rules to the subnet's traffic. The WGU Cloud Deployment and Operations Study Guide (Section 3.2, VPC Routing) states, "A route table must be associated with a subnet (subnet association) to enforce routing rules, such as the default route to an internet gateway, ensuring outbound traffic follows the defined path." Propagation, tags, and edge associations do not activate the route.