Certified Backstage Associate Free Practice Questions
This practice set focuses on the core concepts and practical knowledge needed to understand Backstage as a developer portal. It exercises your understanding of Backstage's primary purpose, the role of the Catalog for entity metadata, and the use of YAML for entity definitions. You will engage with features like Search for service discovery, TechDocs for documentation, and Domain for logical grouping. The set also covers backend responsibilities, integration plugins (e.g., GitHub), the Scaffolder for automation, entity fields like owner, extensibility via plugins, entity pages, Insights for metrics, and GitHub integration prerequisites. Mastery of these topics builds foundational skills for managing and navigating a Backstage deployment.
What this CBA practice set measures
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Core Concepts and Architecture
The practice bank establishes the foundational understanding of Backstage's primary purpose: to serve as a unified developer portal for discovering and understanding services. It also covers the architecture by distinguishing the role of the backend (serving frontend and coordinating plugin communication) and the frontend. The questions test your ability to differentiate Backstage from CI/CD or infrastructure tools, ensuring you grasp its value as a central hub. This section reinforces that Backstage is not a replacement for pipelines but a layer that integrates and presents tooling information.
- Identify Backstage's primary role as a developer portal for service discovery and documentation.
- Recognize that the backend serves the frontend and manages plugin communication, not infrastructure pipelines.
- Understand that Backstage unifies tools without replacing them, integrating via plugins and APIs.
Catalog and Entity Management
A major part of the practice set involves the Catalog, which stores metadata about software entities. Questions address the common YAML format for defining entities, the 'owner' field for team assignment, and the concept of 'Domain' for grouping services. The Catalog is described as the central inventory of all software components. The entity page provides detailed views of individual services, and the Search feature helps discover them. This section ensures you can navigate and manage the structural backbone of Backstage.
- The Catalog component stores structured metadata about software entities in YAML files.
- The 'owner' field specifies the responsible team for an entity, aiding accountability.
- Domains group related services, providing a logical overview of service landscapes.
- Entity pages display detailed information for a single service, including docs and metadata.
Plugin Ecosystem and Extensibility
Backstage functionality is extended through plugins, a key concept tested. Specific plugins covered include TechDocs (for hosting and rendering documentation), GitHub (for source code repository integration), Scaffolder (for automating project setup), and Insights (for displaying metrics and trends). The questions emphasize that plugins are the common way to add features or integrate external tools, and that each plugin has a distinct role. This section builds awareness of how to choose and combine plugins to meet team needs.
- TechDocs integrates documentation repositories and renders technical docs alongside services.
- The GitHub plugin connects Backstage to GitHub repositories for metadata import and linking.
- The Scaffolder plugin automates repetitive tasks like project creation using templates.
- The Insights plugin visualizes service metrics and trends for performance monitoring.
Integration and Automation
The final analysis section covers integration requirements and automation patterns. The GitHub plugin requires a GitHub App with appropriate permissions to securely read repository metadata and post status checks. The Scaffolder automates project setup, reducing manual effort. The Search feature enables quick discovery of services and documentation across the portal. These practical aspects demonstrate how Backstage integrates with existing workflows and automates common developer tasks, reinforcing the portal's value in boosting productivity.
- Connecting GitHub requires a GitHub App with permissions for repository metadata and status checks.
- The Scaffolder automates project setup through templates, minimizing manual initialization work.
- The Search feature allows developers to quickly find services, APIs, and related documentation.
Practice Certified Backstage Associate with real flashcards
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 15-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
What is the primary purpose of Backstage in a software development environment?
Show hint
Understand the core role of Backstage in developer workflows
Study workflow
Turn one CBA attempt into a study plan
- 1
Create a Catalog Entity
Define a new service in Backstage by writing a YAML file with required fields: apiVersion, kind, metadata (including name and owner), and spec. Register the file via the Catalog import feature. Use the 'owner' field to link to the responsible team, and optionally add a domain for grouping.
- 2
Integrate a GitHub Repository
Install a GitHub App in your organization's GitHub account with permissions to read repository metadata and content. Provide the app's credentials to Backstage via configuration. Then, use the GitHub plugin to import repositories, automatically creating catalog entities from the repository's metadata.
- 3
Use the Scaffolder Template
Access the Scaffolder plugin in Backstage, select a template for the type of project you need (e.g., service, library). Fill in the required parameters (like name and owner). The Scaffolder will automatically create a repository, set up the project structure, and register the new entity in the catalog.
- 4
Configure TechDocs for a Service
Ensure your service's documentation is stored in a repository alongside code, following Backstage's TechDocs file structure (e.g., a mkdocs.yml and docs/ folder). In the catalog entity YAML, add the 'annotations' field with 'backstage.io/techdocs-ref' pointing to the documentation source URL. The plugin will render the docs on the entity page.
- 5
Search and Discover Services
Use the global Search bar at the top of Backstage to find services by name, keyword, or metadata. Filter results by type (e.g., component, API) or domain. The Search feature indexes all registered entities and their documentation, enabling quick discovery and navigation across the portal.
FAQ
Questions about this CBA practice page
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
What is the primary purpose of Backstage?+
Backstage provides a unified developer portal for discovering and understanding services. It centralizes documentation, service metadata, and tool integration, helping teams manage their software ecosystem without replacing existing CI/CD or infrastructure tools.
How are entities defined in the Backstage catalog?+
Entities are defined using YAML files with standard fields like apiVersion, kind, metadata (name, description, owner), and spec. The 'owner' field specifies the responsible team. YAML allows version-controlled, human-readable definitions that can be imported into the catalog.
What is the role of the TechDocs plugin?+
TechDocs hosts and renders technical documentation alongside service catalog entries. It integrates documentation repositories (e.g., from mkdocs) and displays docs on the service's entity page, making it easy for developers to find and read documentation in context.
What permissions does a GitHub App need for Backstage integration?+
The GitHub App must have permissions to read repository metadata (like name and description) and content (to discover docs and entity files). It may also need write access for tasks like posting commit statuses, depending on the integration features used.
How does the Scaffolder plugin improve developer productivity?+
The Scaffolder automates repetitive tasks like project setup by providing customizable templates. Developers can fill in parameters to create new repositories with pre-defined folder structures, configuration files, and CI/CD pipelines, reducing manual initialization effort and ensuring consistency.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.