Back to Amazon API Gateway

API Gateway Integration

5 minutes 5 Questions

API Gateway supports different types of integrations with back-end systems, such as AWS Lambda, AWS Service proxies, or HTTP proxies. This allows API Gateway to connect with various services to process incoming requests and respond accordingly. For example, a Lambda integration allows API Gateway t…

Test mode:
Start practice test
AWS Certified Solutions Architect - API Gateway Integration Example Questions

Test your knowledge of API Gateway Integration

Question 1

You operate a REST API on Amazon API Gateway with read-heavy GET endpoints that often return identical responses for several minutes. During peak traffic, users see increased latency due to backend load. Without changing the backend implementation, which API Gateway feature should you enable to reduce latency for repeat requests and decrease backend load?

Correct Answer: API Gateway caching

Enabling API Gateway caching stores responses from backend integrations in a stage-level cache for a configurable TTL. During peak traffic, repeat requests for the same resource can be served directly from the cache, reducing round trips to the backend, lowering backend load, and improving end-to-end latency. This is especially effective for read-heavy, idempotent GET endpoints where responses are reusable for short periods. AWS Lambda Provisioned Concurrency reduces cold-start latency for Lambda-backed APIs but does not address latency caused by backend overload or repeated identical reads. Adjusting throttling limits affects request rates and 429 errors, not per-request latency, and can worsen backend load. Access logging provides observability but does not improve response time.

Question 2

A company has an existing API Gateway connected to a Lambda function. The API Gateway receives POST requests from clients. As an Architect, how can you ensure that API Gateway passes the entire original request, including any newly added headers, to the Lambda function without manual modifications?

Correct Answer: Enable 'Use Lambda Proxy Integration' option

By enabling the 'Use Lambda Proxy Integration' option, the API Gateway will transform the entire request, including headers, body, and query strings automatically without the need for manual modification.

Question 3

An organization needs to expose an API privately using Amazon API Gateway so that it is reachable only from within their VPCs. They want to allow calls only from specific VPC interface endpoint IDs (for example, to whitelist selected VPCs or accounts). What is the best approach to enforce this restriction?

Correct Answer: Create a VPC endpoint and use a resource policy

For an Amazon API Gateway Private API, the supported way to restrict access to specific VPCs is to use interface VPC endpoints (PrivateLink) and enforce access with an API Gateway resource policy. You create the com.amazonaws..execute-api VPC endpoint in the VPCs that should access the API, then attach a resource policy to the private API that allows execute-api:Invoke only when the request originates from the allowed VPC endpoint IDs (using the aws:SourceVpce condition), optionally scoping by account or principal. AWS WAF applies to regional/public APIs and cannot secure a private API. Security groups on the VPC endpoint can limit traffic within a VPC but are not sufficient or authoritative for API-level access control, especially across accounts. Lambda authorizers handle authentication/authorization but do not provide network-level isolation or VPC scoping.

More API Gateway Integration questions
18 questions (total)
Start 18 question test