Practise the standard verbs for building a GraphQL federation gateway.
0 / 5 completed
1 / 5
Fill in: 'We ___ a federated schema from several subgraphs so clients query one gateway instead of many separate services.'
We 'compose a schema' — the standard, established GraphQL federation collocation for merging subgraph schemas. The other options aren't the recognised term here.
2 / 5
Fill in: 'A type conflict between two subgraphs can ___ the entire federated schema failing to compose at build time.'
We say a type conflict will 'cause' a composition failure — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ entity references between subgraphs with the @key directive so the gateway can join data across services.'
We 'declare' a reference — the standard, established federation collocation for marking an entity's identifying fields. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ query plans generated by the gateway to confirm a single request isn't fanning out into dozens of subgraph calls.'
We 'inspect' a plan — the standard, simple collocation for examining a generated execution plan. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ each subgraph independently before publishing it to the schema registry so a bad deploy can't break the whole gateway.'
We 'validate' a subgraph — the standard, established collocation for verifying a schema meets federation rules. The other options aren't the recognised term here.