A new engineer wants to know which team maintains the 'order-service' and whether it is production-ready. Where in the catalog entity page should they look?

Read the 'description' field for maintenance notes.

Check the 'tags' field for 'production' and 'team'.

Check the 'owner' field and the 'lifecycle' field in the entity's metadata.

Look at the 'system' field to see which system it belongs to.

A team has a monorepo containing multiple services, each with its own catalog-info.yaml. They want to register all services without registering each file individually. What is the most efficient method?

Use a script to generate a combined YAML file and register that.

Register the root directory as a location and use a wildcard pattern to match all catalog-info.yaml files.

Register each catalog-info.yaml file individually in the UI.

Create a single catalog-info.yaml that defines all services in one file.

A platform team wants to reduce the time developers spend searching for internal services and their APIs. They plan to adopt Backstage. Which approach best leverages the Backstage Catalog to meet this goal?

Create a single System entity that lists all services in its description field.

Store all service documentation in a shared wiki and add a link to Backstage's homepage.

Register all services as Component entities with metadata YAML files, and link each to its owning team and API entities.

Use Backstage only for CI/CD pipelines and ignore catalog features.

How are catalog entities typically defined in Backstage?

Through JSON configuration files in the Backstage app directory

Through database entries created by administrators

Through a graphical drag-and-drop interface in the Backstage UI

Through metadata YAML files stored in source control

An architect wants to identify which services are in 'deprecated' lifecycle and who owns them, to plan decommissioning. What is the most efficient way in the catalog?

Use the catalog's graph view to find deprecated entities.

Browse all components and look for 'deprecated' in their descriptions.

Search for 'deprecated' in the search bar and read all results.

Filter by lifecycle 'deprecated' and view the owner field for each result.

Certified Backstage Associate (CBA)

Domain 3Objective 1

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

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 6–10

6application · medium
A new engineer wants to know which team maintains the 'order-service' and whether it is production-ready. Where in the catalog entity page should they look?
Select an answer first
7expert · hard
A team has a monorepo containing multiple services, each with its own catalog-info.yaml. They want to register all services without registering each file individually. What is the most efficient method?
Select an answer first
8application · medium
A platform team wants to reduce the time developers spend searching for internal services and their APIs. They plan to adopt Backstage. Which approach best leverages the Backstage Catalog to meet this goal?
Select an answer first
9foundation · easy
How are catalog entities typically defined in Backstage?
Select an answer first
10application · medium
An architect wants to identify which services are in 'deprecated' lifecycle and who owns them, to plan decommissioning. What is the most efficient way in the catalog?
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.