Q45 — AWS DOP-C02 Ch.3

Question 45 of 100 | ← Chapter 3

A company uses lift-and-shift strategies to migrate workloads from on-premises to AWS. It has an Amazon EC2 Auto Scaling group. Each EC2 instance runs a web application, a database, and a Redis cache. Users are experiencing significant latency issues with the web application. Requests to the web application are bottlenecked on a single EC2 instance under variable load. The company wants to decouple application components to improve scalability and performance.

• A. Create a Network Load Balancer and an Auto Scaling group for the web application. Migrate the database to an Amazon Aurora Serverless database. Create an Application Load Balancer and an Auto Scaling group for the Redis cache.
• B. Create an Application Load Balancer and an Auto Scaling group for the web application. Migrate the database to an Amazon Aurora database with Multi-AZ deployment. Create a Network Load Balancer and an Auto Scaling group for the Redis cache in a single Availability Zone.
• C. Create a Network Load Balancer and an Auto Scaling group for the web application. Migrate the database to an Amazon Aurora Serverless database. Create an Amazon ElastiCache cluster for caching. Create a target group with DNS target type containing the ElastiCache cluster hostname.
• D. Create an Application Load Balancer and an Auto Scaling group for the web application. Migrate the database to an Amazon Aurora database with Multi-AZ deployment. Create an Amazon ElastiCache cluster for caching. ✓

Correct Answer: D. Create an Application Load Balancer and an Auto Scaling group for the web application. Migrate the database to an Amazon Aurora database with Multi-AZ deployment. Create an Amazon ElastiCache cluster for caching.

Explanation

In AWS architecture design, decoupling application components improves availability and performance. Per the AWS Well-Architected Framework, layered architectures should scale components independently. An Application Load Balancer (ALB) is appropriate for HTTP-layer routing, and an Auto Scaling group dynamically adjusts web-tier capacity. Multi-AZ deployed Amazon Aurora provides high database availability, while ElastiCache serves as a managed caching service replacing in-instance Redis—eliminating single points of failure and enabling independent scaling. A Network Load Balancer (NLB) suits non-HTTP scenarios; option D avoids redundant components and aligns with layered best practices.