Exam AWS Certified Developer Associate topic 1 question 75 discussion

cannot be D since adding API key would require client code change

A since all clients has to be limited same "limit the number of requests to the API for all current and future clients"

Option A: "Place the API behind an API Gateway and set server-side throttling limits." This refers to stage-level throttling or account-level throttling, which limits traffic globally for all clients collectively. https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html ✅ This approach is correct because the question asks for a global throttling mechanism that applies to all current and future clients. Option D: "Place the API behind an API Gateway and set per-client throttling limits." This refers to usage plans with API keys, where throttling limits are set per client. ❌ This approach is incorrect because the question explicitly states that the limit should apply to all clients collectively.

i think it should be D since the question mentions about limiting the number of requests for client so it has to be D and with A there is no such server side throttling in API gateway instead there is stage level throttling

I know there is no such option as server side throttling as such, but I think AWS here is referring to per API, per Stage limits. Per client throttling can be used for individual clients, but if the number of client increase it would still cause a problem overall. Furthermore it uses Client Identifiers as the API Key. How can these be provisioned keeping in mind all future clients.

A The only reason and important point that makes D incorrect is the keyword "cannot support concurrent invocations". And again, what makes A doubt full is the term "server side throttling" is there a such thing related to API Gateway? So my conclusion I would take the risk of answering A is correct - but I could be wrong.

I go with A and here is why D is not correct Let's assume the ec2 instance in the question can only process 100 requests per second and will not cope with further request count - On the API Gateway console there are two kinds of throttling, one of which can be applied the whole stage and this limits the number of all requests coming through the API to the origin EC2 this one is correct because it makes sure that the APP will never get overwhelmed by requests it can not cope with so for example if we set the stage to 100 requests per second, only 100 requests will pass throw the API to the EC2 instance screenshot: https://monosnap.com/file/0o6S7cqqQ4X2aKYCYWFgDMx1cStwt7 - D can not be correct because if we set the per-client limit to for example 1 and we then get 200 customers, this means 200 requests can pass through the API and overwhelm the instance

Yet another tricky worded questions ... On one side, there is no such a thing like "server-side" throttling in APIGW. However, in the context of the question this sounds to me like "per-stage / per-method" throttling. On the other side, per-client throttling would not prevent different client to concurrently access the API. Thus A (by the way I think that per API-limit cannot prevent different client to concurrently access the API, but only limit it)

https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html

Option D (placing the API behind an Amazon API Gateway API and setting per-client throttling limits) would require modifying the client code, which is explicitly mentioned as a constraint in the question.

D provides per-client throttling, but still accesses the application's REST API directly and does not solve the issue of API load.

The answer is D and I am 100% sure. For those who chose A, there is no such thing as server side limit. And the question clearly states that the developer needs to set limits for current and future clients. Such an easy question but people seem to be confused. Refer to this page: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html

Answer is D

This option meets the requirements as it allows the developer to limit the number of requests to the API without changing the API, the application or the client code. By placing the API behind an Amazon API Gateway, the developer can set server-side throttling limits which will apply to all clients accessing the API. This will ensure that the number of requests to the API does not become overwhelming and affect the performance of the application.

answer D As an API developer, you can set the target limits for individual API stages or methods to improve overall performance across all APIs in your account. Alternatively, you can enable usage plans to set throttles on client request submissions based on specified requests rates and quotas.

D it is Amazon API Gateway provides four basic types of throttling-related settings: AWS throttling limits are applied across all accounts and clients in a region. Per-account limits are applied to all APIs in an account in a specified Region. Per-API, per-stage throttling limits are applied at the API method level for a stage. Per-client throttling limits are applied to clients that use API keys associated with your usage plan as client identifier. Note that these limits can't be higher than the per-account limits.

ANS: D Per-client throttling limits are applied to clients that use API keys associated with your sage plan as client identifier. Note that these limits can't be higher than the per-account limits. https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html