A developer wants to find all services that use a specific database and are owned by the 'data' team. The database is not registered as an entity in the catalog. What is the best approach?

Use the catalog's graph view to find all services connected to the database.

Register the database as a Resource entity and then use relations to find consuming services.

Ask the data team for a list of services using the database.

Search for the database name in the catalog and filter by owner 'data'.

A service is marked as 'deprecated' in its catalog-info.yaml, but the owning team is still actively developing it. The platform team wants to ensure the catalog reflects reality. What should they do?

Change the owner field to a new team that is actively developing it.

Update the lifecycle field in the catalog-info.yaml to 'production' and let the catalog processor refresh the entity.

Use the Backstage UI to edit the lifecycle field directly.

Delete the entity from the catalog and re-register it with the correct lifecycle.

A developer wants to scaffold a new microservice using an approved template and then find the API documentation for an existing service. How can Backstage support both tasks?

Use the TechDocs plugin to create the service and then search for the API.

Use the Software Templates to create the service, then search the catalog for the existing service and open its API docs.

Open the existing service's entity page and click 'Create similar'.

Use the catalog search to find a template, then manually create the service in the UI.

What is the primary way to locate a specific software component in the Backstage Catalog?

Using the search bar and filtering by entity type, tags, or lifecycle

Querying the underlying database directly

Browsing through all entities in alphabetical order only

Using a command-line interface to grep the catalog files

What is the primary purpose of the Backstage Catalog in a developer portal?

To store and manage infrastructure secrets and credentials

To provide a central hub for discovering and managing software components and services

To replace version control systems like GitHub and GitLab

To execute CI/CD pipelines for all registered services

Certified Backstage Associate (CBA)

Domain 3Objective 1

Understand How/why to Use Backstage Catalog CBA Practice Questions (Page 6)

Part of the Backstage Catalog domain, which accounts for 22% of the CBA exam. Linux Foundation does not publish an official question count, but from its 90-minute exam (~35–60 total, ~8–13 in this domain), expect 1–2 from this objective — we provide 32 practice questions to prepare you well beyond it. (estimate)

32questions here

7free pages

7concepts

22%of the exam

Questions 26–30

26expert · hard
A developer wants to find all services that use a specific database and are owned by the 'data' team. The database is not registered as an entity in the catalog. What is the best approach?
Select an answer first
27expert · hard
A service is marked as 'deprecated' in its catalog-info.yaml, but the owning team is still actively developing it. The platform team wants to ensure the catalog reflects reality. What should they do?
Select an answer first
28application · medium
A developer wants to scaffold a new microservice using an approved template and then find the API documentation for an existing service. How can Backstage support both tasks?
Select an answer first
29foundation · easy
What is the primary way to locate a specific software component in the Backstage Catalog?
Select an answer first
30foundation · easy
What is the primary purpose of the Backstage Catalog in a developer portal?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CBA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Linux Foundation. “CBA” is a trademark of its owner, used for identification only.