|
|
|
|
|
by kazinator
2933 days ago
|
|
This is not really an opinion question. It is intended to test the basic understanding of what idempotence is, not whether it is a good idea to use and in what situations. "Useful" doesn't mean "preferred over other alternatives". You're overthinking the test due to having more advanced qualifications. Idempotence, as you know, allows operations to be retried without the maintenance of state to detect duplicate operation, and so the correct answer is simply B. A is somewhat of a distractor since use of idempotent API's is possibly relevant in building scalable systems. Idempotence isn't the cornerstone of scalability, though. C is nonsense; and D is opposite: idempotence allows clients to freely send duplicate API requests. Prevention or detection of duplicates is required when idempotence doesn't hold. I don't see the point of including E; only a complete moron would not guess among the other answers to have a chance at being right. Very odd to see "I don't know" in a multiple choice test. |
|