Networking · interview question
Why is retrying a GET for shipping rates usually safer than retrying a POST that charges a card?
Multiple choiceMediumchapter-11-curatedpremiumnetworkingtimeouts-and-retries
Answer and explanation
Correct answer
D. Because the GET is typically read-only, while the POST may create duplicate side effects
Why
A shipping-rate GET is usually safe to attempt again because it should not mutate remote state. Retrying a payment POST can duplicate business actions unless the remote API supports idempotency or deduplication.
Test yourself on Networking
A free test with instant, explained results. No account needed.
More Networking questions
- Which exception should be caught to handle timeouts specifically in HTTP client operations?
- In Java socket programming, what is the role of a two-way communication endpoint?
- Why does a Socket in Java networking matter in practice?
- When using Jackson's ObjectMapper to deserialize JSON, how can you handle unknown JSON properties without throwing an…
- Why do teams use Jackson's ObjectMapper in a Java application in production code?
- Why does the Content-Type header in HTTP requests matter in practice?