The correct options are An Amazon API Gateway REST API integrates directly with the DynamoDB table to read the sales metrics and An Amazon API Gateway REST API triggers an AWS Lambda function that retrieves items from the DynamoDB table.

Both choices use serverless, fully managed components and minimize operational effort. API Gateway direct integration can call DynamoDB without running compute and it gives a low latency, low management path. API Gateway invoking Lambda adds a compute layer when you need custom business logic or transformation and it still avoids managing servers.

An Application Load Balancer sends traffic to a target group that lists the DynamoDB table as the backend target is not possible because DynamoDB is not a supported ALB target type and ALB cannot route directly to database services.

An Application Load Balancer routes traffic to a target group of Amazon EC2 instances that query the DynamoDB table would work technically but it introduces instance lifecycle, patching, scaling, and monitoring overhead which conflicts with the requirement to keep operations minimal.

An Amazon Route 53 hosted zone routes requests directly to an AWS Lambda endpoint to run code that reads the DynamoDB table is incorrect because Route 53 is a DNS service and does not invoke Lambda directly and you need an HTTP front end such as API Gateway or CloudFront to expose Lambda over HTTP.

Full AWS Practitioner Certification Question