PracticeVideosBlogFlashcardsEspañol
All Practice Exams

100+ Free Certified Backstage Associate Practice Questions

Prepare for the Certified Backstage Associate (CBA) exam with instant access — no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately
100+ Questions
100% Free

Loading practice questions...

Same family resources

Explore More Linux Foundation Certifications

Continue into nearby exams from the same family. Each card keeps practice questions, study guides, flashcards, videos, and articles in one place.

Linux Foundation Certified System Administrator (LFCS)

Practice Questions

Besu Certified Professional (BCP)

Practice Questions

Certified Open Source Developer for Enterprise (CODE)

Practice Questions

Cilium Certified Associate (CCA)

Practice Questions

FCFP FINOS Certified FDC3 Practitioner

Practice Questions

FinOps Certified Engineer (FOCE)

Practice Questions
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 Exam

The Certified Backstage Associate (CBA) validates foundational, hands-on knowledge of Backstage, the open-source CNCF developer portal framework originally created at Spotify. The exam is a 90-minute, online, proctored, multiple-choice test covering four domains: Customizing Backstage (32%), Backstage Development Workflow (24%), Backstage Infrastructure (22%), and Backstage Catalog (22%). Candidates are expected to understand frontend versus backend plugins, the React app and Material UI, the create-app workflow with Yarn and TypeScript, app-config.yaml and the client-server architecture, and modeling software in the catalog with catalog-info.yaml entities and annotations. The credential launched in November 2024 and is valid for two years.

Assessment

Question count not published by the exam provider

Time Limit

90 minutes

Passing Score

Not officially published

Exam Fee

$250 (The Linux Foundation / CNCF)

Certified Backstage Associate Exam Content Outline

32%

Customizing Backstage

Distinguish frontend plugins (React UI in packages/app) from backend plugins (Node.js APIs in packages/backend), install and customize plugins, edit App.tsx routes, EntityPage tabs and EntitySwitch cards, the sidebar, and apply Material UI components and custom themes.

24%

Backstage Development Workflow

Scaffold an app with npx @backstage/create-app, run it locally with yarn dev on ports 3000 and 7007, manage the Yarn workspaces monorepo and package.json dependencies, type-check and build TypeScript, and produce Docker images with multi-stage builds.

22%

Backstage Infrastructure

Understand the client-server architecture, configure app-config.yaml including integrations (GitHub, GitLab), auth providers and sign-in resolvers, the proxy, app and backend baseUrls, secrets via environment variables, and deploy to production with PostgreSQL, the permission framework, Kubernetes plugin, Search, and TechDocs.

22%

Backstage Catalog

Explain the Software Catalog, write catalog-info.yaml with kind, metadata, and spec, model Component, API, Resource, System, Domain, Group, and User entities, apply annotations, register entities and catalog.locations, configure automated ingestion via entity providers, and troubleshoot processing errors.

How to Pass the Certified Backstage Associate Exam

What You Need to Know

  • Passing score: Not officially published
  • Assessment: Question count not published by the exam provider
  • Time limit: 90 minutes
  • Exam fee: $250

Keys to Passing

  • Work through all 100 available questions
  • Review every answer and explanation
  • Track weak areas and revisit them
  • Use our AI tutor for tough concepts

Certified Backstage Associate Study Tips from Top Performers

1Build a Backstage app locally with npx @backstage/create-app and run yarn dev; knowing the frontend (3000) and backend (7007) ports and the monorepo layout is heavily tested.
2Spend the most time on Customizing Backstage (32%): practice distinguishing frontend and backend plugins, editing App.tsx and EntityPage, using EntitySwitch, and styling with Material UI.
3Write several catalog-info.yaml files by hand, modeling Component, API, Resource, System, Group, and User entities, and learn the required apiVersion, kind, metadata, and spec fields.
4Memorize how entities are ingested: catalog.locations static config, the Register an existing component UI flow, and automated GitHub entity/discovery providers, plus how to read processing errors.
5Understand app-config.yaml end to end: integrations and tokens, auth providers and sign-in resolvers, backend.database, app and backend baseUrls, the proxy, and environment-variable secret substitution.
6Know the production story: Docker images, PostgreSQL for persistence and multiple replicas, the permission framework, the Kubernetes plugin with backstage.io/kubernetes-id, Search, and TechDocs with MkDocs.

Frequently Asked Questions

What are the current exam facts for the CBA?

The Certified Backstage Associate is a $250, 90-minute, online proctored, multiple-choice exam from The Linux Foundation and CNCF. It is valid for two years and registration includes two attempts within a 12-month eligibility window.

What does the CBA exam cover?

The CBA covers four domains: Customizing Backstage (32%), Backstage Development Workflow (24%), Backstage Infrastructure (22%), and Backstage Catalog (22%). Together they test plugins, the React app, the create-app workflow, app-config.yaml, and the software catalog.

Which CBA domain carries the most weight?

Customizing Backstage is the largest domain at 32%, covering frontend versus backend plugins, customizing plugins, modifying React code in the Backstage app, and using Material UI components.

What is the passing score for the CBA exam?

The Linux Foundation does not officially publish the CBA passing score or the exact number of questions. The exam is described simply as a 90-minute, online, proctored, multiple-choice test.

Do I need prior Backstage experience to take the CBA?

The CBA is positioned as a beginner-level associate exam with no formal prerequisites. Hands-on familiarity with running Backstage locally, editing catalog-info.yaml, and customizing plugins is strongly recommended.

How long is the CBA certification valid?

The Certified Backstage Associate certification is valid for two years from the date it is earned. The credential launched in November 2024.