Cloud-Deployment-and-Operations Exam Questions & Answers

The AWS monitoring feature used to process events with AWS Lambda is CloudWatch Events, specifically through the use of rules. Rules define the events to monitor (e.g., based on event patterns) and specify targets like AWS Lambda functions to process those events. The WGU Cloud Deployment and Operations Study Guide (Section 4.3, CloudWatch Events) explains that rules are the core component for event-driven architectures, enabling automation by linking events to Lambda for processing. Metrics, targets, and logs are related but not the primary feature for this function.

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.

Multipart uploads must be used when uploading files larger than 5 GB to Amazon S3, as this method splits the file into smaller parts for parallel upload, improving reliability and performance. The WGU Cloud Deployment and Operations Study Guide (Section 2.1, S3 Uploads) states, 'For files exceeding 5 GB, multipart upload is required in S3, allowing the file to be divided into parts (minimum 5 MB each) for concurrent uploads, ensuring efficient and resumable transfers.' Glacier Select, Transfer Acceleration, and Intelligent-Tiering are not designed for this upload optimization.

To deploy a NAT gateway in an existing VPC subnet, the administrator must assign an elastic IP address to the NAT gateway for public internet access and configure the route table associated with the subnet to route traffic through the NAT gateway. The WGU Cloud Deployment and Operations Study Guide (Section 3.2, NAT Gateway) states, 'Deployment of a NAT gateway requires an elastic IP address for outbound internet connectivity and a route table update to direct private subnet traffic to the NAT gateway (e.g., 0.0.0.0/0 via NAT).' Private IP assignment and ACL configuration are not required steps.

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.