Q53 — AWS SAP-C02 Ch.3

Question 53 of 75 | ← Chapter 3

Q278. A software-as-a-service (SaaS) provider exposes APIs through an Application Load Balancer (ALB). The ALB connects to an Amazon Elastic Kubemetes Service (Amazon EKS) cluster that is deployed in the us- east-1Region. The exposed APIs contain usage of a few non-standard REST methods: LINK, UNLINK, LOCK and UNLOCK. Users outside the United States are reporting long and inconsistent response times for these APIs. A solutions architect needs to resolve this problem with a solution that minimizes operational overhead. Which solution meets these requirements?

Correct Answer: C. Add an accelerator in AWS Global Accelerator. Configure the ALB as the origin

Explanation

The solution that meets the requirements to resolve the problem with long and inconsistent response times for non-standard REST methods, with minimal operational overhead is C. C. Add an accelerator in AWS Global Accelerator. Configure the ALB as the origin This solution addresses the issue of long and inconsistent response times by adding an accelerator in AWS Global Accelerator. The Global Accelerator uses AWS's global network infrastructure to improve the performance of applications used by a global audience. The ALB is configured as the origin for the accelerator and it automatically routes traffic to the optimal endpoint. This approach minimizes operational overhead because it does not require any additional deployment or configuration. A, B, and D are not optimal solutions: A. Add an Amazon CloudFront distribution. Configure the ALB as the origin This solution involves adding an Amazon CloudFront distribution to cache and distribute content globally. However, this approach may not be suitable for non-standard REST methods, as CloudFront may not support them. Additionally, it may require additional configuration and maintenance. B. Add an Amazon API Gateway edge-optimized API endpoint to expose the APIs. Configure the ALB as the target. This solution involves adding an Amazon API Gateway endpoint to expose the APIs. However, this approach may not be suitable for non-standard REST methods, as API Gateway may not support them. Additionally, it may require additional configuration and maintenance. D. Deploy the APIs to two additional AWS Regions (eu-west-1 and ap-southeast-2). Add latency-based routing records in Amazon Route 53. This solution involves deploying the APIs to additional AWS Regions and using Amazon Route 53 to route traffic based on the lowest latency. While this approach can improve performance for users outside the United States, it requires additional deployment and configuration of resources in multiple regions, resulting in increased operational overhead. Additionally, this approach may not address the issue of inconsistent response times for non-standard REST methods.