What is the purpose of configuring a refresh schedule for automated ingestion in Backstage?

To ensure the catalog data is updated at regular intervals without manual intervention

To prevent any changes to the catalog from external sources

To limit the number of entities that can be ingested

To manually trigger ingestion when needed

A company's engineering organization is growing, and they are manually adding new services to their Backstage catalog. This process is error-prone and time-consuming. They want to adopt a more scalable and reliable approach. What is the primary benefit of implementing automated ingestion?

It automatically fixes any errors in the source data

It eliminates the need for any manual configuration in Backstage

It guarantees the catalog will have zero downtime

It ensures the catalog is always up to date by continuously polling sources

A company is evaluating whether to implement automated ingestion for their Backstage catalog. Their current process involves developers manually creating pull requests to add new services to a central catalog file. What is a key advantage of switching to automated ingestion?

It reduces the risk of human error and ensures the catalog reflects the actual state of the source system

It guarantees that all entities will be perfectly formatted and error-free

It eliminates the need for developers to learn about Backstage entity specifications

It allows the catalog to be updated in real-time without any delay

A team has just configured a new entity provider for a Git repository. The initial ingestion run completed, but the catalog shows only half of the expected entities. The logs show no errors. What is the most likely reason for the missing entities?

The entity provider is not configured with a schedule

The catalog backend has a limit on the number of entities it can store

Some of the catalog-info.yaml files in the repository are malformed or missing required fields

The Git repository is too large for the provider to handle

Certified Backstage Associate (CBA)

Domain 3Objective 6

Working with Automated Ingestion CBA Practice Questions (Page 2)

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 6–10

6foundation · easy
What is the purpose of configuring a refresh schedule for automated ingestion in Backstage?
Select an answer first
7application · medium
A company's engineering organization is growing, and they are manually adding new services to their Backstage catalog. This process is error-prone and time-consuming. They want to adopt a more scalable and reliable approach. What is the primary benefit of implementing automated ingestion?
Select an answer first
8application · medium
A company is evaluating whether to implement automated ingestion for their Backstage catalog. Their current process involves developers manually creating pull requests to add new services to a central catalog file. What is a key advantage of switching to automated ingestion?
Select an answer first
9application · medium
A team has just configured a new entity provider for a Git repository. The initial ingestion run completed, but the catalog shows only half of the expected entities. The logs show no errors. What is the most likely reason for the missing entities?
Select an answer first
10foundation · easy
Which of the following is a supported source for automated ingestion in the Backstage catalog?
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.