A platform team manages a Backstage catalog with a mix of sources: a primary Git repository that changes frequently and a secondary API that changes rarely. They want to ensure the Git data is as fresh as possible while minimizing the load on the API. What is the best approach?

Set the same schedule for both sources to keep things simple

Configure two separate entity providers with different schedules

Ingest from the API manually and use automation only for Git

Use a single entity provider for both sources with a common schedule

A developer is setting up a new entity provider to ingest data from an internal API. The API returns data in a custom JSON format that is different from Backstage's entity format. What must the developer do to ensure the data can be ingested into the catalog?

Use the API's JSON format directly in the catalog-info.yaml files

Ask the API team to change their API to return Backstage entity format

Write code in the provider to transform the API's JSON into valid Backstage entities

Modify the Backstage catalog backend to accept the custom JSON format

A team is troubleshooting an entity provider that has stopped ingesting data. The Backstage logs show a 'connection refused' error when the provider tries to reach the source system. What is the most likely cause?

The entity provider's schedule is not configured

The authentication token for the source system has expired

The source system is down or the network path is blocked

The data returned by the source system is malformed

A company has a Backstage catalog that is updated by an entity provider on a schedule. They notice that after a recent change in the source system, the catalog is not reflecting the change. They have verified that the source system is correct. What is the most likely reason for the delay?

The change in the source system is not valid Backstage entity data

The entity provider has been disabled by an administrator

The Backstage catalog is read-only and cannot be updated

The entity provider's next scheduled run has not occurred yet

Which of the following is a common cause of automated ingestion failure in Backstage?

Authentication failures with the external source

The Backstage frontend being offline

The catalog database being too large

Too many entities in the catalog

Certified Backstage Associate (CBA)

Domain 3Objective 6

Working with Automated Ingestion CBA Practice Questions (Page 1)

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 1–5

1expert · hard
A platform team manages a Backstage catalog with a mix of sources: a primary Git repository that changes frequently and a secondary API that changes rarely. They want to ensure the Git data is as fresh as possible while minimizing the load on the API. What is the best approach?
Select an answer first
2application · medium
A developer is setting up a new entity provider to ingest data from an internal API. The API returns data in a custom JSON format that is different from Backstage's entity format. What must the developer do to ensure the data can be ingested into the catalog?
Select an answer first
3application · medium
A team is troubleshooting an entity provider that has stopped ingesting data. The Backstage logs show a 'connection refused' error when the provider tries to reach the source system. What is the most likely cause?
Select an answer first
4application · medium
A company has a Backstage catalog that is updated by an entity provider on a schedule. They notice that after a recent change in the source system, the catalog is not reflecting the change. They have verified that the source system is correct. What is the most likely reason for the delay?
Select an answer first
5foundation · easy
Which of the following is a common cause of automated ingestion failure in Backstage?
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.