Which of the following is an example of setting up an entity provider in Backstage?

Adding a GitHub entity provider to the catalog configuration

Manually adding entities through the Backstage UI

Writing a custom plugin that directly modifies the catalog database

Creating a new Kubernetes namespace for the catalog

What is the primary purpose of automated ingestion in the Backstage catalog?

To replace the need for any configuration or maintenance of the catalog

To periodically fetch data from external systems and update catalog entities without manual intervention

To provide a one-time import of all existing catalog data

To manually review each catalog entry before it becomes visible to users

How is automated ingestion for a Git repository typically configured in Backstage?

By adding a catalog provider configuration in the Backstage app-config.yaml file

By installing a plugin that automatically detects all repositories in the organization

By editing the source code of the Backstage backend to hardcode repository URLs

By creating a new database table for each repository

A platform team manages a Backstage catalog for 40 microservices. Their source of truth is a set of YAML catalog files stored across multiple Git repositories. They want the catalog to reflect changes within 15 minutes of a merge, without requiring manual refresh. What should they configure?

A URL entity provider pointing to a single aggregated YAML file

A manual catalog import script run by CI after each merge

A static catalog configuration with a 15-minute refresh interval

A Git entity provider with a 15-minute schedule for each repository

What is the role of an entity provider in Backstage's automated ingestion?

To fetch catalog data from an external system and convert it into catalog entities

To validate the syntax of catalog-info.yaml files

To render the catalog UI for end users

To store catalog entities in a database

Certified Backstage Associate (CBA)

Domain 3Objective 6

Working with Automated Ingestion CBA Practice Questions (Page 4)

Part of the Backstage Catalog domain, which accounts for 22% of the CBA exam. Linux Foundation does not publish an official question count, but from its 90-minute exam (~35–60 total, ~8–13 in this domain), expect 1–2 from this objective — we provide 28 practice questions to prepare you well beyond it. (estimate)

28questions here

6free pages

6concepts

22%of the exam

Questions 16–20

16foundation · easy
Which of the following is an example of setting up an entity provider in Backstage?
Select an answer first
17foundation · easy
What is the primary purpose of automated ingestion in the Backstage catalog?
Select an answer first
18foundation · easy
How is automated ingestion for a Git repository typically configured in Backstage?
Select an answer first
19application · medium
A platform team manages a Backstage catalog for 40 microservices. Their source of truth is a set of YAML catalog files stored across multiple Git repositories. They want the catalog to reflect changes within 15 minutes of a merge, without requiring manual refresh. What should they configure?
Select an answer first
20foundation · easy
What is the role of an entity provider in Backstage's automated ingestion?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CBA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Linux Foundation. “CBA” is a trademark of its owner, used for identification only.