Pass the WGU Courses and Certificates Cloud-Deployment-and-Operations Questions and answers with ExamsMirror

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 `GetSessionToken` API call is needed to perform MFA before accessing a resource, as it generates temporary security credentials for an IAM user after MFA validation. This ensures secure access to AWS resources. The WGU Cloud Deployment and Operations Study Guide (Section 6.2, IAM and MFA) states, "The `GetSessionToken` API is used with MFA to obtain temporary credentials, requiring a valid MFA code to authenticate the user before resource access is granted." GetCallerIdentity, GetFederationToken, and DecodeAuthorizationMessage serve different purposes and do not handle MFA authentication.

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.

Amazon EventBridge should be used to configure email notifications for a trigger by Amazon Made, as it can route events to targets like Amazon SNS (Simple Notification Service) for email delivery. EventBridge integrates with AWS services to handle event-driven notifications. The WGU Cloud Deployment and Operations Study Guide (Section 4.3, EventBridge) states, "EventBridge can be configured to send events from Amazon Made to SNS, enabling email notifications by subscribing an email endpoint to the SNS topic." SQS, EKS, and CodeDeploy do not support this notification configuration.

The latency routing policy in Amazon Route 53 should be used to direct customer requests to the website with the shortest round-trip time (RTT). This policy routes traffic to the AWS region with the lowest latency based on the user's location, optimizing performance. The WGU Cloud Deployment and Operations Study Guide (Section 3.1, Route 53 Routing Policies) states, "The latency-based routing policy in Route 53 measures RTT to direct users to the region with the lowest latency, improving user experience across multiple websites." Geolocation, geoproximity, and weighted policies do not prioritize RTT in this manner.

Amazon Inspector can publish its findings when detecting anomalies to Amazon SNS for real-time notifications and to CloudWatch for metric and event logging, enabling monitoring and response. The WGU Cloud Deployment and Operations Study Guide (Section 6.2, Amazon Inspector) states, "Inspector findings are published to SNS for immediate alerts and to CloudWatch for detailed logging, allowing integration with other AWS services for anomaly response." CloudTrail logs API calls, and SQS is a messaging queue, neither of which are primary destinations for Inspector findings.

The weighted routing policy in Amazon Route 53 allows the company to distribute traffic with specific percentages, such as 75% to AWS and 25% to the on-premises infrastructure, by assigning weights to each resource record. This enables load balancing across hybrid environments. The WGU Cloud Deployment and Operations Study Guide (Section 3.1, Route 53 Routing Policies) states, "Weighted routing policy assigns weights to resource record sets (e.g., 75 for AWS, 25 for on-premises), controlling the percentage of traffic directed to each endpoint." Geolocation, failover, and simple policies do not support percentage-based traffic splitting.

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 meet the requirements of restricting EC2 instances to Free Tier-eligible types and automatically terminating unapproved instances, AWS Systems Manager and AWS Config should be used. Systems Manager can enforce instance compliance through automation documents that monitor and terminate non-compliant instances. AWS Config provides continuous monitoring and evaluation of resource configurations against defined rules, such as those limiting instance types to Free Tier-eligible options (e.g., t2.micro or t3.micro). The WGU Cloud Deployment and Operations Study Guide (Section 6.1, AWS Config and Systems Manager) notes, "AWS Config can be configured with a rule to detect non-Free Tier EC2 instances, while Systems Manager Automation can execute a termination script based on Config findings." OpsWorks and Launch Wizard are not designed for this specific compliance and automation use case.

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.