Q83 — AWS DOP-C02 Ch.3

Question 83 of 100 | ← Chapter 3

A company operates a globally deployed product serving customers outside its home region. Its development team needs to deploy an API using Amazon API Gateway to support this product. The solution must redundantly deploy the API, provide independent availability for each deployment location, assign custom domain URLs per location, and optimize performance for API client requests.

• A. Deploy an API Gateway edge-optimized API endpoint in the US East (N. Virginia) Region. Create a custom domain for the API Gateway API. Create an Amazon Route 53 record set with a geoproximity routing policy for the API's custom domain. Set the geoproximity bias to the maximum allowed value.
• B. Deploy an API Gateway regional API endpoint in the US East (N. Virginia) Region. Integrate the API Gateway API with a public Application Load Balancer (ALB). Create a Global Accelerator standard accelerator. Associate the endpoint with an Amazon Route 53 alias record set pointing the custom domain to the accelerator's DNS name.
• C. Deploy API Gateway regional API endpoints in each AWS Region where the company’s product is deployed. Create an API Gateway custom domain for the deployed API in each Region. Create an Amazon Route 53 record set with a latency-based routing policy for each deployed API Gateway custom domain. ✓
• D. Deploy an API Gateway edge-optimized API endpoint in the US East (N. Virginia) Region. Create an Amazon CloudFront distribution. Configure CloudFront with another domain name and specify the API Gateway invoke URL as the origin. Create an Amazon Route 53 alias record set with a simple routing policy pointing to the CloudFront domain name.

Correct Answer: C. Deploy API Gateway regional API endpoints in each AWS Region where the company’s product is deployed. Create an API Gateway custom domain for the deployed API in each Region. Create an Amazon Route 53 record set with a latency-based routing policy for each deployed API Gateway custom domain.

Explanation

Amazon API Gateway regional API endpoints are deployed within specific AWS Regions. When combined with custom domains and Amazon Route 53 latency-based routing policies, they enable redundant multi-Region deployments while optimizing request latency for end users. AWS documentation states that latency-based routing directs traffic to the Region with the lowest latency from the user’s location, ensuring optimal performance. Option C deploys regional API endpoints in every target Region, creates a custom domain per Region, and configures Route 53 latency-based record sets — satisfying redundancy, independent availability, and performance requirements. Other options either lack multi-Region coverage or do not leverage latency optimization.