A teammate explains that a game engine represents every game object as a plain numeric entity ID, attaches pure-data components like Position, Velocity, or Health to that ID, and lets stateless systems iterate over every entity that has a given combination of components to run their logic each frame. What is being described?
Entity-component-system (ECS) architecture is exactly what is described here. A DNS zone transfer is an unrelated concept about replicating name server records. Understanding ECS is exactly why it comes up so often in real engineering discussions of this kind of problem.
2 / 5
During a design review, the team adopts ECS, specifically to gain a concrete benefit. Which capability does this provide?
ECS here provides flexible composition of behavior from small, independently reusable data components, since a system only needs the entity to have the right components attached. A deep inheritance hierarchy where a Player class extends Character which extends GameObject, and adding one new behavior forces a change to the shared base class is the alternative this avoids. This behavior is exactly why ECS is favored in this kind of scenario.
3 / 5
In a code review, a dev notices a system relies on a deep inheritance hierarchy where a Player class extends Character which extends GameObject, and adding one new behavior forces a change to the shared base class, instead of using ECS. What does this represent?
This is a missed ECS-opportunity, since ECS would provide flexible composition of behavior from small, independently reusable data components, since a system only needs the entity to have the right components attached. A cache eviction policy is an unrelated concept about discarded cache entries. This pattern is exactly the kind of gap a reviewer flags once the tradeoffs are understood.
4 / 5
An incident report shows adding a single new gameplay behavior required editing a shared base class near the root of the inheritance tree, and the change broke unrelated object types that also inherited from it. What practice would prevent this?
Refactoring toward an entity-component-system, so a new behavior is added as an independent, composable component and system instead of editing a shared base class. Continuing the prior approach regardless of the risk it has already caused is exactly what led to the incident described here. This fix is the standard remedy once the root cause is confirmed.
5 / 5
During a PR review, a teammate asks why the team reaches for ECS instead of a deep inheritance hierarchy where a Player class extends Character which extends GameObject, and adding one new behavior forces a change to the shared base class. What is the reasoning?
ECS trades the upfront cost of designing data as small independent components for far more flexible composition, since new behavior is added by attaching a component rather than editing a shared base class, while a deep inheritance hierarchy is quicker to reach for on a small prototype but becomes rigid and fragile as more object types and behaviors accumulate. This is exactly why ECS is favored in scenarios that call for it, while the alternative remains acceptable in simpler cases that don't.
What does the "ECS Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to ecs 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.