Free Certified Backstage Associate (CBA) Practice Questions
100 free questions · Answer explanations · No signup required
View examination details, outline and sourcesLoading selected examination banks…
Sample Practice Questions
Try these 10 sample questions from the Certified Backstage Associate (CBA) practice bank. Each includes the answer and explanation. Continue with the interactive practice above to review the full question set.
1Which command creates a new standalone Backstage application using the official application generator?
- A. npx @backstage/create-app@latest
- B. npx @backstage/cli package build
- C. npx @backstage/cli package start
- D. npx @backstage/cli repo test
2Which description best identifies the purpose of the Backstage framework?
- A. A managed runtime for scheduling application containers
- B. An open source framework for building developer portals
- C. A package registry for distributing compiled JavaScript
- D. A hosted source-control service for application repositories
Answer: B
Explanation: The overview says: "Backstage is an open source framework for building developer" followed by "portals." It integrates tooling into a developer portal rather than acting as a container scheduler, registry, or source-control service.
3What information is the Backstage Software Catalog primarily designed to centralize across an organization's software ecosystem?
- A. Container scheduling and node resource allocation
- B. Ownership and metadata for software assets
- C. Package download caches and compiled application binaries
- D. Live application transactions and database query results
Answer: B
Explanation: The overview describes a centralized system that keeps track of "ownership and metadata for all the software in your ecosystem (services," including websites, libraries, and data pipelines. Catalog inventory and ownership differ from runtime orchestration, artifact storage, or transactional data.
Reference: Backstage Software Catalog — What is a Software Catalog?
4In Backstage's plugin architecture, where does a standalone plugin such as the documented static Tech Radar example execute?
- A. In a backend Node.js process only
- B. In both a browser and a required plugin-specific server
- C. In an external SaaS service only
- D. Entirely in the browser
Answer: D
Explanation: The architecture guide states: "Standalone plugins run entirely in the browser." The static Tech Radar example renders hard-coded information without API requests to other services, so it does not require its own service backend.
Reference: Architecture overview — Plugin architecture — Standalone plugins
5In a newly generated standalone Backstage application, what does running yarn start from the application root start?
- A. The backend alone, with the frontend precompiled
- B. Both frontend and backend as separate processes
- C. The frontend alone, with an external backend required
- D. A production container containing both services
6Which built-in Backstage feature helps create new projects from standardized code skeletons and publish them to a location such as GitHub?
- A. Software Catalog
- B. TechDocs
- C. Software Templates
- D. Search
Answer: C
Explanation: The architecture overview states: "Software Templates - A tool to help you create components inside Backstage. A template can load skeletons of code, include some variables, and then publish the template to a location, such as GitHub." The question concerns project creation rather than inventory, documentation, or information retrieval.
Reference: Architecture overview — Frontend building blocks — Frontend plugins
7How does organizing infrastructure tools around catalog entities help users of a Backstage developer portal?
- A. It replaces tool-specific workflows with editing their catalog metadata
- B. It makes the catalog a directory of external UIs that must be opened separately
- C. It brings tool views around entities into one portal, reducing interface switching
- D. It requires a separate developer portal for each infrastructure tool
Answer: C
Explanation: The catalog guide states: "The software catalog is a great way to organize the infrastructure tools you use to manage the software. This is how Backstage creates one developer portal for all your tools." Its entity-centered integration reduces switching among infrastructure interfaces; it does not replace tool workflows with metadata or require separate UIs or portals for every tool.
Reference: Backstage Software Catalog — Integrated tooling through plugins
8What distinguishes a third-party backend plugin from a service backend plugin in Backstage's documented architectural classification?
- A. Its backing service is hosted outside the adopting company's ecosystem
- B. Its frontend executes on the external service instead of in the Backstage app
- C. Its backing service is hosted inside the adopting company's ecosystem
- D. It runs without a backing service and uses only data bundled in the browser
Answer: A
Explanation: The architecture overview states: "The main difference is that the service which backs the plugin is hosted outside of the ecosystem of the company hosting Backstage." The frontend still integrates into the Backstage app. An internally hosted backing service corresponds to the service-backend form, while browser-only bundled data corresponds to the standalone form.
Reference: Architecture overview — Plugin architecture — Third-party backend plugins
9A standalone Backstage app has compiled successfully, but its browser window did not open. Which default URL should the developer open to view the frontend?
- A. http://localhost:7007
- B. http://localhost:8080
- C. http://localhost:3000
- D. http://localhost:5432
Answer: C
Explanation: The guide says: "When you see the message Rspack compiled successfully, you can navigate directly to http://localhost:3000 to see your Backstage app." This is the default frontend URL for the documented standalone setup.
Reference: Standalone Installation — Browser window didn't open with yarn start
10Which Backstage feature supports creating, maintaining, finding, and using technical documentation with a docs-like-code approach?
- A. Software Templates
- B. Kubernetes
- C. Software Catalog
- D. TechDocs
Answer: D
Explanation: The overview names "Backstage TechDocs for making it easy to" and explains that it helps "create, maintain, find, and use technical documentation". TechDocs is the documentation feature; the other features address scaffolding, service health, or metadata.
Reference: What is Backstage? — What is Backstage? — Out of the box
Topics in this practice bank
These topics describe the available practice for Certified Backstage Associate (CBA). Review the examination outline and its sources for scope and allocation details.
Backstage Development Workflow
- Build and run Backstage projects locally
- Understand local development workflows
- Compile a Backstage project with TypeScript
- Download and install dependencies for a Backstage project with NPM/Yarn
- Use Docker to build a container image of a Backstage project
Backstage Infrastructure
- Understand the Backstage framework
- Configure Backstage
- Deploy Backstage to production
- Understand Backstage client-server architecture
Backstage Catalog
- Understand how/why to use Backstage Catalog
- Populate Backstage Catalog
- Using annotations
- Working with manually registered entity locations
- Troubleshooting entity ingestion
- Working with automated ingestion
Customizing Backstage
- Understand frontend versus backend plugins
- Customizing Backstage plugins
- Make changes to React code in Backstage App
- Using Material UI components
How to use these free practice questions
Choose an answer, check the explanation, and review your progress by chapter. Practice questions and explanations are free to access without signing up.
These are independent study questions, not actual examination items. For examination requirements and official information, view Certified Backstage Associate (CBA) details.