What is the primary purpose of the catalog-info.yaml file in Backstage?

It contains the authentication credentials for external systems.

It specifies the UI layout of the Backstage software catalog.

It defines the metadata and relationships for entities that are registered in the Backstage catalog.

It stores the runtime configuration for Backstage plugins.

A Backstage administrator is troubleshooting a catalog registration failure. The location URL points to a catalog-info.yaml file in a private GitHub repository. The error message says 'unable to fetch the location'. The administrator has configured GitHub authentication. What is the most likely cause?

The GitHub token used by Backstage does not have read access to the repository.

The catalog-info.yaml file contains invalid YAML.

The catalog refresh interval is set too low.

How can custom processors extend the Backstage catalog?

By adding new entity kinds or modifying entity data during processing.

By changing the user interface theme of the catalog.

By storing entities in an external database.

By replacing the entire catalog backend with a custom implementation.

A Backstage administrator notices that a catalog-info.yaml file with an invalid 'spec.type' value is being rejected by the catalog. The administrator wants to allow additional valid values for 'spec.type' without modifying the core Backstage code. What should they do?

Create a custom processor that validates and accepts the additional 'spec.type' values.

Modify the catalog-info.yaml file to use a valid 'spec.type' value.

Use an entity provider to bypass validation for that specific file.

Disable the built-in validation processor for the catalog.

A company uses GitHub Enterprise for all its source code repositories. They want to automatically populate the Backstage catalog with all components defined in their repositories without manual registration. What should they configure?

A GitHub entity provider that scans configured repositories for catalog-info.yaml files.

A GitHub Actions workflow that pushes entity data to the Backstage catalog API.

A webhook from GitHub to Backstage that triggers registration of new repositories.

A custom location that points to each repository's catalog-info.yaml file.

Certified Backstage Associate (CBA)

Domain 3Objective 2

Populate Backstage Catalog CBA Practice Questions (Page 1)

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 25 practice questions to prepare you well beyond it. (estimate)

25questions here

5free pages

8concepts

22%of the exam

Questions 1–5

1foundation · easy
What is the primary purpose of the catalog-info.yaml file in Backstage?
Select an answer first
2expert · hard
A Backstage administrator is troubleshooting a catalog registration failure. The location URL points to a catalog-info.yaml file in a private GitHub repository. The error message says 'unable to fetch the location'. The administrator has configured GitHub authentication. What is the most likely cause?
Select an answer first
3foundation · easy
How can custom processors extend the Backstage catalog?
Select an answer first
4application · medium
A Backstage administrator notices that a catalog-info.yaml file with an invalid 'spec.type' value is being rejected by the catalog. The administrator wants to allow additional valid values for 'spec.type' without modifying the core Backstage code. What should they do?
Select an answer first
5application · medium
A company uses GitHub Enterprise for all its source code repositories. They want to automatically populate the Backstage catalog with all components defined in their repositories without manual registration. What should they configure?
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.