Free practice · No sign-up required
15 questions with answer explanations. Choose an answer below to begin.
What is the primary purpose of Backstage in a software development environment?
Understand the core role of Backstage in developer workflows
0/15 answered · Bookmark questions to review later. Focus the practice area to use keys 1–9 and Enter.
Learn by doing
Use official documentation and hands-on labs to work through topics you missed.
Application examples from the Kubernetes project for practicing manifests and application behavior in a cluster.
Try it: Use a disposable cluster. Read a simple application's manifests, predict which Pods its Service selects, then change a label and use kubectl to diagnose the resulting connectivity problem.
Source is free. A local cluster uses your computer; hosted clusters may incur charges.
Guided tutorials for learning Kubernetes behavior and building practical skills beyond multiple-choice recall.
Try it: Complete a basic application tutorial. Repeat the task without the walkthrough, then explain the difference between declared configuration and observed cluster state.
Documentation is free. Your chosen cluster environment may have costs.
Prefer to read at your own pace? Work through each question below, then open its answer to check your reasoning. You can link directly to a question or print this reference.
What is the primary purpose of Backstage in a software development environment?
To provide a unified developer portal for discovering and understanding services
To replace existing CI/CD pipelines
To monitor production application performance
To manage cloud infrastructure provisioning
Correct answer
To provide a unified developer portal for discovering and understanding services
Backstage serves as a developer portal that centralizes service documentation, discovery, and tooling integration. It does not replace CI/CD or infrastructure management tools.
Which component is responsible for storing metadata about software entities in Backstage?
Catalog
TechDocs
Insights
Plugin registry
Correct answer
Catalog
The Catalog maintains a structured inventory of software entities and their relationships. TechDocs handles documentation, while Insights focuses on metrics.
What format is commonly used to define entities in the Backstage catalog?
YAML
JSON
CSV
XML
Correct answer
YAML
Backstage uses YAML files to define catalog entities, enabling version-controlled descriptions of services and components.
Which Backstage feature helps developers discover services and their documentation?
Catalog
Search
Insights
TechDocs
Correct answer
Search
The Search functionality allows developers to find services, APIs, and related documentation across the Backstage portal.
What is a TechDocs component used for in Backstage?
To host and render technical documentation for services
To track incidents and alerts
To manage access control policies
To visualize dependency graphs
Correct answer
To host and render technical documentation for services
TechDocs integrates documentation repositories and renders technical docs alongside service catalog entries.
Which Backstage concept groups related services and provides a structured overview?
Domain
Component
Catalog
Package
Correct answer
Domain
Domains organize services into logical groups, helping teams manage and navigate large portfolios of software assets.
What is the role of the Backstage backend in a typical deployment?
To serve the frontend and coordinate plugin communication
To store container images
To execute CI/CD workflows
To monitor Kubernetes clusters
Correct answer
To serve the frontend and coordinate plugin communication
The backend provides APIs, manages plugins, and serves the frontend, but does not run pipelines or store container images.
Which Backstage plugin is commonly used to integrate source code repositories?
Scaffolder
TechDocs
Catalog
GitHub
Correct answer
GitHub
The GitHub plugin connects Backstage to GitHub repositories to import metadata and link code with catalog entities.
What does the Backstage Scaffolder plugin help teams automate?
Project setup and repetitive tasks
Monitoring dashboards
Documentation publishing
Access policy reviews
Correct answer
Project setup and repetitive tasks
Scaffolder provides templates to automate project creation, reducing manual setup work for development teams.
Which Backstage entity field is typically used to define the owning team?
owner
team
metadata
lifecycle
Correct answer
owner
The 'owner' field in a catalog entity specifies the responsible team or individual for that service.
What is a common way to extend Backstage functionality?
Plugins
Themes
Widgets
Modules
Correct answer
Plugins
Backstage is extensible through plugins that add new features, integrate tools, or customize the user experience.
Which Backstage page provides an overview of an individual service?
Entity page
Home page
Insights page
Catalog index
Correct answer
Entity page
An entity page displays detailed information about a specific service, including its metadata, docs, and related tools.
What is the purpose of the Backstage Insights plugin?
To display metrics and trends for services
To manage user permissions
To generate API documentation
To create deployment pipelines
Correct answer
To display metrics and trends for services
Insights collects and visualizes service-related metrics, helping teams understand performance and usage trends.
Which Backstage concept refers to the inventory of all software components and services?
Catalog
Registry
Repository
Directory
Correct answer
Catalog
The catalog is the central inventory where services, components, and APIs are registered and described.
What is a typical prerequisite for connecting GitHub to Backstage?
A GitHub App with appropriate permissions
A public repository only
A Backstage frontend deployment
A Kubernetes cluster
Correct answer
A GitHub App with appropriate permissions
Connecting GitHub requires a GitHub App that can read repository metadata and post status checks securely.
Recall the answer before opening each card.
To provide a unified developer portal for discovering and understanding services. It centralizes service documentation, discovery, and tooling integration.
The Catalog stores structured metadata about software entities and their relationships, enabling a central inventory of services, components, and APIs.
YAML (YAML Ain't Markup Language) is used to define catalog entities, allowing version-controlled, human-readable descriptions of services and components.
The Search feature allows developers to quickly find services, APIs, and related documentation across the portal by indexing metadata and content.
TechDocs hosts and renders technical documentation for services, integrating documentation repositories and displaying docs alongside catalog entries.
Domains group related services and provide a structured overview, helping teams organize and navigate large portfolios of software assets.
The backend serves the frontend, manages plugin communication, and provides APIs. It does not run pipelines or store container images.
The GitHub plugin connects Backstage to GitHub repositories to import metadata and link code with catalog entities.
The Scaffolder automates project setup and repetitive tasks using templates, reducing manual initialization work for development teams.
The 'owner' field specifies the responsible team or individual for that service, aiding in accountability and communication.
Through plugins, which add new features, integrate tools, or customize the user experience. Plugins are the primary extension mechanism.
The entity page displays detailed information about a specific service, including its metadata, documentation, and related tool integrations.
To display metrics and trends for services, such as performance data and usage patterns, helping teams understand service health.
The catalog is the central inventory of all software components and services, where they are registered and described with metadata.
A GitHub App with appropriate permissions to read repository metadata and post status checks is required for secure integration.
A domain is a logical grouping of related services, providing a structured overview and helping teams manage large service portfolios.
Software components like services, APIs, libraries, and websites are typical entity types. Each has metadata, relationships, and lifecycle information.
The Scaffolder plugin provides templates to automate project creation, including repository setup, configuration, and CI/CD integration.
TechDocs uses tools like mkdocs to build HTML from Markdown files stored in a repository, then displays the rendered docs on the service's entity page.
Insights provides metrics and trends such as deployment frequency, error rates, and resource usage, helping teams monitor service health and performance.
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
Connect the concepts
Open a branch to connect a topic with its practice questions and explanations. Use the map to choose your next review topic.
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.
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.
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.
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.
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.
Study workflow
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.
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.
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.
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.
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
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
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.
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.
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.
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.
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.
Browse another free bank or use the study strategy guide to turn your misses into spaced review.
