Important WGU Cloud Deployment and Operations Exam Questions

Answer: B

Explanation:

Amazon Route 53 is the AWS solution that sends DNS queries to separate AWS compute instances by leveraging routing policies to distribute traffic across multiple resources. It acts as a scalable Domain Name System (DNS) service, directing queries to healthy instances based on configurations like latency or weighted routing. The WGU Cloud Deployment and Operations Study Guide (Section 3.1, Route 53) states, 'Route 53 uses DNS to route end-user requests to multiple AWS compute instances, supporting features like health checks and traffic distribution.' Elastic Beanstalk, CloudWatch, and EC2 Auto Scaling do not perform DNS query routing.

Answer: C

Explanation:

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.

Answer: A

Explanation:

AWS Control Tower enables a company to enforce and manage governance rules across multiple AWS accounts by setting up a landing zone with preconfigured policies for security, compliance, and operations. It simplifies multi-account management. The WGU Cloud Deployment and Operations Study Guide (Section 6.5, Control Tower) states, 'Control Tower provides a centralized solution to establish and enforce governance rules across multiple accounts, using guardrails and a landing zone to ensure compliance with organizational policies.' Security Hub, GuardDuty, and Systems Manager do not offer this multi-account governance capability.

Answer: B

Explanation:

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.

Answer: C

Explanation:

To reduce conversion delays caused by increased demand, the company should configure a CloudWatch alarm to scale the EC2 fleet based on the SQS queue length. This auto-scaling approach dynamically adjusts the number of EC2 instances to handle the workload, especially during peak evening hours and anticipated growth. The WGU Cloud Deployment and Operations Study Guide (Section 3.3, Auto Scaling and SQS) explains, 'Auto Scaling can be triggered by a CloudWatch alarm monitoring SQS queue depth, ensuring the EC2 fleet scales out to process video conversion tasks efficiently as the queue length increases.' Spot instances, dead-letter queues, and instance type upgrades do not directly address dynamic scaling needs.