A global news site serves 5M readers with personalized headlines requiring sub-50ms header rewrites at edge and heavier A/B personalization needing regional compute. Cache hit ratio must stay high. Which edge architecture using CloudFront Functions and Lambda@Edge meets latency and compute needs?
Select an answer to reveal the explanation.
Short Explanation
You're putting quick errands by the front door. Lightweight Functions handle rewrites in microseconds while Lambda@Edge does heavy lifting, and proximity keeps readers snappy.
Full Explanation
CloudFront Functions runs lightweight JavaScript at edge locations with sub-millisecond startup ideal for header manipulation, redirects, and normalization without hurting cache efficiency, while Lambda@Edge supports larger runtimes, network access, and longer execution for dynamic personalization at viewer or origin triggers. Reversing them wastes cost and latency because Lambda@Edge incurs higher startup and charges for simple rewrites, and CloudFront Functions cannot run heavy personalization logic with its limits. Origin Shield and ALB rules centralize logic away from edge, increasing latency and reducing cache hits for global readers. WAF Bot Control filters bots and cannot perform general header rewrites. For the exam, remember Functions for simple edge rewrites and Lambda@Edge for compute-heavy customization, and in practice test cache policies to separate static and personalized paths.