[2025] Practice with these Cloud-Deployment-and-Operations dumps Certification Sample Questions
Get Instant Access of 100% REAL Cloud-Deployment-and-Operations DUMP Pass Your Exam Easily
NEW QUESTION # 34
(A company uses KMS for key management. The company has a requirement to ensure that cryptographic material is not used longer than a year. Which solution should be used to meet this requirement with the least amount of effort?)
- A. Enable automatic key rotation in KMS
- B. Develop a custom key encryption protocol for KMS
- C. Move keys from KMS to CloudHSM
- D. Write a Lambda function to replace keys in KMS
Answer: A
Explanation:
Enabling automatic key rotation in AWS Key Management Service (KMS) is the least effort solution to ensure cryptographic material is not used longer than a year. KMS automatically rotates the cryptographic material of symmetric customer master keys (CMKs) every 365 days, meeting the requirement without manual intervention. The WGU Cloud Deployment and Operations Study Guide (Section 6.3, KMS) states,
"Automatic key rotation in KMS rotates the backing key material every year for symmetric CMKs, providing a low-effort way to comply with key usage limits." Moving to CloudHSM, custom protocols, or Lambda functions require more effort and complexity.
NEW QUESTION # 35
(Which AWS service is used to provide remote workers with secure access to AWS resources?)
- A. Client VPN
- B. Transit Gateway
- C. NAT instance
- D. Network Firewall
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
AWS Client VPN is used to provide remote workers with secure access to AWS resources by establishing a VPN connection to the VPC, ensuring encrypted access to private networks. The WGU Cloud Deployment and Operations Study Guide (Section 3.2, Client VPN) states, "Client VPN enables secure remote access to AWS resources within a VPC, using mutual authentication and encryption to protect data for remote workers." Transit Gateway manages inter-VPC routing, Network Firewall filters traffic, and NAT instances handle outbound internet access, none of which are designed for remote worker access.
NEW QUESTION # 36
(A company is using CloudWatch on its EC2 instances. The company needs to determine the number of bytes received by an instance on all network interfaces for proper sizing of the instance. Which metric should the company use?)
- A. NetworkIn
- B. NetworkPacketsIn
- C. NetworkPacketsOut
- D. NetworkOut
Answer: A
Explanation:
The `NetworkIn` metric in Amazon CloudWatch should be used to determine the number of bytes received by an EC2 instance across all network interfaces, aiding in proper instance sizing based on inbound traffic. The WGU Cloud Deployment and Operations Study Guide (Section 4.1, CloudWatch Metrics) states, "The
`NetworkIn` metric measures the total number of bytes received on all network interfaces of an EC2 instance, providing critical data for sizing decisions to handle inbound traffic effectively." NetworkPacketsIn, NetworkOut, and NetworkPacketsOut measure packet counts or outbound data, which are less relevant for this purpose.
NEW QUESTION # 37
(Which CloudWatch metric filter includes log events with the word ERROR but excludes log events with the word WARNING?)
- A. "ERROR" WARN
- B. ERROR WARN
- C. ERROR -WARN
- D. ?ERROR ?WARN
Answer: C
Explanation:
A metric filter in Amazon CloudWatch Logs can be used to search for specific terms in log data and create metrics based on the matches. To include log events with the word "ERROR" and exclude those with the word "WARNING," the correct syntax involves using a filter pattern with a positive match for "ERROR" and a negation for "WARNING." The correct pattern is "ERROR -WARN," where the minus sign (-) indicates exclusion of log events containing "WARN." According to the WGU Cloud Deployment and Operations Study Guide (Section 4.2, CloudWatch Logs), metric filters use a pattern-based syntax where terms are included or excluded using positive matches and the negation operator (-). This ensures that only logs with
"ERROR" and without "WARN" are processed into the metric.
NEW QUESTION # 38
(How are custom metrics grouped in CloudWatch?)
- A. Namespace
- B. Value
- C. Date
- D. Service
Answer: A
Explanation:
In Amazon CloudWatch, custom metrics are organized and grouped using namespaces. A namespace is a container for CloudWatch metrics that allows you to isolate and categorize metrics from different applications or services. According to the WGU Cloud Deployment and Operations Study Guide (Section 4.1, CloudWatch Metrics), each custom metric must be assigned to a namespace, which acts as a unique identifier to prevent naming collisions and facilitate metric management. Options like Service, Date, and Value are not used for grouping metrics in this context.
NEW QUESTION # 39
(An administrator is unable to make an AMI public. What is the cause?)
- A. Paravirtual virtualization is used
- B. Legacy BIOS boot mode is used
- C. Boot volume is encrypted
- D. Bookmark is absent
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The inability to make an AMI public is caused by an encrypted boot volume. AWS does not allow AMIs with encrypted EBS snapshots to be shared publicly due to security constraints; sharing is limited to specific AWS accounts. The WGU Cloud Deployment and Operations Study Guide (Section 6.3, AMI Management) states,
"An AMI cannot be made public if its boot volume is encrypted; encryption restricts sharing to authorized accounts only, requiring decryption keys to be managed separately." Legacy BIOS, paravirtual virtualization, and the absence of a bookmark do not impact AMI sharing.
NEW QUESTION # 40
(A company is using Route 53 for Domain Name System (DNS) hosting. The company requires a zone that should only be accessible from instances in a Virtual Private Cloud (VPC). Which type of hosted zone should be used?)
- A. DNS Zone
- B. Private Zone
- C. Public Hosted Zone
- D. Lightsail DNS Zone
Answer: B
Explanation:
A Private Hosted Zone in Amazon Route 53 should be used to restrict DNS resolution to instances within a Virtual Private Cloud (VPC), ensuring that the zone is only accessible internally. This isolates DNS services from public internet access. The WGU Cloud Deployment and Operations Study Guide (Section 3.1, Route 53 Hosted Zones) states, "A Private Hosted Zone in Route 53 limits DNS resolution to resources within a specified VPC, preventing external access and enhancing security for internal services." Public Hosted Zones, DNS Zones, and Lightsail DNS Zones do not provide this VPC-specific restriction.
NEW QUESTION # 41
(An administrator needs to troubleshoot a connectivity issue from on-premises computers to public IP addresses assigned to EC2 instances. The administrator suspects the cause to be a network security group.
Which VPC feature should be used to troubleshoot the issue?)
- A. PrivateLink
- B. Reachability Analyzer
- C. Traffic Mirroring
- D. Flow Logs
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The Reachability Analyzer in AWS VPC should be used to troubleshoot connectivity issues from on-premises computers to EC2 instances, especially when a network security group (NSG) is suspected. It analyzes the network path and identifies blocked traffic due to NSG rules or route tables. The WGU Cloud Deployment and Operations Study Guide (Section 3.2, VPC Troubleshooting) states, "Reachability Analyzer helps diagnose connectivity issues by simulating traffic paths, identifying if an NSG rule (e.g., blocked port) or route table is causing the problem from on-premises to EC2 public IPs." Flow Logs provide data but not analysis, PrivateLink is for private connections, and Traffic Mirroring is for monitoring.
NEW QUESTION # 42
(Which service should be used to horizontally scale Amazon EC2 instances?)
- A. Elastic Load Balancing
- B. Elastic network interface
- C. Elastic IPs
- D. Elastic Beanstalk
Answer: A
Explanation:
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.
NEW QUESTION # 43
(A company has the following disaster recovery requirements: The loss of up to three hours of data is acceptable. Services must be restored within one hour of failure. Which recovery characteristics will allow the company to meet the requirements?)
- A. RPO 1 hour, RTO 2 hours
- B. RPO 2 hours, RTO 1 hour
- C. RPO 4 hours, RTO 1 hour
- D. RPO 1 hour, RTO 4 hours
Answer: C
Explanation:
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.
NEW QUESTION # 44
(Which Performance Insights view provides information on the hardware resource that may be causing a bottleneck?)
- A. Wait event
- B. Hosts
- C. Statement
- D. Users
Answer: A
Explanation:
The Wait event view in Amazon RDS Performance Insights provides information on hardware resources (e.g., CPU, I/O, memory) that may be causing bottlenecks by showing wait times for database operations. The WGU Cloud Deployment and Operations Study Guide (Section 7.2, Performance Insights) states, "The Wait event view in Performance Insights identifies resource bottlenecks (e.g., I/O wait times) by analyzing wait states, helping optimize database performance on hardware resources." Users, Hosts, and Statement views focus on different aspects and do not directly address hardware bottlenecks.
NEW QUESTION # 45
(An administrator deploys an EC2 instance with the public IP address 54.18.127.233 into a newly created VPC in us-west-2. The EC2 instance must be accessible via ec2-public-54.18.127.233.us-west-2.compute.
amazonaws.com from the internet. Which solution should be used?)
- A. Assign a resource-based name to the EC2 instance
- B. Assign a resource tag to the EC2 instance
- C. Set the VPC attribute enableDnsSupport to false
- D. Set the VPC attribute enableDnsHostnames to true
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
To make the EC2 instance accessible via a public DNS hostname like ec2-public-54.18.127.233.us-west-2.
compute.amazonaws.com, the administrator must set the VPC attribute enableDnsHostnames to true. This enables the automatic assignment of public DNS hostnames to instances with public IP addresses in the VPC.
The WGU Cloud Deployment and Operations Study Guide (Section 3.2, VPC Configuration) states, "Setting enableDnsHostnames to true in the VPC configuration ensures that EC2 instances with public IPs receive a public DNS hostname (e.g., ec2-public-<ip>.<region>.compute.amazonaws.com), facilitating internet accessibility." Resource tags, disabling DNS support, and resource-based names do not enable this functionality.</region></ip>
NEW QUESTION # 46
(What should be configured in Systems Manager to set the error threshold for automation documents?)
- A. Maintenance windows
- B. Rate control
- C. Session preferences
- D. Resource group
Answer: B
Explanation:
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.
NEW QUESTION # 47
(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?)
- A. Use spot instances instead of on-demand
- B. Configure an alarm to scale the fleet based on queue length
- C. Switch from t2.medium to t2.xlarge instance type
- D. Implement a dead-letter queue
Answer: B
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.
NEW QUESTION # 48
(What is used to change stacks across multiple accounts and Regions in a single operation?)
- A. Nested stacks
- B. Stack policies
- C. StackSets
- D. StackInstance
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
StackSets are used to change stacks across multiple AWS accounts and regions in a single operation, enabling centralized management of infrastructure deployments. StackSets allow administrators to create, update, or delete stacks consistently across specified accounts and regions. The WGU Cloud Deployment and Operations Study Guide (Section 5.4, StackSets) states, "StackSets provide the capability to manage and update stacks across multiple accounts and regions with a single operation, streamlining multi-region deployments." StackInstance, nested stacks, and stack policies do not support this multi-account, multi-region functionality.
NEW QUESTION # 49
(Which AWS monitoring feature is used to process events using AWS Lambda?)
- A. Metrics
- B. Rules
- C. Targets
- D. Logs
Answer: B
Explanation:
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.
NEW QUESTION # 50
(An AWS SysOps administrator needs to configure Amazon Route 53 to load balance customer requests across multiple identically configured websites. The load balancing method must ensure that the customer requests are directed to the website that offers the shortest round-trip time. Which routing policy should be used?)
- A. Latency
- B. Geoproximity
- C. Weighted
- D. Geolocation
Answer: A
Explanation:
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.
NEW QUESTION # 51
(An administrator needs to set up self-managed permissions for AWS CloudFormation StackSet operations.
Which two roles should be created in the administrator account and in the target accounts? Choose 2 answers.)
- A. In each target account, create a service role named AWSCloudFormationStackSetExecutionRole that trusts the administrator account.
- B. In each target account, create a service role named AWSCloudFormationStackSetAdministrationRole that trusts the administrator account.
- C. In the administrator account, create an IAM role named AWSCloudFormationStackSetExecutionRole.
- D. In the administrator account, create an IAM role named
AWSCloudFormationStackSetAdministrationRole.
Answer: A,D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
To set up self-managed permissions for CloudFormation StackSet operations, two roles are required: in the administrator account, create an IAM role named AWSCloudFormationStackSetAdministrationRole to manage StackSet operations, and in each target account, create a service role named AWSCloudFormationStackSetExecutionRole that trusts the administrator account to execute the stacks. The WGU Cloud Deployment and Operations Study Guide (Section 5.4, StackSets) states, "For self-managed permissions, the administrator account requires the AWSCloudFormationStackSetAdministrationRole, while each target account needs the AWSCloudFormationStackSetExecutionRole with a trust relationship to the administrator account for stack deployment." Roles B and D are incorrectly named or misplaced.
NEW QUESTION # 52
(A company manages a containerized application by manually deploying AWS compute instances. Which solution should be used to optimize the cost of the application?)
- A. RDS
- B. EFS
- C. Fargate
- D. Aurora
Answer: C
Explanation:
AWS Fargate should be used to optimize the cost of a containerized application by eliminating the need for manual instance management, as it provides serverless container orchestration that automatically scales and charges only for resource usage. The WGU Cloud Deployment and Operations Study Guide (Section 7.5, Fargate) states, "Fargate optimizes costs for containerized applications by removing the overhead of managing EC2 instances, scaling automatically, and billing based on vCPU and memory usage, reducing manual deployment expenses." Aurora, RDS, and EFS are database or storage solutions not designed for container cost optimization.
NEW QUESTION # 53
(A company is using Route 53 for Domain Name System (DNS) hosting. The company requires a zone that should only be accessible from instances in a Virtual Private Cloud (VPC). Which type of hosted zone should be used?)
- A. DNS Zone
- B. Private Zone
- C. Public Hosted Zone
- D. Lightsail DNS Zone
Answer: B
Explanation:
A Private Hosted Zone in Amazon Route 53 should be used to restrict DNS resolution to instances within a Virtual Private Cloud (VPC), ensuring that the zone is only accessible internally. This isolates DNS services from public internet access. The WGU Cloud Deployment and Operations Study Guide (Section 3.1, Route 53 Hosted Zones) states, "A Private Hosted Zone in Route 53 limits DNS resolution to resources within a specified VPC, preventing external access and enhancing security for internal services." Public Hosted Zones, DNS Zones, and Lightsail DNS Zones do not provide this VPC-specific restriction.
NEW QUESTION # 54
(Which type of support plan provides a technical account manager and full use of Trusted Advisor?)
- A. Developer
- B. Enterprise
- C. Standard
- D. Business
Answer: B
Explanation:
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.
NEW QUESTION # 55
(Which AWS monitoring feature is used to process events using AWS Lambda?)
- A. Metrics
- B. Rules
- C. Targets
- D. Logs
Answer: B
Explanation:
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.
NEW QUESTION # 56
(What needs to be configured in Systems Manager to run Automation documents on schedule?)
- A. Resource groups
- B. Rate control
- C. Maintenance window
- D. Session preferences
Answer: C
Explanation:
To run Automation documents on a schedule in AWS Systems Manager, a maintenance window must be configured. Maintenance windows define the time periods during which automated tasks, including the execution of Automation documents, can run. The WGU Cloud Deployment and Operations Study Guide (Section 5.2, Maintenance Windows) explains that maintenance windows are used to schedule and control the execution of Systems Manager tasks, ensuring they align with operational windows. Rate control, session preferences, and resource groups are not used for scheduling automation tasks.
NEW QUESTION # 57
(Which two retention periods are supported by Performance Insights? Choose 2 answers.)
- A. 7 days
- B. 1 day
- C. 2 years
- D. 1 year
Answer: A,D
Explanation:
Amazon RDS Performance Insights supports retention periods of 7 days and 1 year for storing performance data, depending on the configuration and edition. The default retention is 7 days for standard monitoring, while enabling enhanced monitoring or the Performance Insights extended retention feature allows data to be retained for up to 1 year. The WGU Cloud Deployment and Operations Study Guide (Section 7.2, Performance Insights) states, "Performance Insights offers a 7-day retention period by default, with an option to extend to 1 year for detailed historical analysis, supporting cost and performance optimization." Options A (1 day) and D (2 years) are not supported retention periods.
NEW QUESTION # 58
......
Free Exam Files Downloaded Instantly: https://www.examboosts.com/WGU/Cloud-Deployment-and-Operations-practice-exam-dumps.html
Cloud-Deployment-and-Operations Free Exam Questions with Quality Guaranteed: https://drive.google.com/open?id=1zBW3LQ5whKvO9097gTgw5s2kkwXdMfPZ