Answer: AWS Lambda, Amazon DynamoDB

## Explanation **AWS Lambda (Option B)** is the correct choice for the compute layer because: - It provides automatic scaling from 0 to over 500 requests per second without any provisioning - No need to manage servers or scaling policies - Pay-per-use pricing model aligns with unpredictable traffic patterns - Seamless integration with API Gateway **Amazon DynamoDB (Option C)** is the correct choice for the database layer because: - It's a fully managed NoSQL database that supports simple key-value queries - Provides automatic scaling to handle unpredictable traffic patterns - Can scale from zero to thousands of requests per second automatically - Suitable for data less than 1 GB with unpredictable future growth - Serverless architecture with pay-per-request pricing **Why not the other options:** - **AWS Fargate (Option A)**: While serverless, it still requires container management and may not scale as quickly as Lambda from 0 to 500+ requests per second - **Amazon EC2 Auto Scaling (Option D)**: Requires provisioning and management of scaling policies, not ideal for sudden spikes from 0 to 500+ requests - **MySQL-compatible Amazon Aurora (Option E)**: While it can scale, it's a relational database and not optimized for simple key-value queries; DynamoDB is more suitable for this use case The combination of AWS Lambda and Amazon DynamoDB provides a fully serverless, auto-scaling architecture that can handle unpredictable traffic patterns while efficiently managing simple key-value data queries.

Author: LeetQuiz Editorial Team