Practise the standard verbs for compressing API responses effectively.
0 / 5 completed
1 / 5
Fill in: 'We ___ gzip compression on every API response above a minimum size to cut bandwidth without much CPU cost.'
We 'enable compression' — the standard, simple collocation for turning on a response-processing feature. The other options are less idiomatic here.
2 / 5
Fill in: 'Compressing tiny responses can ___ more CPU overhead than the bandwidth it actually saves.'
We say compressing small payloads will 'cost' more overhead than benefit — the standard collocation for a net-negative trade-off. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the Accept-Encoding header from the client before choosing whether to compress the response at all.'
We 'check' a header — the standard, simple collocation for inspecting request metadata. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ Brotli over gzip when the client supports it, since it typically compresses text more tightly.'
We 'prefer' one option — the standard, simple collocation for choosing between two comparable choices. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ payload sizes before and after enabling compression to confirm it's actually paying off.'
We 'measure' sizes — the standard, simple collocation for evaluating an effect numerically. The other options are less idiomatic here.