1 / 5
Fill in: 'We ___ a consistent error taxonomy so clients can handle failures programmatically.'
-
-
-
-
We 'define' a taxonomy — the standard collocation for establishing a structured classification. The other options aren't idiomatic here.
2 / 5
Fill in: 'We ___ every error with a machine-readable code, not just a human-readable message.'
-
-
-
-
We 'tag' an error — the standard collocation for attaching a structured identifier. The other options are less idiomatic here.
3 / 5
Fill in: 'Vague error messages can ___ integrators into guessing what actually went wrong.'
-
-
-
-
We say vague messages will 'leave' integrators guessing — the standard, natural collocation here. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ retryable errors from permanent ones so clients know when retrying is pointless.'
-
-
-
-
We 'distinguish' error categories — the standard collocation for separating them meaningfully. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ the taxonomy in the API docs so every consumer works from the same reference.'
-
-
-
-
We 'publish' a taxonomy — the standard collocation for making a reference document public. The other options aren't idiomatic here.