Cloud-Deployment-and-Operations Exam Dumps - WGU Courses and Certificates Questions and Answers

Amazon RDS Performance Insights supports retention periods of 7 days and 1 year for storing performance data, depending on the configuration and edition. The default retention is 7 days for standard monitoring, while enabling enhanced monitoring or the Performance Insights extended retention feature allows data to be retained for up to 1 year. The WGU Cloud Deployment and Operations Study Guide (Section 7.2, Performance Insights) states, "Performance Insights offers a 7-day retention period by default, with an option to extend to 1 year for detailed historical analysis, supporting cost and performance optimization." Options A (1 day) and D (2 years) are not supported retention periods.

To receive emails when a Lambda function returns an error, the administrator should use Amazon CloudWatch to monitor the function’s logs and metrics (e.g., errors) and Amazon Simple Notification Service (SNS) to send email notifications based on CloudWatch alarms. The WGU Cloud Deployment and Operations Study Guide (Section 4.3, CloudWatch and SNS) states, "CloudWatch can detect Lambda errors via logs and trigger an alarm, which integrates with SNS to send email notifications to subscribed endpoints, ensuring timely error alerts." SQS and CloudTrail are not designed for this notification workflow.

Comprehensive and Detailed Explanation From Exact Extract:

A Billing alarm in Amazon CloudWatch should be used to monitor estimated AWS charges by setting thresholds on cost metrics and triggering notifications when exceeded. This helps manage budgets effectively. The WGU Cloud Deployment and Operations Study Guide (Section 7.4, Cost Monitoring) states, "Billing alarms in CloudWatch monitor estimated charges against a defined threshold, sending alerts via SNS to prevent cost overruns." Cognito handles user authentication, Pricing Calculator estimates costs pre-deployment, and Forecast predicts usage, none of which monitor real-time charges.

Amazon S3 (Simple Storage Service) should be used to host content to be processed for Amazon Made, as it provides scalable object storage ideal for storing and retrieving large amounts of data, such as media files or documents, for processing workflows. The WGU Cloud Deployment and Operations Study Guide (Section 2.1, Amazon S3) states, "S3 is the preferred solution for hosting content to be processed by services like Amazon Made, offering durable and highly available storage with support for lifecycle policies and integration with other AWS services." DocumentDB, DynamoDB, and EC2 are not designed for this content hosting purpose.

When Amazon Route 53 determines an endpoint is unhealthy based on a failure threshold (e.g., via health checks), it terminates the connection attempt to that endpoint and routes traffic to a healthy alternative, if available. This behavior ensures high availability using routing policies like failover or latency-based routing. The WGU Cloud Deployment and Operations Study Guide (Section 3.1, Route 53 Health Checks) states, "Route 53 stops routing traffic to an unhealthy endpoint by terminating connection attempts once the health check failure threshold is exceeded, redirecting to a healthy resource." Options A, C, and D are not direct actions taken by Route 53 in this scenario.

Comprehensive and Detailed Explanation From Exact Extract:

The VPC flow log fields indicate the following: the source IP is 192.168.20.1, the destination IP is 203.0.113.66, the source port is 2066, the destination port is 22, and the action is "ACCEPT OK," meaning the traffic was permitted. This shows outbound traffic from the internal network (192.168.20.1) to an external IP (203.0.113.66) with destination port 2066. The WGU Cloud Deployment and Operations Study Guide (Section 3.2, VPC Flow Logs) states, "In a flow log, the format includes source IP, destination IP, source port, destination port, and action; for example, 192.168.20.1 to 203.0.113.66 with source port 2066 and destination port 22 indicates permitted outbound traffic." Only option C correctly interprets this flow.

Comprehensive and Detailed Explanation From Exact Extract:

Spot Instances are the most suitable EC2 instance type for this workload pattern, offering the lowest cost for short, interruptible tasks like 3D rendering, where work can be redistributed if interrupted. This aligns with the company’s cost-plus pricing model. The WGU Cloud Deployment and Operations Study Guide (Section 7.3, EC2 Instance Types) states, "Spot Instances provide significant cost savings (up to 90% off On-Demand) for fault-tolerant, short-term workloads like rendering, where interruptions can be handled by redistributing tasks to other nodes." On-Demand, Dedicated, and Reserved Instances are more expensive and less flexible for this use case.

The `NetworkIn` metric in Amazon CloudWatch should be used to determine the number of bytes received by an EC2 instance across all network interfaces, aiding in proper instance sizing based on inbound traffic. The WGU Cloud Deployment and Operations Study Guide (Section 4.1, CloudWatch Metrics) states, "The `NetworkIn` metric measures the total number of bytes received on all network interfaces of an EC2 instance, providing critical data for sizing decisions to handle inbound traffic effectively." NetworkPacketsIn, NetworkOut, and NetworkPacketsOut measure packet counts or outbound data, which are less relevant for this purpose.

If a patch baseline is not explicitly defined in Patch Manager, it is attached to the default patch group. This default group applies a preconfigured baseline with AWS-recommended patches, ensuring basic compliance for instances without custom baselines. The WGU Cloud Deployment and Operations Study Guide (Section 5.2, Patch Manager) states, "If no custom patch baseline is defined, instances are associated with the default patch group, which uses AWS-provided baseline settings for automatic patch approval." Options A, C, and D are not valid attachments for patch baselines.

A Private Hosted Zone in Amazon Route 53 should be used to restrict DNS resolution to instances within a Virtual Private Cloud (VPC), ensuring that the zone is only accessible internally. This isolates DNS services from public internet access. The WGU Cloud Deployment and Operations Study Guide (Section 3.1, Route 53 Hosted Zones) states, "A Private Hosted Zone in Route 53 limits DNS resolution to resources within a specified VPC, preventing external access and enhancing security for internal services." Public Hosted Zones, DNS Zones, and Lightsail DNS Zones do not provide this VPC-specific restriction.