What is a common approach to managing state in a Backstage plugin?

Storing state in the plugin's README

Using a global variable in the browser

A company uses the SonarQube plugin to display code quality metrics. They need to support multiple SonarQube instances (e.g., dev, staging, prod) and allow users to switch between them. The plugin currently only supports a single instance configured in app-config.yaml. What is the best way to achieve this?

Create multiple instances of the plugin, each configured for a different SonarQube instance.

Use environment variables to switch the SonarQube instance at build time.

Use the plugin's API to dynamically change the instance based on user selection, storing the selection in the plugin's state.

Fork the SonarQube plugin and modify it to support multiple instances.

A company uses the Lighthouse plugin to run audits on their websites. They want to change the default timeout for audits from 60 seconds to 120 seconds. Where should they make this change?

In the catalog-info.yaml file, add a timeout annotation to the component.

In the app-config.yaml file, under the lighthouse section, set the timeout option.

In the plugin's package.json, update the timeout field.

In the plugin's source code, change the default timeout constant.

A team uses the GitHub Insights plugin to display repository statistics. They want to replace the default 'Contributors' card with a custom component that shows a different metric. They have already created a new React component. What is the correct way to integrate this custom component into the plugin?

Create a new plugin that duplicates the GitHub Insights functionality and replace the old one in the app.

Use the plugin's extension mechanism to override the 'Contributors' card with the custom component.

Replace the plugin's API client to return data in a format that the default component can display.

Modify the plugin's source code in node_modules to import and render the new component.

A new developer is joining a team that maintains a Backstage app with several custom plugins. They need to understand how a plugin is structured to contribute effectively. Which statement best describes the structure of a Backstage plugin?

A plugin is a single file containing all frontend and backend logic.

A plugin consists of frontend components, backend APIs, and configuration schemas.

A plugin is a collection of static assets that are loaded at runtime.

A plugin is a standalone application that runs independently of the Backstage app.

Certified Backstage Associate (CBA)

Domain 4Objective 2

Customizing Backstage Plugins CBA Practice Questions (Page 3)

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

32questions here

7free pages

8concepts

32%of the exam

Questions 11–15

11foundation · easy
What is a common approach to managing state in a Backstage plugin?
Select an answer first
12expert · hard
A company uses the SonarQube plugin to display code quality metrics. They need to support multiple SonarQube instances (e.g., dev, staging, prod) and allow users to switch between them. The plugin currently only supports a single instance configured in app-config.yaml. What is the best way to achieve this?
Select an answer first
13application · medium
A company uses the Lighthouse plugin to run audits on their websites. They want to change the default timeout for audits from 60 seconds to 120 seconds. Where should they make this change?
Select an answer first
14application · medium
A team uses the GitHub Insights plugin to display repository statistics. They want to replace the default 'Contributors' card with a custom component that shows a different metric. They have already created a new React component. What is the correct way to integrate this custom component into the plugin?
Select an answer first
15application · medium
A new developer is joining a team that maintains a Backstage app with several custom plugins. They need to understand how a plugin is structured to contribute effectively. Which statement best describes the structure of a Backstage plugin?
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.

Customizing Backstage Plugins CBA Practice Questions (Page 3)

Questions 11–15

What is a common approach to managing state in a Backstage plugin?

A company uses the Lighthouse plugin to run audits on their websites. They want to change the default timeout for audits from 60 seconds to 120 seconds. Where should they make this change?

A new developer is joining a team that maintains a Backstage app with several custom plugins. They need to understand how a plugin is structured to contribute effectively. Which statement best describes the structure of a Backstage plugin?

Keep studying — Customizing Backstage