Troubleshooting Entity Ingestion CBA Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   When diagnosing an entity ingestion failure, which log detail is most useful for identifying the root cause?

   • AThe stack trace from the catalog processor that attempted to parse the entity.
   • BThe total number of entities currently in the catalog.
   • CThe timestamp of the last successful catalog refresh.
   • DThe name of the user who registered the location.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A catalog location points to a Bitbucket Cloud repository. The location was working, but now the catalog logs show: 'Failed to read URL, AuthenticationError: Unauthorized'. Other locations from the same Bitbucket workspace still work. What is the most likely cause?

   • AThe Bitbucket integration is not configured in the app-config.
   • BThe catalog processor for Bitbucket is disabled.
   • CThe specific repository is private and the configured token lacks access to it.
   • DThe location URL has a typo in the repository name.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which of the following is a built-in catalog processor in Backstage?

   • AThe `DatabaseEntityProcessor`
   • BThe `KubernetesEntityProcessor`
   • CThe `AzureEntityProcessor`
   • DThe `GithubEntityProcessor`
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   An entity ingestion fails with the error message 'Unable to read file from target'. Which step should you take first to diagnose the root cause?

   • ARestart the Backstage backend service.
   • BCheck if the target URL is accessible and the file exists at that path.
   • CCheck the entity's relationship references in the descriptor.
   • DReview the catalog configuration for entity policy rules.
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A catalog entity is not updating even though the source YAML file in GitHub was changed. The catalog logs show no errors. The entity has the annotation `backstage.io/refresh-interval: '1h'`. The global `catalog.locations.refreshInterval` is set to `30m`. What is the most likely cause?

   • AThe catalog processor for GitHub is not enabled in the app-config.
   • BThe entity has a duplicate `metadata.name` in the catalog.
   • CThe entity-specific annotation overrides the global setting, so the entity only refreshes every hour.
   • DThe GitHub integration token has expired, preventing the catalog from fetching updates.
   Reveal Solution Discussion Select an answer first