Practise the standard verbs for defining Elasticsearch index mappings safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ an explicit mapping before indexing so Elasticsearch never guesses a field's type incorrectly.'
We 'define a mapping' — the standard, established Elasticsearch collocation for declaring field types up front. The other options aren't the recognised term here.
2 / 5
Fill in: 'A dynamic mapping left unchecked can ___ a mapping explosion once too many distinct field names appear.'
We say uncontrolled dynamic mapping will 'cause' an explosion — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a new index with the corrected mapping and reindex into it rather than editing the mapping in place.'
We 'create an index' — the standard, established Elasticsearch collocation for provisioning a new index. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ query performance after a mapping change to confirm the new field types didn't slow anything down.'
We 'measure' performance — the standard, simple collocation for evaluating an effect. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ an alias to point at the new index so clients can query it without knowing the underlying name changed.'
We 'use an alias' — the standard, established Elasticsearch collocation for abstracting the underlying index name. The other options aren't the recognised term here.