(Which service should be used to horizontally scale Amazon EC2 instances?)
Answer(s): A
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. ELBworks 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.
(An endpoint is not responding to a request based on the failure threshold provided. What does Route 53 do once it considers the endpoint unhealthy?)
Answer(s): B
When Amazon Route 53 determines an endpoint is unhealthy based on a failure threshold (e.g., via health checks), it terminates the connection attempt to that endpoint and routes traffic to a healthy alternative, if available. This behavior ensures high availability using routing policies like failover or latency-based routing. The WGU Cloud Deployment and Operations Study Guide (Section 3.1, Route 53 Health Checks) states, "Route 53 stops routing traffic to an unhealthy endpoint by terminating connection attempts once the health check failure threshold is exceeded, redirecting to a healthy resource." Options A, C, and D are not direct actions taken by Route 53 in this scenario.
(An administrator plans to deploy a database to AWS that supports the following: multiple Availability Zones, a standby database instance that provides failover support, a database instance that allows only read-only connections. Which two database solutions should the administrator use? Choose 2 answers.)
Answer(s): B,C
To meet the requirements, the administrator should use an Amazon RDS Multi-AZ DB instance for multiple Availability Zones and failover support, and an Amazon Aurora DB instance with Aurora Replica for a read-only connection. The RDS Multi-AZ configuration automatically provisions a standby instance in a different AZ for failover, while Aurora Replicas provide read-only instances for scaling read traffic. The WGU Cloud Deployment and Operations Study Guide (Section 7.1, RDS and Aurora) states, "RDS Multi-AZ deploys a standby instance across AZs for failover, and Aurora Replicas are read-only instances that enhance performance by offloading read traffic from the primary instance." Options A and D are incorrect as multi-master replication and Multi-AZ clusters do not align with the read-only requirement.
(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?)
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.
(An administrator needs to implement Amazon Route 53 multivalue routing policy. The operator must ensure that Route 53 will respond to incoming requests with the maximum allowed number of records. How many records should be created?)
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.
Post your Comments and Discuss WGU Cloud-Deployment-and-Operations exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Cloud-Deployment-and-Operations content, but please register or login to continue.