5 exercises — practice the vocabulary for developer portal governance, entity ownership, catalog completeness, and metadata SLAs.
0 / 22 completed
1 / 22
Your platform team reports: "Twelve catalog entries have no owner — they are stale entries."
What is a stale entry in a developer portal?
A stale entry is a catalog record that has decayed — the owning team may have disbanded, the service may have been decommissioned, or the metadata was never kept up to date. Stale entries reduce catalog trustworthiness. Governance processes typically include a stale entry SLA (e.g., "entries not verified in 90 days trigger an owner notification").
2 / 22
A platform engineer says: "Our catalog completeness score is 64%."
What does this metric measure?
A catalog completeness score measures data quality — how many entries have all required fields filled in. A score of 64% means 36% of entries are missing at least one mandatory field. Platform teams use this metric to drive governance campaigns: "All components must have an owner, lifecycle, and docs link by Q3."
3 / 22
Complete the platform governance SLA statement:
"Any service registered in the catalog must have a designated _____ — a team or individual who is accountable for keeping the metadata accurate and responding to dependency questions."
Owner is the standard term in developer portals and software catalogs. In Backstage, spec.owner references a Group or User entity. Entity ownership is the foundation of portal governance — without it, there is no accountability for accuracy, incident response, or decommissioning decisions.
4 / 22
A portal governance policy states: "All catalog entries must meet the metadata SLA within 30 days of registration."
What does SLA for portal metadata typically include?
A metadata SLA defines the quality and freshness standards for catalog entries. It typically specifies: required fields (owner, lifecycle, system), optional fields (tags, links), and a time window for compliance after registration. Platform teams use automated scoring and reminders to enforce it. The SLA turns the catalog from a snapshot into a living record.
5 / 22
Which statement best describes portal governance in the context of an internal developer portal?
Portal governance is the operational discipline of keeping the developer portal trustworthy and useful over time. Without governance, catalogs decay: orphaned entries accumulate, metadata becomes stale, and developers stop trusting the portal. Good governance includes completeness scoring, stale entry detection, ownership validation, and regular review cycles.
6 / 22
Sarah from the API team just posted this message in Slack: "I'm seeing a lot of requests hitting our /users/{userId} endpoint that are returning 404 errors. The documentation clearly states this endpoint should always be available, and we haven't made any recent changes to the underlying service."
This scenario highlights a common troubleshooting approach within developer portals. While documentation errors can occur, the initial response should focus on potential client-side issues – incorrect configurations are far more frequent than infrastructure problems in this context. Escalating directly to infrastructure without investigating the client is premature and inefficient; Sarah's role as an API consumer makes her best positioned to initially investigate these types of issues. The option about traffic overload is possible, but less likely given the clear documentation reference.
7 / 22
PR Description:
"Fix: Added endpoint for user profile retrieval. This resolves issue #1234 where users were intermittently unable to access their profiles. The API documentation has been updated to reflect this new endpoint."
During a code review, your teammate asks: 'Can you elaborate on the governance implications of adding this new endpoint? Specifically, how does it impact our catalog management?'
This question assesses understanding of how new APIs impact portal governance. Simply adding a new endpoint isn't enough; it necessitates updating metadata in the developer portal (like API documentation) to ensure consistency and traceability. The correct answer highlights that this update is vital for maintainability and aligns with broader catalog management practices, preventing stale information or misinterpretations.
8 / 22
DevOps Team is reviewing a recent PR that added a new API endpoint for retrieving user profiles. During the review, a senior engineer asks: 'Given this endpoint's inclusion in the catalog, what are the key governance considerations we need to address?'
Which of the following best describes those considerations?
The correct answer highlights the importance of metadata management within the developer portal catalog. A common misconception is that governance solely focuses on technical performance or security. However, the catalog acts as a central source of truth about an API endpoint – its purpose, who's responsible for it, and how it interacts with other services. Maintaining accurate metadata ensures accountability, facilitates dependency tracking, and allows the platform team to manage changes effectively. Options A and B focus on technical aspects that are secondary to governance; option C directly addresses the core concept of catalog governance, while option D is a misdirection focusing solely on security.
9 / 22
Sarah from the API team just posted this message in Slack: "I'm seeing a lot of requests hitting our /users/{userId} endpoint that are returning 404 errors. The documentation clearly states this endpoint should always be available, and we haven't made any recent changes to the underlying service."
This scenario highlights a common troubleshooting approach within developer portals. While documentation errors can occur, the initial response should focus on potential client-side issues – incorrect configurations are far more frequent than infrastructure problems in this context. Escalating directly to infrastructure without investigating the client is premature and inefficient; Sarah's role as an API consumer makes her best positioned to initially investigate these types of issues. The option about traffic overload is possible, but less likely given the clear documentation reference.
10 / 22
PR Description:
"Fix: Added endpoint for user profile retrieval. This resolves issue #1234 where users were intermittently unable to access their profiles. The API documentation has been updated to reflect this new endpoint."
During a code review, your teammate asks: 'Can you elaborate on the governance implications of adding this new endpoint? Specifically, how does it impact our catalog management?'
This question assesses understanding of how new APIs impact portal governance. Simply adding a new endpoint isn't enough; it necessitates updating metadata in the developer portal (like API documentation) to ensure consistency and traceability. The correct answer highlights that this update is vital for maintainability and aligns with broader catalog management practices, preventing stale information or misinterpretations.
11 / 22
DevOps Team is reviewing a recent PR that added a new API endpoint for retrieving user profiles. During the review, a senior engineer asks: 'Given this endpoint's inclusion in the catalog, what are the key governance considerations we need to address?'
Which of the following best describes those considerations?
The correct answer highlights the importance of metadata management within the developer portal catalog. A common misconception is that governance solely focuses on technical performance or security. However, the catalog acts as a central source of truth about an API endpoint – its purpose, who's responsible for it, and how it interacts with other services. Maintaining accurate metadata ensures accountability, facilitates dependency tracking, and allows the platform team to manage changes effectively. Options A and B focus on technical aspects that are secondary to governance; option C directly addresses the core concept of catalog governance, while option D is a misdirection focusing solely on security.
12 / 22
Sarah from the API team just posted this message in Slack: "I'm seeing a lot of requests hitting our /users/{userId} endpoint that are returning 404 errors. The documentation clearly states this endpoint should always be available, and we haven't made any recent changes to the underlying service."
This scenario highlights a common troubleshooting approach within developer portals. While documentation errors can occur, the initial response should focus on potential client-side issues – incorrect configurations are far more frequent than infrastructure problems in this context. Escalating directly to infrastructure without investigating the client is premature and inefficient; Sarah's role as an API consumer makes her best positioned to initially investigate these types of issues. The option about traffic overload is possible, but less likely given the clear documentation reference.
13 / 22
PR Description:
"Fix: Added endpoint for user profile retrieval. This resolves issue #1234 where users were intermittently unable to access their profiles. The API documentation has been updated to reflect this new endpoint."
During a code review, your teammate asks: 'Can you elaborate on the governance implications of adding this new endpoint? Specifically, how does it impact our catalog management?'
This question assesses understanding of how new APIs impact portal governance. Simply adding a new endpoint isn't enough; it necessitates updating metadata in the developer portal (like API documentation) to ensure consistency and traceability. The correct answer highlights that this update is vital for maintainability and aligns with broader catalog management practices, preventing stale information or misinterpretations.
14 / 22
DevOps Team is reviewing a recent PR that added a new API endpoint for retrieving user profiles. During the review, a senior engineer asks: 'Given this endpoint's inclusion in the catalog, what are the key governance considerations we need to address?'
Which of the following best describes those considerations?
The correct answer highlights the importance of metadata management within the developer portal catalog. A common misconception is that governance solely focuses on technical performance or security. However, the catalog acts as a central source of truth about an API endpoint – its purpose, who's responsible for it, and how it interacts with other services. Maintaining accurate metadata ensures accountability, facilitates dependency tracking, and allows the platform team to manage changes effectively. Options A and B focus on technical aspects that are secondary to governance; option C directly addresses the core concept of catalog governance, while option D is a misdirection focusing solely on security.
15 / 22
Sarah from the API team just posted this message in Slack: "I'm seeing a lot of requests hitting our /users/{userId} endpoint that are returning 404 errors. The documentation clearly states this endpoint should always be available, and we haven't made any recent changes to the underlying service."
This scenario highlights a common troubleshooting approach within developer portals. While documentation errors can occur, the initial response should focus on potential client-side issues – incorrect configurations are far more frequent than infrastructure problems in this context. Escalating directly to infrastructure without investigating the client is premature and inefficient; Sarah's role as an API consumer makes her best positioned to initially investigate these types of issues. The option about traffic overload is possible, but less likely given the clear documentation reference.
16 / 22
PR Description:
"Fix: Added endpoint for user profile retrieval. This resolves issue #1234 where users were intermittently unable to access their profiles. The API documentation has been updated to reflect this new endpoint."
During a code review, your teammate asks: 'Can you elaborate on the governance implications of adding this new endpoint? Specifically, how does it impact our catalog management?'
This question assesses understanding of how new APIs impact portal governance. Simply adding a new endpoint isn't enough; it necessitates updating metadata in the developer portal (like API documentation) to ensure consistency and traceability. The correct answer highlights that this update is vital for maintainability and aligns with broader catalog management practices, preventing stale information or misinterpretations.
17 / 22
DevOps Team is reviewing a recent PR that added a new API endpoint for retrieving user profiles. During the review, a senior engineer asks: 'Given this endpoint's inclusion in the catalog, what are the key governance considerations we need to address?'
Which of the following best describes those considerations?
The correct answer highlights the importance of metadata management within the developer portal catalog. A common misconception is that governance solely focuses on technical performance or security. However, the catalog acts as a central source of truth about an API endpoint – its purpose, who's responsible for it, and how it interacts with other services. Maintaining accurate metadata ensures accountability, facilitates dependency tracking, and allows the platform team to manage changes effectively. Options A and B focus on technical aspects that are secondary to governance; option C directly addresses the core concept of catalog governance, while option D is a misdirection focusing solely on security.
18 / 22
During a code review, John comments on a PR with the following text: 'This endpoint doesn't have an SLA defined. We need to add one to ensure ongoing maintenance and documentation alignment.' What does John likely mean in this context?
John is referring to Service Level Agreements (SLAs), a key component of portal governance. An SLA for an API defines the expected level of service – in this case, metadata maintenance – and ensures ongoing accountability. The incorrect options address security or localization, not the core concept of documented standards and upkeep.
19 / 22
Maria from the infrastructure team sends this message in a Slack channel: 'I'm noticing a significant increase in API calls to the /billing/transactions endpoint. We need to investigate if there's a potential governance issue – are we properly tracking usage and ensuring it aligns with our documented SLAs?' What is Maria primarily concerned about?
Maria's message highlights the importance of operational governance. The core issue isn't technical performance (option 3) or a vulnerability (option 1), but rather whether the endpoint is being monitored and managed according to established policies – specifically SLAs – which are central to portal governance. Monitoring helps ensure compliance.
20 / 22
Reviewing a PR description:
'This change introduces a new API endpoint for retrieving customer order details. The documentation has been updated to reflect the changes and the endpoint is now included in the catalog with version 2.0. We've established an SLA requiring weekly checks of the endpoint's performance metrics.' What is the primary purpose of including the 'SLA requirement' in this PR description?
The SLA isn't about uptime (option 1) or documentation updates (option 2). It's a critical element of governance – a defined metric for measuring the API's health and performance. This allows the team to proactively identify and address potential issues before they impact users.
21 / 22
During a daily stand-up update, David says: 'I've added a new API endpoint for retrieving user profile data. I've updated the documentation and have started tracking key metrics to ensure we meet our SLAs.' What is David primarily focusing on in this statement?
David's statement directly addresses the concept of SLAs. Tracking metrics is a key activity within a governance framework – it's how you demonstrate that an API is being managed according to its defined standards and obligations. This confirms David understands his role in upholding portal governance.
22 / 22
A developer discovers a new API endpoint has been added to the portal without any associated metadata or SLA definition. What is the *most* appropriate action for them to take?
The core principle of portal governance dictates that all catalog entries must have defined SLAs. This proactive step ensures accountability and compliance, preventing potential issues related to undocumented or poorly managed APIs – this action is vital for maintaining a well-governed developer portal.
What does the "Portal Governance Vocabulary — Developer Portal English Exercise" exercise cover?
Practice English vocabulary for developer portal governance: entity ownership, catalog completeness scores, stale entries, and metadata SLAs. 5 exercises.
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 "Portal Governance Vocabulary — Developer Portal English Exercise"?
This exercise has 22 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.