SAP-C02 Question #379: Real Exam Question with Answer & Explanation

Question

A company is building an electronic document management system in which users upload their documents. The application stack is entirely serverless and runs on AWS in the eu-central-1 Region. The system includes a web application that uses an Amazon CloudFront distribution for delivery with Amazon S3 as the origin. The web application communicates with Amazon API Gateway Regional endpoints. The API Gateway APIs call AWS Lambda functions that store metadata in an Amazon Aurora Serverless database and put the documents into an S3 bucket. The company is growing steadily and has completed a proof of concept with its largest customer. The company must improve latency outside of Europe. Which combination of actions will meet these requirements? (Choose two.)

Options

• AEnable S3 Transfer Acceleration on the S3 bucket. Ensure that the web application uses the
• BCreate an accelerator in AWS Global Accelerator. Attach the accelerator to the CloudFront
• CChange the API Gateway Regional endpoints to edge-optimized endpoints.
• DProvision the entire stack in two other locations that are spread across the world. Use global
• EAdd an Amazon RDS proxy between the Lambda functions and the Aurora Serverless database.

Explanation

Enabling S3 Transfer Acceleration (A) routes document uploads through CloudFront's globally distributed edge locations, dramatically reducing upload latency for users far from eu-central-1 by sending data over AWS's optimized backbone instead of the public internet. Switching API Gateway to edge-optimized endpoints (C) similarly routes API calls through the nearest CloudFront edge PoP, reducing round-trip latency for users outside Europe without changing the underlying regional architecture.

Why the distractors fail:

• B is wrong because you cannot attach Global Accelerator to a CloudFront distribution - Global Accelerator works with ALBs, NLBs, and EC2/Elastic IPs; CloudFront already uses AWS's global edge network, making this redundant and architecturally invalid.
• D would technically improve latency but it's massively over-engineered - it requires multi-region database replication, routing logic, and operational overhead far beyond what's needed.
• E (RDS Proxy) solves Lambda connection pool exhaustion against Aurora, not geographic latency - it's a scaling/stability fix, not a latency fix.

Memory tip: Follow the request path - documents travel to S3 (fix with Transfer Acceleration) and API calls travel through API Gateway (fix with edge-optimized endpoints). Both solutions leverage the existing CloudFront edge network with minimal re-architecture, which is the AWS exam's preferred approach over full multi-region deployments.

No community discussion yet for this question.