Practice the vocabulary of composing a unified GraphQL API from independently owned subgraphs.
0 / 5 completed
1 / 5
At standup, a dev mentions composing a single unified GraphQL API from several independently owned subgraphs, each maintained by a different team. What is this architecture called?
GraphQL federation composes a single unified GraphQL API from several independently owned and deployed subgraphs, each maintained by a different team, presenting them to a client as one cohesive schema. A single monolithic schema maintained by one central team becomes an organizational bottleneck as more teams need to contribute their own domain's data. Federation lets each team independently own and evolve its own subgraph while still contributing to a genuinely unified API surface for clients.
2 / 5
During a design review, the team wants a type defined in one subgraph to be extended with additional fields contributed by a different subgraph. Which capability supports this?
Entity extension across subgraphs lets a type originally defined in one subgraph be extended with additional fields contributed by a different subgraph, letting a client query fields from both subgraphs on what appears to be a single, cohesive type. Requiring every field of a type to live in a single subgraph would prevent a separate team from meaningfully contributing its own related data to that same entity. This extension mechanism is central to what makes federation genuinely composable across independently owned subgraphs.
3 / 5
In a code review, a dev notices the federation gateway automatically plans how to fetch data from multiple subgraphs and combine it into a single response for one client query. What does this represent?
Federated query planning and execution automatically determines which subgraphs need to be queried and how to combine their results into a single coherent response for one client query, without the client needing any awareness of how the API is actually composed underneath. Requiring the client to manually issue a separate query to each subgraph defeats the entire purpose of presenting a unified API surface. This automatic planning is handled by the federation gateway, which sits between the client and the individual subgraphs.
4 / 5
An incident report shows a subgraph team deployed a breaking schema change without coordinating with other teams, breaking the composed federated schema for every client. What practice would prevent this?
Validating a subgraph's proposed schema change against the composed federated schema before deployment catches a breaking change that would otherwise disrupt the unified API for every client. Assuming a change in one subgraph can never affect the composed whole ignores exactly the kind of cross-team coordination federation requires to work safely. This composition validation step is a standard practice in a mature federated GraphQL setup, often enforced automatically in CI.
5 / 5
During a PR review, a teammate asks why the team adopted GraphQL federation instead of maintaining a single monolithic GraphQL schema owned by one central team. What is the reasoning?
A single monolithic schema owned by one central team becomes an organizational bottleneck as more teams need to contribute their own domain-specific data to the API. Federation distributes that ownership, letting each team evolve its own subgraph independently while still contributing to one unified schema clients can query. The tradeoff is the added infrastructure and coordination needed to plan and validate how the independently owned subgraphs compose together correctly.
What does the "GraphQL Federation Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to graphql federation vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.