
CBA (Certified Backstage Associate) is the Linux Foundation and CNCF certification for Backstage, the open-source framework for building internal developer portals, created at Spotify. Platform engineering teams use Backstage to give developers one place for the software catalog, documentation, templates that create new services, and plugins for CI, Kubernetes and cloud. The exam is multiple choice but practical: about a third covers customising Backstage with plugins and React code, so you need to have built and run a Backstage app yourself.
This guide follows the official Linux Foundation exam page: the four domains with weights, Backstage's architecture and catalog files, the commands you'll use, a 4-week plan and 15 original practice questions.
Quick facts (Linux Foundation, November 2026)
| Item | Detail |
|---|---|
| Format | Online, proctored, multiple choice |
| Duration | 90 minutes |
| Level | Beginner; no prerequisites listed |
| Price | US$250 exam only; US$495 with an annual training subscription |
| Validity | 2 years |
| Eligibility | 12 months to schedule and take the exam; a retake is included |
Read the official CBA exam page and the Backstage documentation.
Domains and weights
| Domain | Weight | Objectives (from the Linux Foundation) |
|---|---|---|
| Customizing Backstage | 32% | Frontend vs backend plugins; customising plugins; changing React code in the Backstage app; Material UI components |
| Backstage Development Workflow | 24% | Build and run projects locally; local development workflow; compile with TypeScript; install dependencies with npm/Yarn; build a container image with Docker |
| Backstage Infrastructure | 22% | The framework; configuration; deploying to production; client-server architecture |
| Backstage Catalog | 22% | Why and how to use the catalog; populating it; annotations; manually registered locations; troubleshooting ingestion; automated ingestion |
How Backstage is built
- Monorepo:
packages/appis the React frontend;packages/backendis the Node.js backend; plugins live underplugins/. - Configuration:
app-config.yaml, overridden byapp-config.production.yamland environment variables (for example${GITHUB_TOKEN}). Secrets come from the environment, never the file. - Client-server: the frontend calls backend plugin APIs; the backend talks to the database (SQLite for local development, PostgreSQL in production) and to external systems.
- Core features: Software Catalog, Software Templates (scaffolder), TechDocs (docs-as-code), Search, and Kubernetes and CI plugins.
A catalog entity
# catalog-info.yaml in the service's repository
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
name: payments-api
description: Payments REST API
annotations:
github.com/project-slug: example/payments-api
backstage.io/techdocs-ref: dir:.
backstage.io/kubernetes-id: payments-api
spec:
type: service
lifecycle: production
owner: team-payments
system: checkout
providesApis: [payments-v1]
Know the main kinds: Component, API, Resource, System, Domain, Group, User, Template and Location. Entities enter the catalog by manual registration (a Location pointing at the file) or automated ingestion (entity providers that discover catalog-info.yaml files across an organisation). Annotations connect an entity to plugins.
Commands to know
npx @backstage/create-app@latest # scaffold a new app
yarn install # install dependencies
yarn start # run frontend and backend locally (older apps: yarn dev)
yarn tsc # type-check the project
yarn build:backend # build the backend bundle
docker image build . -f packages/backend/Dockerfile --tag backstage
yarn new # create a new plugin or package
Command names change between Backstage releases, so check the version of the docs that matches your app.
4-week study plan
| Week | Focus | Lab |
|---|---|---|
| 1 | Create an app, local workflow, TypeScript, Yarn, project structure, app-config | Create and run an app; change the title and an integration in app-config |
| 2 | Catalog: entity kinds, annotations, registration, automated discovery, troubleshooting ingestion | Register 3 components, a group and an API; break one YAML and find the error |
| 3 | Plugins: frontend vs backend, installing and customising, React and Material UI changes | Add the Kubernetes or GitHub Actions plugin; add a custom card to the entity page |
| 4 | Production: PostgreSQL, Docker image, auth, configuration by environment; review | Build the Docker image and run it against PostgreSQL; book the exam |
15 practice questions with answers
These are original questions written for this guide, not exam questions.
1. What is Backstage?
An open-source framework for building internal developer portals, created at Spotify and hosted by the CNCF.
2. Which file describes a service for the catalog?
catalog-info.yaml.
3. Which entity kind represents a team?
Group.
4. Which kind groups related components and APIs into a product?
System (and Systems group into Domains).
5. How does a component link to its GitHub repository for plugins?
Through an annotation such as github.com/project-slug.
6. A newly registered entity doesn't appear in the catalog. Where do you look first?
The backend logs and the location's processing errors, usually YAML or schema mistakes.
7. What is the difference between manual registration and automated ingestion?
Manual registration adds one Location by hand; automated ingestion uses entity providers to discover entity files across an organisation.
8. Which database is recommended for production?
PostgreSQL (SQLite is for local development).
9. Where should a GitHub token used by Backstage be stored?
In an environment variable referenced from app-config, not in the file itself.
10. Which feature creates a new repository from a template with a form?
Software Templates (the scaffolder).
11. Which feature renders Markdown documentation stored next to the code?
TechDocs.
12. A plugin needs to call a third-party API with a secret key. Frontend or backend plugin?
Backend plugin, so the secret never reaches the browser.
13. Which UI component library does the Backstage frontend use?
Material UI (MUI).
14. Which language and type checker does Backstage use?
TypeScript, checked with tsc.
15. Which config file overrides settings for production?
app-config.production.yaml (plus environment variables).
After CBA
- Complete the platform engineering set with CGOA, Argo CAPA and CKAD.
- Learn platform tooling in our DevOps course and Kubernetes course.
- See live platform and DevOps jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches DevOps, platform engineering and full-stack development with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is the CBA exam?
The Linux Foundation and CNCF Certified Backstage Associate: an online, proctored, multiple-choice exam on building and running Backstage developer portals.
How long is the CBA exam?
90 minutes.
Which CBA domain has the most weight?
Customizing Backstage at 32%.
What is Backstage?
An open-source framework for internal developer portals, created at Spotify and hosted by the CNCF.
Which file adds a service to the Backstage catalog?
catalog-info.yaml in the service's repository.
How long is CBA valid?
2 years.



