Practice English vocabulary for service ownership, dependency management, and system relationships in developer portals: owners, consumers, dependencies, APIs, and lifecycle stages.
0 / 5 completed
1 / 5
In a software catalog (such as Backstage), what does the 'owner' field of a component represent?
In catalog-based portals, ownership is about accountability, not authorship. The owner field points to a team or person who is responsible for keeping the service running, handling incidents, communicating breaking changes to consumers, and eventually deprecating the service. Catalog tools use ownership to route alerts, automatically populate on-call rosters, and identify who to contact before making changes to a dependency.
2 / 5
What does it mean for a service to have 'upstream dependencies'?
Upstream and downstream are often confused. In the software supply chain model: upstream dependencies are the services your service relies on (they feed data or functionality into yours), and downstream dependencies are services that rely on yours. If an upstream service changes its API or has an outage, your service is affected. Developer portals visualise these dependency graphs to help teams understand blast radius and change impact.
3 / 5
A catalog entry shows a service with lifecycle: 'deprecated'. What should teams consuming this service do?
The deprecated lifecycle stage signals that a service is in its end-of-life phase. The owner is communicating: 'We have a replacement — please migrate.' Consuming teams should: (1) identify the replacement in the catalog, (2) plan and execute migration, and (3) stop creating new dependencies on the deprecated service. Portals typically allow owners to link to migration guides and set a sunset date alongside the deprecated status.
4 / 5
What is a 'dependency graph' in a developer portal context?
Dependency graphs in developer portals (like Backstage's relationship view) show the runtime and build-time relationships between components, APIs, systems, and teams. They help answer questions like: 'If I change this API, who will break?' and 'What is the blast radius of this outage?' They are typically derived from catalog-info.yaml files where components declare their dependsOn and providesApis / consumesApis relationships.
5 / 5
The platform team says a service is 'well-catalogued'. What does this mean?
A well-catalogued service has all its metadata kept current in the software catalog. This typically means: (1) the owner field points to an active team, (2) the lifecycle reflects reality (production, experimental, deprecated), (3) all consumed and provided APIs are declared, (4) links to documentation, runbooks, and dashboards are populated, and (5) the service passes the platform's catalog scorecard thresholds. Poorly catalogued services create operational risk because engineers can't find ownership or runbooks during incidents.
What does the "Service Ownership & Dependency Vocabulary" exercise cover?
Practice English vocabulary for service ownership, dependency management, and system relationships in developer portals: owners, consumers, dependencies, APIs, and lifecycle stages.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Service Ownership & Dependency Vocabulary"?
This exercise has 5 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Developer Portal Vocabulary exercises?
Browse the full Developer Portal Vocabulary hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.