1 / 5
Fill in: 'We ___ every incoming payload against a schema before it reaches business logic.'
-
-
-
-
We 'validate' a payload — the standard collocation for confirming it matches an expected shape. The other options aren't idiomatic here.
2 / 5
Fill in: 'We ___ a schema for every public endpoint so consumers know exactly what shape to send.'
-
-
-
-
We 'define' a schema — the standard collocation for specifying a data contract. The other options aren't idiomatic here.
3 / 5
Fill in: 'An overly loose schema can ___ malformed data straight through into the database.'
-
-
-
-
We say a loose schema will 'let' bad data through — the standard, natural collocation here. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ validation errors clearly so a client knows exactly which field failed and why.'
-
-
-
-
We 'report' errors — the standard collocation for surfacing validation failures to a caller. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ schemas alongside the API version so old and new contracts never get mixed up.'
-
-
-
-
We 'version' schemas — the standard collocation for tracking changes to a contract over time. The other options aren't idiomatic here.