Practice English vocabulary for software catalogs: catalog entries, ownership, service dependency graphs, catalog completeness, orphan components, and finding the owning team.
0 / 25 completed
1 / 25
What distinguishes a 'software catalog' from a traditional service catalog?
Software catalogs (like Backstage's) are engineering-facing tools designed to track the full estate of software assets and their relationships. IT service catalogs (like ServiceNow) are typically business-facing and list services users can request. Different audiences, different purposes.
2 / 25
What is the 'lifecycle' field in a catalog entry used for?
Lifecycle communicates a component's operational maturity. 'Experimental' means early-stage and not production-ready. 'Production' means fully supported with an on-call owner. 'Deprecated' warns consumers to migrate. This helps engineers make informed dependency decisions.
3 / 25
What is an 'orphan component' in a software catalog?
Orphan components are a catalog health issue: the entry exists but the owner team has been disbanded, renamed, or simply never assigned. Orphans create operational risk — when something breaks, there is no clear team to page. Catalog hygiene work often involves resolving orphans.
4 / 25
How would you explain 'catalog completeness score' to an engineering manager?
Catalog completeness is a quality metric for the software catalog itself. A component missing an owner, a stale description, or undeclared dependencies reduces its completeness score. Platform teams track this to drive catalog adoption and ensure the data is actually useful.
5 / 25
How would you use 'finding the owning team' in a sentence about the catalog?
'Finding the owning team' is a core catalog use case. When an API is misbehaving, a consumer needs to know who to contact. Without a catalog, this means Slack messages and organisational archaeology. With a catalog, the owner is one click away.
6 / 25
Sarah: "Hey team, I'm struggling to find the API documentation for the PaymentService. It's listed in the catalog, but the link is broken and I can't access it."
This scenario highlights the importance of understanding catalog entries beyond just their presence. While broken links are frustrating, Sarah's problem isn't necessarily with the catalog itself; it's likely a stale or incorrect reference within the catalog. The correct response is to investigate whether the documentation URL has been updated – this is a common issue requiring a quick check of the catalog entry details, not immediate escalation.
7 / 25
David: "I'm seeing a lot of entries in the software catalog that say 'In Development.' What does that actually *mean*? Should I be prioritizing these or treating them like fully deployed services?"
The term 'In Development' in a software catalog signifies more than just a stage of deployment. It's a status flag indicating the component is actively being tested, potentially undergoing significant changes, and is therefore considered unstable. Treating it with caution – prioritizing it appropriately – aligns with best practices when dealing with components marked as 'In Development,' preventing misinterpretations about their stability or readiness for production.
8 / 25
PR Description:
"Fix: Updated documentation for the AuthService. Added details on rate limiting and authentication flows. Also, updated the catalog entry to reflect the new API version (v2)."
Which of the following best describes the significance of updating the 'catalog entry' in this PR description?
A. It solely indicates a change in the API version being used.
B. It signifies that the documentation has been corrected, and the catalog record now accurately reflects the updated service state.
C. It's primarily a notification to the team about the new API version, with no impact on the software catalog itself.
D. The 'catalog entry' is irrelevant in this scenario; all updates should be made directly within the documentation repository.
The correct answer highlights the crucial role of the 'catalog entry'. Software catalogs aren't just lists of names; they're *living* records that should mirror the actual state of services. Updating the catalog entry ensures consistency – a change in API version needs to be reflected so developers know which documentation and configurations apply. Options A, C, and D misunderstand this fundamental purpose; a catalog update directly corresponds to an update in the service's documented details.
9 / 25
Sarah: "Hey team, I'm struggling to find the API documentation for the PaymentService. It's listed in the catalog, but the link is broken and I can't access it."
This scenario highlights the importance of understanding catalog entries beyond just their presence. While broken links are frustrating, Sarah's problem isn't necessarily with the catalog itself; it's likely a stale or incorrect reference within the catalog. The correct response is to investigate whether the documentation URL has been updated – this is a common issue requiring a quick check of the catalog entry details, not immediate escalation.
10 / 25
David: "I'm seeing a lot of entries in the software catalog that say 'In Development.' What does that actually *mean*? Should I be prioritizing these or treating them like fully deployed services?"
The term 'In Development' in a software catalog signifies more than just a stage of deployment. It's a status flag indicating the component is actively being tested, potentially undergoing significant changes, and is therefore considered unstable. Treating it with caution – prioritizing it appropriately – aligns with best practices when dealing with components marked as 'In Development,' preventing misinterpretations about their stability or readiness for production.
11 / 25
PR Description:
"Fix: Updated documentation for the AuthService. Added details on rate limiting and authentication flows. Also, updated the catalog entry to reflect the new API version (v2)."
Which of the following best describes the significance of updating the 'catalog entry' in this PR description?
A. It solely indicates a change in the API version being used.
B. It signifies that the documentation has been corrected, and the catalog record now accurately reflects the updated service state.
C. It's primarily a notification to the team about the new API version, with no impact on the software catalog itself.
D. The 'catalog entry' is irrelevant in this scenario; all updates should be made directly within the documentation repository.
The correct answer highlights the crucial role of the 'catalog entry'. Software catalogs aren't just lists of names; they're *living* records that should mirror the actual state of services. Updating the catalog entry ensures consistency – a change in API version needs to be reflected so developers know which documentation and configurations apply. Options A, C, and D misunderstand this fundamental purpose; a catalog update directly corresponds to an update in the service's documented details.
12 / 25
Sarah: "Hey team, I'm struggling to find the API documentation for the PaymentService. It's listed in the catalog, but the link is broken and I can't access it."
This scenario highlights the importance of understanding catalog entries beyond just their presence. While broken links are frustrating, Sarah's problem isn't necessarily with the catalog itself; it's likely a stale or incorrect reference within the catalog. The correct response is to investigate whether the documentation URL has been updated – this is a common issue requiring a quick check of the catalog entry details, not immediate escalation.
13 / 25
David: "I'm seeing a lot of entries in the software catalog that say 'In Development.' What does that actually *mean*? Should I be prioritizing these or treating them like fully deployed services?"
The term 'In Development' in a software catalog signifies more than just a stage of deployment. It's a status flag indicating the component is actively being tested, potentially undergoing significant changes, and is therefore considered unstable. Treating it with caution – prioritizing it appropriately – aligns with best practices when dealing with components marked as 'In Development,' preventing misinterpretations about their stability or readiness for production.
14 / 25
PR Description:
"Fix: Updated documentation for the AuthService. Added details on rate limiting and authentication flows. Also, updated the catalog entry to reflect the new API version (v2)."
Which of the following best describes the significance of updating the 'catalog entry' in this PR description?
A. It solely indicates a change in the API version being used.
B. It signifies that the documentation has been corrected, and the catalog record now accurately reflects the updated service state.
C. It's primarily a notification to the team about the new API version, with no impact on the software catalog itself.
D. The 'catalog entry' is irrelevant in this scenario; all updates should be made directly within the documentation repository.
The correct answer highlights the crucial role of the 'catalog entry'. Software catalogs aren't just lists of names; they're *living* records that should mirror the actual state of services. Updating the catalog entry ensures consistency – a change in API version needs to be reflected so developers know which documentation and configurations apply. Options A, C, and D misunderstand this fundamental purpose; a catalog update directly corresponds to an update in the service's documented details.
15 / 25
Sarah: "Hey team, I'm struggling to find the API documentation for the PaymentService. It's listed in the catalog, but the link is broken and I can't access it."
This scenario highlights the importance of understanding catalog entries beyond just their presence. While broken links are frustrating, Sarah's problem isn't necessarily with the catalog itself; it's likely a stale or incorrect reference within the catalog. The correct response is to investigate whether the documentation URL has been updated – this is a common issue requiring a quick check of the catalog entry details, not immediate escalation.
16 / 25
David: "I'm seeing a lot of entries in the software catalog that say 'In Development.' What does that actually *mean*? Should I be prioritizing these or treating them like fully deployed services?"
The term 'In Development' in a software catalog signifies more than just a stage of deployment. It's a status flag indicating the component is actively being tested, potentially undergoing significant changes, and is therefore considered unstable. Treating it with caution – prioritizing it appropriately – aligns with best practices when dealing with components marked as 'In Development,' preventing misinterpretations about their stability or readiness for production.
17 / 25
PR Description:
"Fix: Updated documentation for the AuthService. Added details on rate limiting and authentication flows. Also, updated the catalog entry to reflect the new API version (v2)."
Which of the following best describes the significance of updating the 'catalog entry' in this PR description?
A. It solely indicates a change in the API version being used.
B. It signifies that the documentation has been corrected, and the catalog record now accurately reflects the updated service state.
C. It's primarily a notification to the team about the new API version, with no impact on the software catalog itself.
D. The 'catalog entry' is irrelevant in this scenario; all updates should be made directly within the documentation repository.
The correct answer highlights the crucial role of the 'catalog entry'. Software catalogs aren't just lists of names; they're *living* records that should mirror the actual state of services. Updating the catalog entry ensures consistency – a change in API version needs to be reflected so developers know which documentation and configurations apply. Options A, C, and D misunderstand this fundamental purpose; a catalog update directly corresponds to an update in the service's documented details.
18 / 25
During a code review, Alice comments: 'This function doesn't have any documentation. It's listed as 'Uncategorized' in the software catalog.' What does 'Uncategorized' typically mean in this context?
'Uncategorized' in a software catalog usually indicates a component that hasn't yet been formally documented. It's a placeholder, highlighting the need to add metadata and documentation. Options A and D are incorrect as they relate to deprecated or internal components respectively; option C is also not accurate.
19 / 25
You're in a Slack channel discussing the status of a new feature. Ben says: 'I'm going to update the catalog entry for the UserProfile service to reflect the changes we made last week.' What is he primarily doing?
Ben is updating the *metadata* of the UserProfile service within the catalog. This involves modifying details like version numbers, dependencies, and potentially status flags – ensuring the catalog accurately reflects the current state of the component. Option A is incorrect as it refers to adding a new component; option D is unrelated.
20 / 25
During a standup meeting, Mark says: 'I've updated the catalog entry for the PaymentService to include details about the new API v2. I've also added a link to the updated documentation.' What is Mark communicating regarding his work?
Mark is updating the *metadata* of the PaymentService in the catalog. Specifically, he's adding details about the new API version (v2) and linking it to the updated documentation – both crucial pieces of information for other developers. Options A and D describe deployment actions; option B is a misinterpretation.
21 / 25
Alice is reviewing a pull request for the OrderProcessing service. The PR includes a change to the catalog entry stating: 'Status: Deprecated.' What does 'Deprecated' usually signify within the software catalog?
Hint: Consider what it means when a service is no longer actively maintained
'Deprecated' in a software catalog almost always indicates that a service is no longer actively supported or recommended for new development. It's often superseded by a newer alternative, so developers should avoid using it unless specifically required and aware of the risks. This contrasts with 'In Development,' which suggests ongoing activity.
22 / 25
During a Slack discussion about microservices, Chloe asks: 'I've created a new catalog entry for the UserAuthentication service. The description includes 'API Version: v1.' What is the primary purpose of this field in the software catalog?
The 'API Version' field in a software catalog is crucial for managing dependencies and ensuring that services are compatible. It allows developers to track which versions of an API are supported and avoid conflicts when integrating with other services. This is distinct from team ownership or infrastructure details.
23 / 25
In a standup meeting, David states: 'I've updated the catalog entry for the DataIngestion service to include a link to the Terraform configuration files.' What is David primarily communicating when he updates the catalog entry?
Updating the catalog entry with a link to Terraform configuration files provides valuable context regarding the infrastructure supporting the DataIngestion service. This allows other developers to quickly understand how it's deployed and potentially replicate or troubleshoot its environment – moving beyond just naming the service.
24 / 25
During a code review, Emily comments: 'This API endpoint is listed in the catalog as 'Beta.' What does the term 'Beta' typically signify regarding this service?
Consider the implications for stability and potential changes.
'Beta' in a software catalog indicates that the service is still under development and testing. It suggests users should expect potential instability, bugs, or changes before it's considered fully stable for production use. This contrasts with 'Production' which denotes a reliable, tested service.
25 / 25
You are reviewing a pull request that modifies the catalog entry for the ReportingService. The changes include: 'Tags: Analytics, Data Visualization.' What is the primary function of these 'Tags' within the software catalog?
Tags are used within a software catalog to categorize and organize services by their function or purpose (e.g., 'Analytics', 'Data Visualization'). This allows developers to quickly find relevant services based on their needs and improves overall discoverability within the system—a fundamental organizational tool.
What does the "Software Catalog Vocabulary" exercise cover?
Practice English vocabulary for software catalogs: catalog entries, ownership, service dependency graphs, catalog completeness, orphan components, and finding the owning team.
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 "Software Catalog Vocabulary"?
This exercise has 25 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.