Troubleshooting Entity Ingestion CBA Practice Questions (Page 2)

Questions 6–10

1. 6expert · hard

   A catalog location points to a GitHub repository that contains multiple `catalog-info.yaml` files in subdirectories. The location is registered as a single file URL pointing to the root `catalog-info.yaml`. Only the root entity appears in the catalog; entities in subdirectories do not. What is the most likely cause?

   • AThe subdirectory entities have duplicate names with the root entity.
   • BThe subdirectory entities have invalid `metadata.name` fields.
   • CThe location is registered as a single file, so Backstage does not scan subdirectories for additional catalog files.
   • DThe catalog processor for GitHub is not configured to process subdirectories.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which catalog configuration setting is used to define the locations that the catalog should ingest entities from?

   • A`catalog.locations`
   • B`catalog.processors`
   • C`catalog.providers`
   • D`catalog.rules`
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A component entity in the catalog shows outdated metadata even though the source catalog-info.yaml in GitLab was updated an hour ago. The catalog is configured with a default location refresh interval. Other entities from the same location update correctly. What should you check first?

   • AWhether the GitLab integration token has expired.
   • BWhether the catalog processor for GitLab is enabled in the app-config.
   • CWhether the entity has a duplicate `metadata.name` in the catalog.
   • DWhether the component entity has an individual `backstage.io/refresh-interval` annotation.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   A catalog location points to a GitHub repository URL, but the entity is not being ingested. What is the most likely cause?

   • AThe URL points to a directory that does not contain any entity descriptor files.
   • BThe entity kind is not supported by the catalog.
   • CThe location was registered with the wrong type.
   • DThe catalog refresh interval is set to 0.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   An organization wants to allow only `Component` and `API` entities in the catalog. They configure `catalog.rules` to allow these kinds. However, a `Group` entity still appears in the catalog. What is the most likely cause?

   • AThe catalog location for the Group entity is configured with a different processor.
   • BThe Group entity has a `backstage.io/approved` annotation.
   • CThe Group entity is ingested by a processor that bypasses the catalog rules.
   • DThe catalog rules are case-sensitive and 'group' is lowercase in the YAML.
   Reveal Solution Discussion Select an answer first