(Which AWS solution can send email based on CloudWatch alarms?)
Answer : B
Amazon CloudWatch alarms can trigger notifications when a metric breaches a defined threshold. The AWS solution designed to send emails based on these alarms is Amazon Simple Notification Service (SNS). SNS supports sending notifications via email, SMS, and other protocols when subscribed endpoints are triggered by CloudWatch alarms. The WGU Cloud Deployment and Operations Study Guide (Section 4.3, Monitoring and Alarms) states that SNS is the primary service for delivering notifications from CloudWatch, allowing users to configure email subscriptions for alarm states. Other options like SQS, Amplify, and Kinesis are not designed for this purpose.
(A company uses SQS and EC2 to convert videos uploaded by users. In the evenings, videos take several hours to convert when they normally take minutes. The user base is expected to grow a hundredfold in the next 12 months. Which solution should be used to reduce the conversion delays?)
Answer : C
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.
(What should be used to monitor estimated AWS charges?)
Answer : B
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.
(A company configures the CloudFront caching TTL to the following settings: Min: 0, Max: 172800. An administrator updates the Cache-Control setting to 432000. However, objects are only cached for 48 hours. What is required to ensure objects are cached for up to 120 hours?)
Answer : A
Comprehensive and Detailed Explanation From Exact Extract:
In Amazon CloudFront, the caching TTL is controlled by the minimum and maximum TTL settings, with the maximum TTL (in seconds) capping the cache duration. The current Max TTL is 172800 seconds (48 hours), and the Cache-Control setting of 432000 seconds (120 hours) is ignored because it exceeds the Max TTL. To cache objects for up to 120 hours, the Max setting must be configured to 432000 seconds. The WGU Cloud Deployment and Operations Study Guide (Section 4.4, CloudFront Caching) states, 'The maximum TTL in CloudFront settings (e.g., 172800 seconds) overrides any higher Cache-Control value; to allow 120 hours (432000 seconds), the Max TTL must be set accordingly.' Adjusting Min, expiration, or Cache-Control alone does not resolve this.
(What should be configured in Systems Manager to set the error threshold for automation documents?)
Answer : C
In AWS Systems Manager, the error threshold for automation documents is configured using rate control. Rate control allows administrators to define the maximum number of errors or concurrent executions that can occur before an automation task is throttled or stopped, ensuring system stability. The WGU Cloud Deployment and Operations Study Guide (Section 5.1, Systems Manager Automation) explicitly states, 'Rate control settings in Automation documents can be used to specify the maximum number of errors allowed during execution, helping to manage error thresholds effectively.' Resource groups, session preferences, and maintenance windows do not directly address error thresholds.
(Which performance optimization method must be used when uploading files larger than 5 GB to S3?)
Answer : A
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.
(An administrator sees the following VPC flow log: 2 123456739010 eni-123bfecad12529 192.168.20.1 203.0.113.66 2066 22 20 7782 1645859356 1645859536 ACCEPT OK. What does the log indicate about the traffic flow?)
Answer : C
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.