Answer: A, C
A. Create an Amazon API Gateway REST API. Configure this API with direct integrations to DynamoDB by using API Gateway’s AWS integration type.
C. Create an Amazon API Gateway HTTP API. Configure this API with integrations to AWS Lambda functions that return data from the DynamoDB tables.
Explanation: Here's a detailed justification for why options A and C are the correct choices, and why the others are not: Why A is correct: Amazon API Gateway REST API: API Gateway is a fully managed service that makes it easy to create, publish, maintain, monitor, and secure APIs at any scale. It's designed for creating robust, scalable APIs for backend services. A REST API allows you to expose your DynamoDB data through standard HTTP methods (GET, POST, PUT, DELETE). Direct Integrations (AWS Integration Type): API Gateway offers "AWS Service Proxy" integrations, which allow you to directly integrate with AWS services like DynamoDB without needing to write any code. You can map the incoming HTTP request parameters to DynamoDB operations (e.g., GetItem , Query , Scan ). This greatly simplifies the architecture and reduces latency. Why C is correct: Amazon API Gateway HTTP API: Similar to REST APIs, HTTP APIs also offer a way to expose backend functionality via HTTP. They are often more cost-effective and have lower latency than REST APIs for simpler use cases. Lambda Function Integration: This involves using Lambda functions as an intermediary layer between the API Gateway and DynamoDB. The API Gateway triggers the Lambda function upon receiving a request. The Lambda function then interacts with DynamoDB (e.g., querying the database), processes the retrieved data, and returns the response back to the API Gateway, which in turn sends it to the client. This offers flexibility in data transformation and business logic implementation. Why B is incorrect: While HTTP APIs are a viable option for creating APIs, direct integration with DynamoDB is not a supported feature for HTTP APIs. They are better suited for proxying requests to backend computes such as Lambda functions, HTTP endpoints or Application Load Balancers. Why D is incorrect: AWS Global Accelerator and Lambda@Edge: While Global Accelerator improves application availability and performance for globally distributed users, it is not primarily designed for API functionality as described in the question. While Lambda@Edge, which operates as part of CloudFront, could interact with DynamoDB, it's more commonly used for edge processing and caching closer to users. Using it as the primary API layer introduces unnecessary complexity compared to API Gateway. Why E is incorrect: Network Load Balancer (NLB) with Lambda: While NLBs can front Lambda functions, they are not typically used to expose API endpoints directly to the public. An NLB is a Layer 4 load balancer, which means it operates on the transport layer. It primarily handles TCP, TLS, and UDP traffic. API Gateway provides better features to define API endpoints and ensure security with authorization. In summary: Options A and C provide the best serverless architectures for exposing DynamoDB data via a public API, offering scalability, security, and ease of management. Option A simplifies the setup with direct integrations, while Option C provides more flexibility and customization. Authoritative Links: Amazon API Gateway: AWS Lambda: Amazon DynamoDB: API Gateway AWS Integrations: A company has registered 10 new domain names. The company uses the domains for online marketing. The company needs a solution that will redirect online visitors to a specific URL for each domain. All domains and target URLs are defined in a JSON document. All DNS records are managed by Amazon Route 53.
Reference:
https://aws.amazon.com/api-gateway/
https://aws.amazon.com/lambda/
https://aws.amazon.com/dynamodb/
https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-integration-types.html