Q93 — AWS SAA-C03 Ch.10

Question 93 of 100 | ← Chapter 10

Q693. A company has users all around the world accessing its HTTP-based application deployed on Amazon EC2 instances in multiple AWS Regions.The company wants to improve the availability and performance of the application. The company also wants to protect the application against common web exploits that may affect availability, compromise security, or consume excessive resources. Static IP addresses are required. What should a solutions architect recommend to accomplish this?

Correct Answer: B. Put the EC2 instances behind Application Load Balancers (ALBs) in each Region. Deploy AWS WAF on the ALBs. Create an accelerator using AWS Global Accelerator and register the ALBs as endpoints

Explanation

To improve the availability, performance, and security of an HTTP-based application deployed on Amazon EC2 instances in multiple AWS Regions, and to fulfill the requirement of static IP addresses, the recommended solution is:B. Put the EC2 instances behind Application Load Balancers (ALBs) in each Region. Deploy AWS WAF on the ALBs. Create an accelerator using AWS Global Accelerator and register the ALBs as endpoints. Option B provides a comprehensive solution that addresses the requirements of availability, performance, security, and static IP addresses:- Put the EC2 instances behind Application Load Balancers (ALBs) in each Region: ALBs distribute incoming traffic across multiple EC2 instances, improving availability and scaling capabilities. They can also perform health checks on the instances to ensure traffic is only routed to healthy instances.- Deploy AWS WAF on the ALBs: AWS WAF (Web Application Firewall) protects the application against common web exploits and attacks. By deploying AWS WAF on the ALBs, you can mitigate security threats and apply custom rules to block malicious traffic.- Create an accelerator using AWS Global Accelerator and register the ALBs as endpoints: AWS Global Accelerator is a service that improves the availability and performance of your applications by routing traffic through the global AWS network. By creating an accelerator and registering the ALBs as endpoints, you can take advantage of the global infrastructure to optimize the delivery of traffic to your application.Option A, putting the EC2 instances behind Network Load Balancers (NLBs) and deploying AWS WAF on the NLBs, does not provide the caching and content delivery capabilities needed to improve performance globally. Additionally, it does not include the use of AWS Global Accelerator.Option C, putting the EC2 instances behind NLBs, deploying AWS WAF on the NLBs, and creating a CloudFront distribution with an origin that uses Amazon Route 53 latency-based routing to route requests to the NLBs, is not the optimal solution. NLBs are primarily used for TCP/UDP traffic, while ALBs provide more advanced features for HTTP-based applications. Moreover, this option does not leverage AWS Global Accelerator.Option D, putting the EC2 instances behind ALBs and creating a CloudFront distribution with an origin that uses Amazon Route 53 latency-based routing, without deploying AWS WAF or using AWS Global Accelerator, does not fully address the requirement of protecting the application against common web exploits and optimizing global traffic routing.Therefore, the best solution to accomplish the requirements is B: Put the EC2 instances behind Application Load Balancers (ALBs) in each Region. Deploy AWS WAF on the ALBs. Create an accelerator using AWS Global Accelerator and register the ALBs as endpoints. This solution combines ALBs, AWS WAF, and AWS Global Accelerator to improve availability, performance, security, and fulfill the static IP address requirement.