Exam AWS Certified Solutions Architect - Professional topic 1 question 823 discussion

"multiple API methods" and "Logs indicate that the Lambda function is never invoked" makes me think it's Account-level throttling and not Per-Method Throttling.

key word: Too Many Requests from multiple API methods during peak usage hours

correct D. Option C states that the company reached its API Gateway account limit for calls per second, which is a throttling limit that applies to all methods in all REST APIs within an AWS account and Region. This option is not a likely cause of the error messages, because it affects all methods in all REST APIs within an account and Region, whereas the error messages are reported by only some of the premium tier customers in various Regions. If option C was the cause, then all customers in all Regions would receive the same error messages. Moreover, option C does not explain why the Lambda function is never invoked, because the account limit for calls per second occurs before the request reaches the integration layer. Therefore, option D is more likely than option C, because it affects only specific methods in specific REST APIs, and it does not invoke the Lambda function.

C is for Too Many Request of limit of API Gateway foureye2004 is correct D is for error Limit Exceed Same question in version 2 of SAP 02 in ExamTopic https://www.examtopics.com/discussions/amazon/view/95465-exam-aws-certified-solutions-architect-professional-sap-c02/ C

It would be all customers complaining if if it's C. And here is several premium customers complaining - I think it's D

I'll go with C

from multiple API methods during peak usage hours

Should be C https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html#apig-request-throttling-account-level-limits The documents is really clear for the error 429 Too Many Requests with D, maybe the error will be: 429 Limit Exceeded

https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html#apig-request-throttling-account-level-limits

After reviewing it few times i will have to choose C. If the company sends 10 keys for 10 different users it will for sure cross the 10k quota. Why not D? the default per-method limit is the same as Usage plan - and this is limit to 3000.

C in my opinion

In my opinion, I would choose D over C. Because 429 error, we should think about client error, so eliminate A & B due to Lamdba is server side. Between C and D, Rest API could get 10,000 requests per second as the link below https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html While the question mention that user request upto 3000/s, so C should not be the reason cause error. So the remain answer should be D.

C is correct. It is because other API's caused the limit being reached. D is incorrect. If it is due to per method limit (20 per second). There would be some Lambda functions fired before throtolling happened. But it said Lambda functions never fired.

I also think its C

D could be the answer. Default throttling limit for API gateway is 10,000. Seems method level throttling defined in the usage plan is causing the 429 error.

D is the ans C: Default API gateway account limit is 10,000 requests per second A,B: wrong choices as Lambda never called on erroneous requests

I thought this one was tough tbh, because both Lambda concurrency issues and API gateway throttling can cause this error. My logic in the end was that it was C, because of the numbers quoted in https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html. In essence the requests per second limit per *account* is 10,000, so selling premium subscriptions that allow up to 3000 isnt scalable, and there is no mention of an account per API. Moreover that link seems to suggest that regional APIs are 600p/s. Tricky and im still not entirely sold on my answer.