5 exercises — practice the vocabulary for developer portal governance, entity ownership, catalog completeness, and metadata SLAs.
0 / 5 completed
Core portal governance concepts
Entity ownership: Every catalog entry must have an accountable owner — a team or person who keeps it accurate.
Catalog completeness score: The percentage of entries with all required fields populated (owner, lifecycle, docs).
Stale entry: An entry not verified or updated within the defined governance window.
Metadata SLA: The policy that defines required fields and update frequency for all registered services.
1 / 5
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 / 5
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 / 5
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 / 5
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 / 5
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.