A development team wants to ensure that every service in their Backstage catalog has up-to-date documentation that is versioned with the code. They also want the documentation to be searchable within the Backstage portal. Which setup should they use?

Store documentation as Markdown files in a central documentation repository.

Add documentation as a custom field in the Software Catalog.

Use an external wiki and link to it from the catalog entries.

Enable TechDocs for each service and store documentation in the same repository as the code.

A developer wants to quickly find the owner and documentation for a specific service they are working on. They know the service name but not its location in the catalog. What is the most efficient way to find this information in Backstage?

Use the Scaffolder to create a new service with the same name.

Ask a colleague who might know the service.

Browse through the entire catalog manually.

Use the Backstage search bar to search for the service name.

How does the Software Catalog typically ingest information about software components?

By scanning the network for running services and automatically inferring their metadata.

By requiring users to manually enter all component information through a web form.

By connecting to a central database that is maintained by the platform team.

By reading catalog-info.yaml files that are stored in source code repositories.

A company wants to restrict access to a Backstage plugin that displays sensitive deployment information. Only members of the 'platform-eng' group should be able to view it. They already use an OIDC provider for authentication. What should they configure?

Rely on the OIDC provider to restrict access to the plugin.

Set the plugin's visibility to 'private' in the app config.

Hide the plugin from the sidebar for non-members.

Use Backstage's authorization framework to define a permission policy that checks group membership.

Certified Backstage Associate (CBA)

Domain 2Objective 1

Understand the Backstage Framework CBA Practice Questions (Page 6)

Part of the Backstage Infrastructure 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 2–3 from this objective — we provide 37 practice questions to prepare you well beyond it. (estimate)

37questions here

8free pages

9concepts

22%of the exam

Questions 26–30

26foundation · easy
What is the primary configuration file used to customize a Backstage application?
Select an answer first
27application · medium
A development team wants to ensure that every service in their Backstage catalog has up-to-date documentation that is versioned with the code. They also want the documentation to be searchable within the Backstage portal. Which setup should they use?
Select an answer first
28application · medium
A developer wants to quickly find the owner and documentation for a specific service they are working on. They know the service name but not its location in the catalog. What is the most efficient way to find this information in Backstage?
Select an answer first
29foundation · easy
How does the Software Catalog typically ingest information about software components?
Select an answer first
30application · medium
A company wants to restrict access to a Backstage plugin that displays sensitive deployment information. Only members of the 'platform-eng' group should be able to view it. They already use an OIDC provider for authentication. 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.