ExamTopics Logo
Mail Us[email protected]
Menu
Amazon Discussions
exam questions

Exam AWS Certified Solutions Architect - Professional All Questions

View all questions & answers for the AWS Certified Solutions Architect - Professional exam
Go to Exam

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

Exam question from Amazon's AWS Certified Solutions Architect - Professional
Question #: 778
Topic #: 1
[All AWS Certified Solutions Architect - Professional Questions]

A software company has deployed an application that consumes a REST API by using Amazon API Gateway, AWS Lambda functions, and an Amazon
DynamoDB table. The application is showing an increase in the number of errors during PUT requests. Most of the PUT calls come from a small number of clients that are authenticated with specific API keys.
A solutions architect has identified that a large number of the PUT requests originate from one client. The API is noncritical, and clients can tolerate retries of unsuccessful calls. However, the errors are displayed to customers and are causing damage to the API's reputation.
What should the solutions architect recommend to improve the customer experience?

  • A. Implement retry logic with exponential backoff and irregular variation in the client application. Ensure that the errors are caught and handled with descriptive error messages.
  • B. Implement API throttling through a usage plan at the API Gateway level. Ensure that the client application handles code 429 replies without error.
  • C. Turn on API caching to enhance responsiveness for the production stage. Run 10-minute load tests. Verify that the cache capacity is appropriate for the workload.
  • D. Implement reserved concurrency at the Lambda function level to provide the resources that are needed during sudden increases in traffic.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
by Firelord at Dec. 31, 2021, 12:32 a.m.
Disclaimers:
  • - ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
  • - Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
Firelord
Highly Voted 2 years, 11 months ago
Put can’t be cached, better throttling
upvoted 11 times
...
RVivek
Highly Voted 2 years, 9 months ago
Answer A. Custermer can accept delay /even failed attempts. https://aws.amazon.com/premiumsupport/knowledge-center/aws-batch-requests-error/
upvoted 8 times
...
marszalekm
Most Recent 10 months, 1 week ago
Selected Answer: B
https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-usage-plans.html
upvoted 1 times
...
Jesuisleon
1 year, 6 months ago
Selected Answer: B
B is wrong, if you implement AP throttling, then it will impact all clients not just that client with put request. "clients can tolerate retries of unsuccessful calls" it implies using retry logic.
upvoted 3 times
...
dev112233xx
1 year, 7 months ago
Selected Answer: B
The main reason of the "errors" is the one client that sends too many requests to the API Gateway. i don't think retry will solve this. better to limit the request through usage plan.
upvoted 2 times
...
[Removed]
1 year, 9 months ago
I dont see how throttling will help, if you set a throttle limit clients will still hit that limit and get error 429, which according to AWS documentation can be resolved by using retries and an exponential backoff algorithm with jitter, and then resubmit your API request.
upvoted 1 times
...
yuyuyuyuyu
1 year, 11 months ago
The problem is that an error is displayed. The way to solve that is B.
upvoted 1 times
...
evargasbrz
1 year, 11 months ago
Selected Answer: B
i'll go with B
upvoted 1 times
...
Blair77
2 years, 1 month ago
Selected Answer: A
AAA - all the information here: https://aws.amazon.com/premiumsupport/knowledge-center/api-gateway-429-limit/
upvoted 3 times
...
wassb
2 years, 1 month ago
Selected Answer: A
I would go for A since the throttling can affect the other clients. Answer B would have been more accurate if we were using the API key specific to the client for the usage plan.
upvoted 2 times
...
skywalker
2 years, 1 month ago
Selected Answer: A
A. B. is not ok since large number of the PUT requests originate from one client... Having Usage Plan to control throttle will not help. C. No clue. D. Problem is not Lambda issue
upvoted 1 times
...
joancarles
2 years, 2 months ago
Selected Answer: B
Usage plans seems the best way to improve the customer experience. Option A doesn't fix nothing in this sense, so I go for B here.
upvoted 2 times
...
wannaaws
2 years, 4 months ago
Concern is "faults are visible to clients, jeopardizing the API's reputation", implies no failure should/error be made visible to client. App can retry from backend in event of 429. Hence B is preferred.
upvoted 2 times
...
Hasitha99
2 years, 7 months ago
Selected Answer: B
API gateway support based on customers (since they are using API keys)
upvoted 2 times
...
pat100
2 years, 9 months ago
Answer B - 1) REST API - allows Usage Plan and API Keys - which help enable throttle requests - by request per second or burst requests 2) API Keys can be associated to client 3) When client submit requests breaching defined threshold, they will receive 429 - client error, NOT API server error - This is the key requirement as server errors dents API reputation Clients can catch such exceptions [429 Too Many Requests error responses ], the client can resubmit the failed requests in a way that is rate limiting https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html
upvoted 5 times
user0001
2 years, 7 months ago
B, since we know the majority of them are coming from 1 client, B will solve the issue
upvoted 2 times
...
...
Dohecadi
2 years, 9 months ago
Selected Answer: A
A is correct. Three points from the question: a) The application is seeing an increase in the amount of PUT request failures. b) However, the faults are visible to clients, jeopardizing the API's reputation. It also says: c) The API is not mission-critical, and customers may accept failed call retries. A. From point "c" above, retries are permissable. B. From point "b" above, throttling even further will only make it worse. C. From point "a" above, caching on API is best suited for GET rqeuests. D. Problem is with API Gateway not Lambda.
upvoted 2 times
...
GeniusMikeLiu
2 years, 10 months ago
A or B??
upvoted 1 times
GeniusMikeLiu
2 years, 10 months ago
should be A. customer can accept retry.
upvoted 1 times
...
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago