This website uses cookies to ensure you get the best experience.
Learn more.
A handler times out while waiting for a downstream HTTP call with no client deadline. Retries can repeat writes. Which changes are appropriate? Select 2 answers.
Published
- Set suitable connection and read deadlines within the invocation time budget.
- Ignore all downstream exceptions and always return a completed result.
- Generate a new order ID after every timeout and repeat the purchase automatically.
- Use bounded retry policies and idempotency for operations that can be repeated after an uncertain response.
- Remove every timeout so the function can wait indefinitely.
Comments — 0
Sign in to comment