Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 426 discussion

D is the proper answer CloudFront Functions - can be used only for manipulation with requests data CloudFront Lambda@Edge functions - can be used for anything, because this is a regular lambda function

Correct Answer is A

Aurora global databases have a primary region for writes and secondary read-only regions, which can add latency for write operations (marking barcodes as used).

I do not think it is Lambda@Edge use case which are mostly addressing routing or content management type of things or A/B testing. It is write intensive so i would choose Aurora and Global Accelerator and this is not about content cache (Cloud front)

Aurora Global Database provides low-latency read access from multiple Regions and allows writes in a primary Region. Since the system only marks the ticket as used once, it's safe to centralize writes. ECS clusters deployed regionally offer scalable, containerized API backends. AWS Global Accelerator routes users to the closest backend ECS cluster using the AWS edge network, minimizing latency and maximizing performance. Route 53 maps the DNS (api.example.com) to the Global Accelerator endpoint.

Option D is correct DynamoDB global tables: By hosting your database in multiple Regions, you can reduce latency for users located in different parts of the world. CloudFront: You can use CloudFront as a CDN to cache static assets and route dynamic requests to the nearest origin. In this case, it will direct users to the Lambda@Edge function closest to them. Lambda@Edge functions: These allow you to execute code at the edge of the network, which reduces latency and improves performance. Using Lambda@Edge functions in conjunction with DynamoDB global tables provides a great combination for reducing latency and improving performance.

Option: D

D withoud any doubt. For this simple data, a DynamoDB Table is enought; so global table is perfect. For check logic, cloudfront function is not enought because it is only for manipulate HTTP header or something very very light (code, metadata etc.). So for calling some backend layer (querying DynamoDB in this case) we need a Lambda@Edge function, which is much complete.

Option D

D. Lambda@Edge

https://aws.amazon.com/blogs/networking-and-content-delivery/leveraging-external-data-in-lambdaedge/ https://aws.amazon.com/blogs/networking-and-content-delivery/lambdaedge-design-best-practices/