Free Cloud Deployment and Operations Practice Test Questions and Answers (2026)

The Enterprise support plan provides a technical account manager (TAM) and full use of Trusted

Advisor, offering proactive guidance and comprehensive access to all checks. This plan is designed for

large-scale, mission-critical workloads. The WGU Cloud Deployment and Operations Study Guide

(Section 6.4, AWS Support Plans) states, "The Enterprise support plan includes a dedicated Technical

Account Manager and full Trusted Advisor access, providing 24/7 support and proactive optimization

recommendations." Developer, Standard, and Business plans offer limited or no TAM support and

partial Trusted Advisor access.

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.

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.

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.

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.

To create a metric filter in the Amazon CloudWatch console, the first step is to select a log group from

which the log data will be analyzed. A log group contains log streams, and metric filters are applied

to the log data within these groups to extract metrics based on patterns. The WGU Cloud

Deployment and Operations Study Guide (Section 4.2, CloudWatch Logs) specifies that the process

begins by navigating to the CloudWatch console, selecting a log group, and then defining the filter

pattern. Actions like enabling an alarm, defining a trace, or specifying a stream are subsequent or

unrelated steps.

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.

Comprehensive and Detailed Explanation From Exact Extract:

The Mappings section in a CloudFormation template should be used to set values based on region-

specific AMI IDs. Mappings allow the template to define a lookup table that associates regions with

corresponding AMI IDs, enabling dynamic selection during stack creation across multiple regions. The

WGU Cloud Deployment and Operations Study Guide (Section 5.3, CloudFormation Mappings)

states, "The Mappings section enables region-specific configurations, such as mapping AMI IDs to

regions (e.g., 'us-east-1': 'ami-123456'), ensuring the correct AMI is used based on the deployment

region." Outputs, WaitCondition, and Resources do not provide this mapping functionality.

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.

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.

Amazon CloudWatch supports several monitoring and management solutions, including event

response and instance monitoring. Event response is facilitated through CloudWatch Events, which

can trigger actions based on predefined rules, such as invoking AWS Lambda functions. Instance

monitoring involves collecting and tracking metrics from Amazon EC2 instances, providing visibility

into performance and health. The WGU Cloud Deployment and Operations Study Guide (Section 4.1,

CloudWatch Overview) highlights that CloudWatch is designed for instance monitoring and event-

driven responses, while load balancing and threat detection are handled by services like Elastic Load

Balancing and GuardDuty, respectively.

The multivalue routing policy in Amazon Route 53 allows up to 8 healthy records to be returned in

response to DNS queries, enabling load balancing across multiple resources. To ensure the maximum

allowed number of records is utilized, the administrator should create 8 records. The WGU Cloud

Deployment and Operations Study Guide (Section 3.1, Route 53 Routing Policies) specifies,

"Multivalue answer routing supports up to 8 healthy resource record sets per response, requiring the

creation of 8 records to maximize the policy's capability." Options A, C, and D exceed or fall short of

this limit.

Comprehensive and Detailed Explanation From Exact Extract:

AWS CloudFormation uses YAML and JSON languages to define infrastructure as code (IaC)

templates, specifying resources, parameters, and configurations. These formats are human-readable

and support the creation of stacks for provisioning AWS resources. The WGU Cloud Deployment and

Operations Study Guide (Section 5.3, CloudFormation) states, "CloudFormation templates can be

written in YAML or JSON, both of which are supported for defining infrastructure resources like EC2

instances and S3 buckets." XML and C# are not supported languages for CloudFormation templates.

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.

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.