SAP-C02 · Question #34
A public retail web application uses an Application Load Balancer (ALB) in front of Amazon EC2 instances running across multiple Availability Zones (AZs) in a Region backed by an Amazon RDS MySQL…
The correct answer is B. Configure the target group health check to point at a simple HTML page instead of a product E. Configure an Amazon ElastiCache cluster and place it between the web application and RDS. A: Since the issue lies with query response (read) it is cheaper and faster to use ElastiCache which is in memory. B\C: Unlike a Classic Load Balancer or a Network Load Balancer, an Application Load Balancer can't have transport layer (layer 4) TCP or SSL/TLS listeners. It…
Question
A public retail web application uses an Application Load Balancer (ALB) in front of Amazon EC2 instances running across multiple Availability Zones (AZs) in a Region backed by an Amazon RDS MySQL Multi-AZ deployment. Target group health checks are configured to use http and pointed at the product catalogue page. Auto Scaling is configured to maintain the web fleet size based on the ALB health check. Recently, the application experienced an outage. Auto Scaling continuously replaced the instances during the outage. A subsequent investigation determined that the web server metrics were within the normal range, but the database tier was experiencing high load, resulting in severely elevated query response times. Which of the following changes together would remediate these issues while improving monitoring capabilities for the availability and functionality of the entire application stack for future growth? (Choose two.)
Options
- AConfigure read replicas for Amazon RDS MySQL and use the single reader endpoint in the web
- BConfigure the target group health check to point at a simple HTML page instead of a product
- CConfigure the target group health check to use a TCP check of the Amazon EC2 web server and
- DConfigure an Amazon CloudWatch alarm for Amazon RDS with an action to recover a high-load,
- EConfigure an Amazon ElastiCache cluster and place it between the web application and RDS
How the community answered
(53 responses)- A11% (6)
- B79% (42)
- C4% (2)
- D6% (3)
Explanation
A: Since the issue lies with query response (read) it is cheaper and faster to use ElastiCache which is in memory. B\C: Unlike a Classic Load Balancer or a Network Load Balancer, an Application Load Balancer can't have transport layer (layer 4) TCP or SSL/TLS listeners. It supports only http and httpS listeners. Additionally, it can't use backend authentication to authenticate https connections between the load balancer and backend instances. D: Should not recover the RDS instance.
Community Discussion
No community discussion yet for this question.