(Which two retention periods are supported by Performance Insights? Choose 2 answers.)
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.
(An administrator successfully accesses an EC2 instance via SSH from a local computer then stops it and starts it. Following the restart, the EC2 instance is no longer accessible. Which solution should be used to resolve the issue?)
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.
(Which Performance Insights view provides information on the hardware resource that may be causing a bottleneck?)
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.
(What is used to change stacks across multiple accounts and Regions in a single operation?)
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.
(A company builds an application that renders 3D movies for its users. The application does this by spawning a fleet of instances that each take a slice of the workload and then render a few hundred frames in around 30 minutes. If processing on a node is interrupted, the work can be moved to other running nodes. The cost to users is based on the underlying AWS cost plus a margin. Which EC2 instance type is most suitable to run workload pattern at the lowest cost?)
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.
Dyan
8 days agoVal
15 days agoVincenza
22 days agoDalene
30 days agoTiffiny
1 month agoOren
1 month agoMarget
2 months agoLeonardo
2 months agoShawnna
2 months agoRonnie
2 months agoTamar
3 months agoBette
3 months agoKatie
3 months agoDenny
3 months agoDorthy
4 months ago