(How are custom metrics grouped in CloudWatch?)
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.
(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.
(An administrator needs to deploy a NAT gateway in an existing VPC subnet. Which two tasks should this administrator perform during deployment? Choose 2 answers.)
To deploy a NAT gateway in an existing VPC subnet, the administrator must assign an elastic IP address to the NAT gateway for public internet access and configure the route table associated with the subnet to route traffic through the NAT gateway. The WGU Cloud Deployment and Operations Study Guide (Section 3.2, NAT Gateway) states, 'Deployment of a NAT gateway requires an elastic IP address for outbound internet connectivity and a route table update to direct private subnet traffic to the NAT gateway (e.g., 0.0.0.0/0 via NAT).' Private IP assignment and ACL configuration are not required steps.
(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.
Francene
11 days agoLaticia
18 days agoPaulina
25 days agoEstrella
1 month agoBette
1 month agoDyan
2 months agoVal
2 months agoVincenza
2 months agoDalene
2 months agoTiffiny
3 months agoOren
3 months agoMarget
3 months agoLeonardo
3 months agoShawnna
4 months agoRonnie
4 months agoTamar
4 months agoBette
4 months agoKatie
5 months agoDenny
5 months agoDorthy
5 months ago