Troubleshooting Entity Ingestion CBA Practice Questions (Page 5)

Questions 21–25

1. 21foundation · easy

   Which tool or method is used to validate an entity descriptor file against the Backstage catalog schema?

   • AThe `curl` command with the `--validate` flag.
   • BThe `npm` command with the `check` flag.
   • CThe `kubectl` command with the `validate` flag.
   • DThe `backstage-cli` with the `catalog:validate` command.
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   A catalog-info.yaml file contains a component entity with `metadata.name: my-service` and `metadata.namespace: default`. The entity fails to ingest with the error: 'Entity does not match the schema: /metadata/name must match pattern "^[a-z0-9]([-a-z0-9]*[a-z0-9])?$"'. The name appears valid. What is the most likely cause?

   • AThe name contains an uppercase letter that is not visible in the error message.
   • BThe namespace field is set to `default` but the entity is in a different namespace.
   • CThe entity has a `metadata.title` field that conflicts with the name.
   • DThe YAML file uses tabs instead of spaces for indentation.
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   A catalog entity for a service has `spec.owner: team:platform`. The team entity exists in the catalog. However, the service's 'Owner' field in the UI shows 'Unresolved'. The catalog logs show: 'Entity has an invalid relation: owner, target team:platform'. What is the most likely cause?

   • AThe catalog has too many entities and the relation processor timed out.
   • BThe service entity is missing the `spec.type` field.
   • CThe team entity has a `spec.owner` field of its own.
   • DThe team entity is defined in a different namespace than the service.
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   When a custom catalog processor throws an error during entity processing, what is the recommended way to handle it?

   • ACatch the error and silently skip the entity.
   • BCatch the error and modify the entity to bypass the processor.
   • CCatch the error, log it, and rethrow it to fail the ingestion.
   • DIgnore the error and let the entity be ingested without processing.
   Reveal Solution Discussion Select an answer first
6. 25expert · hard

   A service entity has `spec.providesApis: [api:payments]`. The API entity `payments` exists in the `default` namespace. The service is in the `payments` namespace. The catalog shows the service, but the 'Provides APIs' field is empty. The logs show: 'Entity has an invalid relation: providesApi, target api:payments'. What is the most likely cause and fix?

   • AThe API is in a different namespace than the service; use the fully qualified reference `api:default/payments`.
   • BThe service entity is missing the `spec.system` field; add a system reference to the service.
   • CThe API entity has a `spec.owner` field that conflicts with the service's owner.
   • DThe API entity is missing the `spec.type` field; add `spec.type: openapi` to the API descriptor.
   Reveal Solution Discussion Select an answer first