WGU Cloud-Deployment-and-Operations - WGUCloud Deployment and Operations

Comprehensive and Detailed Explanation From Exact Extract:

To reduce latency in region B due to increased demand for media files stored in region A, cross-region replication (CRR) should be used. CRR replicates objects to an S3 bucket in another region (e.g., region B), allowing users to access files from a closer location, thus minimizing latency. The WGU Cloud Deployment and Operations Study Guide (Section 2.2, S3 Replication) states, "Cross-Region Replication in S3 copies objects to a destination bucket in a different region, reducing latency by enabling access to data from the nearest region, such as region B in this case." S3 Batch, S3 Versioning, and Same-Region replication do not address cross-region latency.

Comprehensive and Detailed Explanation From Exact Extract:

Recovery Point Objective (RPO) measures the maximum acceptable data loss, while Recovery Time Objective (RTO) measures the maximum acceptable downtime. The company requires an RPO of up to 3 hours (acceptable data loss) and an RTO of 1 hour (service restoration time). The correct option is RPO 4 hours, RTO 1 hour, as it meets the RPO requirement (allowing up to 3 hours of data loss is within 4 hours) and satisfies the RTO of 1 hour. The WGU Cloud Deployment and Operations Study Guide (Section 8.1, Disaster Recovery) states, "RPO defines the maximum data loss tolerance (e.g., 3 hours), and RTO defines the maximum downtime (e.g., 1 hour); a configuration of RPO 4 hours and RTO 1 hour aligns with these thresholds." Other options fail to meet both criteria simultaneously.

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.

Patch Manager in AWS Systems Manager sends compliance reports to an Amazon S3 bucket, where they are stored for auditing and analysis. This allows administrators to track patch compliance status across EC2 instances and on-premises servers. The WGU Cloud Deployment and Operations Study Guide (Section 5.2, Patch Manager) states, "Patch Manager compliance reports are delivered to an S3 bucket configured as a target, providing a centralized location for reviewing patch status and compliance data." OpsWorks, EBS, and Route 53 are not used for storing these reports.

Comprehensive and Detailed Explanation From Exact Extract:

After stopping and starting an EC2 instance, the public IP address may change (unless an Elastic IP is attached), but the security group rules remain intact. If the instance is no longer accessible via SSH, it’s likely due to an inbound rule (e.g., for port 22) not being correctly configured or applied. Adding or verifying a rule in the security group associated with the network interface (NIC) to allow SSH (port 22) from the administrator’s IP resolves this. The WGU Cloud Deployment and Operations Study Guide (Section 3.2, Security Groups) states, "Stopping and starting an EC2 instance may require verifying or adding an inbound SSH rule (port 22) in the security group if connectivity is lost due to IP or rule misconfiguration." Route table or IP changes are not the primary issue here.

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.

Elastic Load Balancing (ELB) should be used to horizontally scale Amazon EC2 instances by distributing incoming traffic across multiple instances, improving availability and fault tolerance. ELB works in conjunction with Auto Scaling groups to add or remove instances based on demand. The WGU Cloud Deployment and Operations Study Guide (Section 3.2, Elastic Load Balancing) notes, "Elastic Load Balancing distributes traffic across EC2 instances, enabling horizontal scaling as part of an Auto Scaling group to handle increased load efficiently." Elastic IPs, elastic network interfaces, and Elastic Beanstalk do not provide this scaling functionality.

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.

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.