Why is state management important in a Backstage plugin?

To hide the plugin's data from other plugins

To make the plugin's code more complex

To prevent users from using the plugin

To ensure the plugin's data persists and the user experience is consistent

A developer is extending the Scaffolder plugin with a custom action that requires access to a secret stored in the Backstage backend. The action needs to run asynchronously and update the task status. What is the best way to implement this?

Implement the action on the frontend and use the Backstage API to read the secret.

Use a separate microservice to handle the action and call it from the Scaffolder.

Store the secret in the app-config.yaml and read it from the frontend.

Create a custom action that reads the secret from the backend environment and updates the task status using the Scaffolder API.

A team is customizing the Search plugin to include a custom filter that remembers the user's last selected filter value across sessions. What is the best way to persist this state?

Store the value in the plugin's internal state using React useState.

Store the value in the backend database using a custom API.

Use the Backstage storage API to save the value in the browser's local storage.

Encode the value in the URL query parameters.

What is the purpose of a plugin's public API in Backstage?

To store the plugin's configuration

To replace the Backstage core API

To allow other plugins or the app to interact with the plugin's capabilities

To hide the plugin's functionality from users

How can you extend a plugin's default behavior without altering its core code?

By changing the plugin's package version

By modifying the plugin's source code directly

By creating a fork of the plugin repository

By using the plugin's extension points or adding custom logic in your app

Certified Backstage Associate (CBA)

Domain 4Objective 2

Customizing Backstage Plugins CBA Practice Questions (Page 4)

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 16–20

16foundation · easy
Why is state management important in a Backstage plugin?
Select an answer first
17expert · hard
A developer is extending the Scaffolder plugin with a custom action that requires access to a secret stored in the Backstage backend. The action needs to run asynchronously and update the task status. What is the best way to implement this?
Select an answer first
18application · medium
A team is customizing the Search plugin to include a custom filter that remembers the user's last selected filter value across sessions. What is the best way to persist this state?
Select an answer first
19foundation · easy
What is the purpose of a plugin's public API in Backstage?
Select an answer first
20foundation · easy
How can you extend a plugin's default behavior without altering its core code?
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.