Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 301 discussion

REST APIs and HTTP APIs are both RESTful API products. REST APIs support more features than HTTP APIs, while HTTP APIs are designed with minimal features so that they can be offered at a lower price. Choose REST APIs if you need features such as API keys, per-client throttling, request validation, AWS WAF integration, or private API endpoints. Choose HTTP APIs if you don't need the features included with REST APIs.

Option A answer is little confusing because it talks about Quota but not about Throttle limits. Option B mentions route-level throttling that is also not correct. Route-level throttling can not be applied at per user basis. So option A is right answer.

A This approach allows you to create a separate API Gateway instance for each customer, which enables you to implement quotas at the API level. By using a proxy integration, you can invoke the Lambda function on behalf of each customer, while still enforcing their individual quota limits. Configuring an API Gateway usage plan and creating an API key for each user within a customer's organization allows you to manage and enforce quotas for each user separately. This solution is particularly well-suited for managing multiple customers with different quota requirements. By using API Gateway, you can create separate APIs for each customer, which enables fine-grained control over quota enforcement at the client level.

Option A https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-vs-rest.html

In order to achieve "Some customers must receive a higher quota for a shorter time period.", throttling should be set with rate and burst can be set using Throttling

Option A https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-vs-rest.html

Its A, you dont need route level throttling

Option B route-level throttling for each usage plan

https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-usage-plans.html HTTP API doesn't include USAGE feature.

Option A Create REST API with Proxy Integration and for each customer set the usage plan and Create API Key. https://medium.com/geekculture/api-key-and-usage-plan-integration-with-aws-api-gateway-2d07bbb9a2a4