All Practice Exams

100+ Free Certified Backstage Associate Practice Questions

Certified Backstage Associate (CBA) practice questions are available now; exam metadata is being verified.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately
100+ Questions
100% Free
1 / 100
Question 1
Score: 0/0

Which database does the default create-app backend use for quick local development, and which is recommended for production?

A
B
C
D
to track
2026 Statistics

Key Facts: Certified Backstage Associate Exam

$250

Exam Fee (USD)

The Linux Foundation

90 minutes

Exam Duration

The Linux Foundation

32% / 24% / 22% / 22%

Domain Weights (Customizing / Workflow / Infrastructure / Catalog)

The Linux Foundation CBA curriculum

2 years

Certification Validity

The Linux Foundation

2 attempts

Included Attempts (one retake)

The Linux Foundation

Nov 2024

Certification Launch

The Linux Foundation / CNCF

The Certified Backstage Associate (CBA) is a $250, 90-minute, online proctored, multiple-choice exam from The Linux Foundation and CNCF, valid for two years. It covers four domains: Customizing Backstage (32%), Backstage Development Workflow (24%), Backstage Infrastructure (22%), and Backstage Catalog (22%). Registration includes two attempts within a 12-month window. The Linux Foundation does not officially publish the exact question count or the passing score.

Sample Certified Backstage Associate Practice Questions

Try these sample questions to test your Certified Backstage Associate exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1In Backstage, what is the primary architectural difference between a frontend plugin and a backend plugin?
A.Frontend plugins render React UI components in the app, while backend plugins run on the Node.js server and expose HTTP routes and business logic
B.Frontend plugins are written in Go, while backend plugins are written in TypeScript
C.Frontend plugins handle database access, while backend plugins render the user interface
D.There is no difference; both run entirely in the browser
Explanation: Backstage is split into a frontend app (a React single-page application) and a backend (a Node.js service). Frontend plugins contribute React components, routes, and pages to the app; backend plugins run server-side, exposing HTTP endpoints, talking to databases, and integrating with external systems.
2Which UI component library does the default Backstage frontend use for styling and building its interface?
A.Bootstrap
B.Material UI (MUI)
C.Chakra UI
D.Ant Design
Explanation: Backstage's frontend is built on Material UI (MUI). Plugins and the core app use MUI components and the makeStyles/useStyles theming approach, so customizing Backstage UI typically means working with MUI components and the Backstage theme.
3In a standard Backstage monorepo created with create-app, where is the React code for the frontend application primarily located?
A.In the packages/backend directory
B.In the root app-config.yaml file
C.In the packages/app directory
D.In the plugins/catalog-backend directory
Explanation: The create-app scaffold produces a monorepo with packages/app holding the frontend React application and packages/backend holding the Node.js backend. To modify the app's React code, such as App.tsx and the routing, you edit files under packages/app.
4A developer wants to add a new page route to the Backstage frontend app so that visiting /my-plugin renders a plugin's page. Which file do they typically edit?
A.packages/app/public/index.html
B.packages/backend/src/index.ts
C.app-config.production.yaml
D.packages/app/src/App.tsx
Explanation: Frontend routing is defined in packages/app/src/App.tsx, where the <FlatRoutes> element lists <Route> entries mapping paths to plugin page elements. Adding a route means adding a <Route path="/my-plugin" element={<MyPluginPage />} /> there.
5What is the main purpose of the EntityPage in a Backstage frontend app?
A.It defines the layout, tabs, and cards shown on a catalog entity's detail page
B.It configures which databases the backend connects to
C.It registers backend plugins with the new backend system
D.It stores the YAML descriptor for each catalog entity
Explanation: The EntityPage (in packages/app/src/components/catalog/EntityPage.tsx) composes the entity detail view, choosing which tabs and cards appear for different entity kinds using <EntitySwitch> and <EntityLayout>. Customizing what users see on a Component, API, or System page means editing EntityPage.
6When customizing a Backstage frontend plugin's appearance, which Material UI mechanism is commonly used to apply scoped CSS styles to components?
A.Inline style attributes only
B.The makeStyles hook (or useStyles) provided by Material UI
C.A separate global styles.css file imported into index.html
D.Tailwind utility classes configured in tailwind.config.js
Explanation: Backstage uses Material UI's makeStyles hook to generate scoped class names and apply theme-aware styling within React components. A developer calls const useStyles = makeStyles(theme => ({...})) and then uses the returned classes in JSX.
7A team has built a custom backend plugin and wants it to run as part of the Backstage backend using the new backend system. What is the correct way to install it?
A.Add a route entry in packages/app/src/App.tsx
B.List the plugin under catalog.locations in app-config.yaml
C.Call backend.add(import('@internal/plugin-myplugin-backend')) in packages/backend/src/index.ts
D.Register it as an EntitySwitch case in EntityPage.tsx
Explanation: With the new backend system, plugins are installed by calling backend.add(import('...')) in packages/backend/src/index.ts after createBackend(). Plugins are standalone features; modules augment plugins, and services override behavior.
8In the Backstage new backend system, what is the difference between a plugin and a module?
A.There is no difference; the terms are interchangeable
B.A plugin only runs in the frontend, while a module only runs in the backend
C.A module is a standalone feature, while a plugin only adds configuration
D.A plugin is a standalone feature, while a module augments or extends an existing plugin
Explanation: In the new backend system, a plugin is a self-contained feature (such as the catalog or scaffolder), while a module extends an existing plugin, for example adding a new scaffolder action or catalog entity provider. Services provide shared capabilities that plugins and modules consume.
9Which component is used in EntityPage.tsx to conditionally render different content depending on the kind or type of the catalog entity being displayed?
A.<EntitySwitch>
B.<RouterProvider>
C.<ConfigReader>
D.<BackendFeature>
Explanation: <EntitySwitch> with nested <EntitySwitch.Case> elements lets the EntityPage render different layouts for different entity kinds or types, using filter functions like isKind('component') or isComponentType('service'). This is how a service Component page differs from a Website page.
10A developer installs a community frontend plugin via npm. After adding the dependency, what is generally required to make its page visible in the Backstage app?
A.Nothing; npm install alone makes the page appear automatically
B.Import the plugin's page component and add a <Route> for it in App.tsx (and often a sidebar item)
C.Add the plugin to app-config.yaml under backend.plugins
D.Recompile the backend with yarn build:backend only
Explanation: With the classic frontend system, installing a frontend plugin requires wiring it into the app: import its exported page component, add a <Route> in App.tsx, and typically add a sidebar link in Root.tsx. The dependency alone does not register the route.

About the Certified Backstage Associate Practice Questions

Verified exam format metadata for Certified Backstage Associate (CBA) is pending. The practice questions above remain available while official exam length, timing, passing score, fee, and administrator details are reviewed.