List of questions
Related questions
Question 166 - Certified MuleSoft Integration Architect I discussion
A rale limiting policy has been applied to a soap VI.2 API published in Clondhub. The API implementation catches errors in a global error handler on error propagate in the main flow for HTTP: RETRY_EXHAUSTED with HTTP status set to 429 and any with the HTTP status set to 500.
What is the expected H1TP status when the client exceeds the quota of the API calls?
A.
HTTP status 429 as defined in the HTTP:RETRY EXHAUSTED error handler in the API
B.
HTTP status 500 as defined in the ANY error handler in the API since an API:RETRY_EXHAUSTED will be generated
C.
HTTP status 401 unauthorized for policy violation
D.
HTTP status 400 from the rate-limiting policy violation since the call does not reach the back-end
Your answer:
0 comments
Sorted by
Leave a comment first