Skip to content

CBA - Certified Backstage Associate

Multiple-choice exam | 90 minutes | Passing score: 66% | $250 USD | Launched 2025

The CBA (Certified Backstage Associate) validates your understanding of Backstage, the CNCF-incubating Internal Developer Portal created by Spotify. Unlike the Kubernetes certifications, CBA is not a hands-on exam — it’s multiple-choice. But don’t be fooled: it tests real development knowledge. You need to understand TypeScript, React, plugin architecture, catalog YAML, and production deployment — not just theory.

KubeDojo covers ~90% of CBA topics through our existing Backstage toolkit module, Platform Engineering discipline, and three dedicated CBA modules covering development workflows, plugin development, and catalog/infrastructure.

Key difference from other CNCF certs: CBA is a developer certification. It tests whether you can build and extend Backstage, not just use it. Think of it as “CKAD for developer portals.”


These modules cover the areas between KubeDojo’s existing Backstage toolkit module and the CBA exam requirements:

#ModuleTopicDomains Covered
1Backstage Developer WorkflowMonorepo structure, TypeScript essentials, Docker builds, app-config, CLIDomain 1 (24%)
2Backstage Plugin DevelopmentFrontend/backend plugins, React/MUI, scaffolder actions, themes, APIsDomain 4 (32%)
3Backstage Catalog & InfrastructureEntity processors, providers, annotations, auth, deployment, troubleshootingDomains 2-3 (44%)

DetailValue
CertificationCertified Backstage Associate (CBA)
Issued byThe Linux Foundation / CNCF
FormatMultiple-choice
Duration90 minutes
Questions~60
Passing score66%
Cost$250 USD (includes one free retake)
Validity3 years
PrerequisitesNone (but TypeScript/React experience strongly recommended)
ProctoringOnline proctored via PSI

DomainWeightKubeDojo Coverage
Customizing Backstage32%Excellent (Plugin Development — React/MUI, plugins, themes, scaffolder)
Backstage Development Workflow24%Excellent (Developer Workflow — monorepo, TypeScript, Docker, CLI)
Backstage Infrastructure22%Excellent (Catalog & Infrastructure — auth, deployment, production)
Backstage Catalog22%Excellent (Catalog & Infrastructure — processors, providers, annotations)

Domain 1: Backstage Development Workflow (24%)

Section titled “Domain 1: Backstage Development Workflow (24%)”
  • Creating and running a Backstage app locally
  • TypeScript fundamentals for Backstage development
  • Monorepo structure (packages/app, packages/backend)
  • Docker builds for Backstage
  • yarn commands and workspace management
  • Development vs production configuration

Existing coverage:

ModuleTopicRelevance
Backstage 7.1Installation, npx @backstage/create-app, yarn devPartial — covers basic setup only

Dedicated CBA module:

ModuleTopicRelevance
Backstage Developer WorkflowMonorepo structure, TypeScript essentials, Docker builds, app-config overlays, CLI commandsDirect

  • Backstage framework architecture (frontend/backend separation)
  • Configuration system (app-config.yaml hierarchy)
  • Database setup (SQLite for dev, PostgreSQL for production)
  • Authentication providers (GitHub, Okta, OIDC)
  • Deploying Backstage to Kubernetes
  • Client-server architecture and API communication
  • Proxying external service requests

Existing coverage:

ModuleTopicRelevance
Backstage 7.1Architecture diagram, app-config.yaml, K8s deployment YAMLDirect
Platform Eng 2.3IDP concepts, why portals matterBackground
Platform Eng 2.2Developer Experience principlesBackground

Dedicated CBA module:

ModuleTopicRelevance
Backstage Catalog & InfrastructureAuth providers, proxy, database migrations, production hardening, backend-for-frontendDirect

  • Entity kinds (Component, API, Resource, System, Domain, Group, User, Location, Template)
  • catalog-info.yaml structure and fields
  • Annotations and their purposes
  • Entity ingestion methods (static, discovery, processors)
  • Automated ingestion (GitHub discovery, entity providers)
  • Entity relationships (ownerOf, partOf, consumesApi, providesApi, dependsOn)
  • Troubleshooting catalog issues (orphaned entities, refresh failures)
  • Well-known annotations (backstage.io/techdocs-ref, github.com/project-slug, etc.)

Existing coverage:

ModuleTopicRelevance
Backstage 7.1Entity types, catalog-info.yaml, relationships, annotations, auto-discoveryDirect
Platform Eng 2.4Golden paths concept (templates use catalog)Background
Platform Eng 2.5Self-service conceptsBackground

Dedicated CBA module:

ModuleTopicRelevance
Backstage Catalog & InfrastructureEntity processors, providers, all annotations, troubleshooting, Location kind, lifecycle managementDirect

  • Frontend plugin development (React components)
  • Backend plugin development (Express routers)
  • React fundamentals for Backstage (hooks, state, props)
  • Material UI (MUI) components and theming
  • Backstage plugin APIs (createPlugin, createRoutableExtension, createApiRef)
  • Creating custom themes
  • Adding pages and tabs to the entity view
  • Scaffolder custom actions
  • Extension points and overrides

Existing coverage:

ModuleTopicRelevance
Backstage 7.1Plugin ecosystem overview, basic plugin code snippetMinimal

Dedicated CBA module:

ModuleTopicRelevance
Backstage Plugin DevelopmentReact/MUI, frontend/backend plugins, scaffolder actions, themes, extension pointsDirect

Our existing Backstage module (7.1) provides a toolkit overview, and three dedicated CBA modules now cover the exam in depth: development workflows, plugin development, and catalog/infrastructure operations.

KUBEDOJO CBA COVERAGE
════════════════════════════════════════════════════════════════
Domain 1: Development Workflow (24%) █████████░ ~90% covered
Domain 2: Infrastructure (22%) █████████░ ~90% covered
Domain 3: Catalog (22%) █████████░ ~90% covered
Domain 4: Customizing Backstage (32%) █████████░ ~90% covered
Overall weighted coverage: ~90%
ModuleTopicsDomains Covered
Backstage Developer WorkflowMonorepo structure, TypeScript essentials, Docker builds, app-config overlays, CLI commands, local dev workflowDomain 1 (24%)
Backstage Plugin DevelopmentFrontend plugins (React/MUI), backend plugins (Express), scaffolder custom actions, custom themes, extension points, API refsDomain 4 (32%)
Backstage Catalog & InfrastructureEntity processors, entity providers, all annotations, auth, production deployment, troubleshootingDomains 2-3 (44%)

These three modules plus the existing Module 7.1 provide comprehensive CBA preparation.


CBA PREPARATION PATH (4-week plan)
══════════════════════════════════════════════════════════════
Week 1: Foundations & Catalog (Domains 2-3, 44% of exam)
├── Platform Engineering 2.1-2.3 (IDP concepts)
├── Backstage 7.1 (architecture, catalog, templates)
├── Install Backstage locally, explore the catalog
├── Practice writing catalog-info.yaml for different entity kinds
└── Study all entity relationships and annotations
Week 2: Development Workflow (Domain 1, 24% of exam)
├── Set up local Backstage dev environment
├── Explore monorepo: packages/app, packages/backend
├── Understand app-config.yaml hierarchy and env substitution
├── Practice Docker builds (host build + multi-stage)
├── Learn Backstage CLI commands
└── KubeDojo: Backstage Developer Workflow module
Week 3: Customizing Backstage (Domain 4, 32% of exam!)
├── React fundamentals: components, hooks, props, state
├── Material UI: common components, theming, sx prop
├── Build a frontend plugin from scratch
├── Build a backend plugin with Express router
├── Create a custom scaffolder action
└── KubeDojo: Backstage Plugin Development module
Week 4: Review & Practice
├── Review all 4 domains
├── Focus on Domain 4 (32%) -- biggest weight
├── Practice catalog troubleshooting scenarios
├── Review Backstage official documentation gaps
└── Take practice questions if available

The CBA weights Customizing Backstage at 32% — nearly a third of the exam. Combined with Development Workflow (24%), that means 56% of the exam is about writing code. If you’re coming from an ops background, budget extra time for React and TypeScript.

STUDY TIME ALLOCATION (by exam weight)
══════════════════════════════════════════════════════════════
Customizing Backstage (32%) ████████████████ ← Start weak? Study most
Development Workflow (24%) ████████████
Backstage Catalog (22%) ███████████
Backstage Infrastructure (22%) ███████████

  • This is a code-reading exam. Many questions show TypeScript/React snippets and ask what they do. You don’t write code, but you need to understand it.
  • Know the plugin APIs by heart. createPlugin, createRoutableExtension, createApiRef, createBackendPlugin — know what each does and when to use it.
  • Catalog YAML is heavily tested. Practice writing catalog-info.yaml from memory. Know every entity kind, annotation, and relationship type.
  • Don’t skip Material UI. Questions test specific MUI components (Grid, Card, Table, InfoCard) and how they’re used in Backstage.
  • Understand the config hierarchy. Know how app-config.yaml, app-config.local.yaml, and app-config.production.yaml merge and override. Know how ${VAR} environment substitution works.
  • Focus on the “why.” The exam tests understanding of architectural decisions — why Backstage separates frontend and backend plugins, why the catalog uses a descriptor format, why Software Templates use a step-based workflow.
  • Read the official Backstage docs. The exam is closely aligned with backstage.io/docs. The “Getting Started” and “Plugin Development” sections are especially relevant.
  • TypeScript is non-negotiable. If you don’t know TypeScript, spend a few days on the basics before starting CBA prep. Focus on: types, interfaces, generics, async/await, and module imports.


CERTIFICATION PATH
══════════════════════════════════════════════════════════════
Developer Portal:
└── CBA (Backstage Associate) ← YOU ARE HERE
Platform Engineering:
├── KCNA (Cloud Native Associate) — K8s fundamentals
├── CNPA (Platform Engineering Associate) — Platform basics
└── CNPE (Platform Engineer) — Hands-on platform engineering
Kubernetes:
├── CKA (K8s Administrator) — Cluster operations
├── CKAD (K8s Developer) — Application deployment
└── CKS (K8s Security Specialist) — Security hardening

The CBA pairs well with the CNPE (Certified Cloud Native Platform Engineer). CNPE tests building platforms; CBA tests building the portal that sits on top. Together, they validate end-to-end platform engineering skills. If you’re pursuing the Kubestronaut path, CBA is a complementary certification that deepens your platform tooling expertise.


ModulePathCBA Relevance
Backstage 7.1module-7.1-backstage.mdCore — architecture, catalog, templates, plugins overview
Platform Eng 2.1module-2.1-what-is-platform-engineering.mdBackground — what platform engineering is
Platform Eng 2.2module-2.2-developer-experience.mdBackground — DevEx principles
Platform Eng 2.3module-2.3-internal-developer-platforms.mdBackground — IDP concepts
Platform Eng 2.4module-2.4-golden-paths.mdBackground — golden paths (templates)
Platform Eng 2.5module-2.5-self-service-infrastructure.mdBackground — self-service concepts
Platform Eng 2.6module-2.6-platform-maturity.mdBackground — maturity models