> ## Documentation Index > Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Exam Overview > Overview of the Certified Backstage Associate exam format, domains, weights, and key competencies to study, with study tips and links to Backstage documentation. This lesson summarizes the Certified Backstage Associate (CBA) exam format and the exam domains you should focus on. Read through each domain to understand the competencies tested and its approximate weight toward your final score. The exam is proctored online and timed at 90 minutes. Questions are multiple-choice with a single correct answer. There are no hands-on or lab-based tasks — you will not be required to log into any terminals. If you pass, the certification is valid for two years. The exam is 90 minutes long, proctored online, multiple-choice (single answer), with no lab exercises. The certification remains valid for two years after passing. Exam domains at a glance: | Domain | Weight | Core focus | | -----------------------------: | :----: | ------------------------------------------------------------------------------------------------------------------------------------------ | | Backstage Development Workflow | 24% | Local development, TypeScript build and tooling, npm/Yarn dependency management, and building Docker images of Backstage apps. | | Backstage Infrastructure | 22% | Backstage configuration, deployment to production, and understanding client–server architecture and component interactions. | | Backstage Catalog | 22% | Using and populating the software catalog, annotations, entity registration (manual & automated), and troubleshooting ingestion pipelines. | | Customizing Backstage | 32% | Frontend vs backend plugins, creating and modifying plugins, React and Material-UI usage, and theming/backstage UI customization. | Below are expanded summaries for each domain with the specific competencies to prioritize when preparing. Backstage Development Workflow — 24% * Build and run Backstage projects locally (create-app flow and local dev servers). * TypeScript compilation and troubleshooting typical TypeScript issues. * Install and manage dependencies using `npm` and Yarn across Backstage packages. * Use Docker to containerize a Backstage app and understand basic Dockerfile patterns for Backstage services. A presentation slide titled "Domains & Competencies" with a donut chart highlighting 24% for "Backstage Development Workflow." To the right is a rounded box listing related skills like building and running Backstage projects locally, compiling with TypeScript, installing dependencies with NPM/Yarn, and using Docker. Backstage Infrastructure — 22% * Know the Backstage framework components and where configuration lives (`app-config.yaml` and environment layering). * Deploy Backstage to production environments (container orchestration basics, reverse proxies, and static asset serving). * Understand the client–server architecture: how the frontend communicates with backend plugins and service discovery patterns. A presentation slide titled "Domains & Competencies" with a donut chart highlighting a 22% slice for "Backstage Infrastructure." Beside it is a purple-bordered box listing competencies: understand the Backstage framework, configure Backstage, deploy it to production, and understand its client‑server architecture. Backstage Catalog — 22% * Understand the purpose of the Backstage software catalog and when to use it. * Populate the catalog with applications, components, and organizational entities using YAML descriptors. * Use annotations and register entity locations both manually and via automated discovery/ingestion. * Troubleshoot entity ingestion issues and configure automated ingestion pipelines. A slide titled "Domains & Competencies" showing a donut chart with a 22% slice labeled "Backstage Catalog." A blue-green box lists Backstage Catalog competencies like understanding and populating the catalog, using annotations, and troubleshooting/manual/automated entity ingestion. Customizing Backstage — 32% * Distinguish between frontend and backend plugins and know typical responsibilities for each. * Create and customize plugins (frontend and backend) to add functionality and integrations. * Modify React code within a Backstage app to add features and change appearance. * Use Material-UI components and layout primitives to extend and standardize the UI. * Apply theming and design tokens to adjust the overall look-and-feel of your Backstage instance. A presentation slide titled "Domains & Competencies" with a donut chart highlighting "Customizing Backstage" at 32%. To the right, a green panel lists bullet points about frontend vs backend plugins, customizing Backstage plugins, editing React code in the Backstage app, and using Material‑UI components. Study tips * Map your study time to the domain weights — allocate more time to Customizing Backstage (32%) and Development Workflow (24%). * Practice local development flows: scaffold an app, run the dev server, add a simple plugin (frontend and backend), and build a Docker image. * Read the official Backstage docs and examine example plugins to understand patterns and conventions. Links and references * [Backstage Documentation](https://backstage.io/docs/) * [Backstage GitHub Repository](https://github.com/backstage/backstage) * [Backstage Software Catalog Guide](https://backstage.io/docs/features/software-catalog) Focus your review on the competencies listed under each domain to prepare effectively for the exam. Good luck with your preparation!