Using Annotations CBA Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   Which statement correctly describes annotations in the Backstage catalog?

   • AAnnotations are only allowed on components and not on other entity kinds
   • BAnnotations are required for every entity and must include a backstage.io/techdocs-ref key
   • CAnnotations are optional key-value pairs that provide additional metadata for an entity
   • DAnnotations are used to define the entity's relations to other entities
   Reveal Solution Discussion Select an answer first
2. 17application · easy

   A user is editing a catalog-info.yaml file and adds the following annotation: 'backstage.io/techdocs-ref: dir:./docs'. When they try to register the entity, Backstage reports a validation error. What is the issue?

   • AThe 'dir:' prefix is not valid for TechDocs references.
   • BThe annotation must be placed in the 'spec' section.
   • CThe annotation key is misspelled.
   • DThe value './docs' is not a valid directory reference.
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A catalog entity for a service has the following annotation: 'backstage.io/techdocs-ref: url:https://example.com/docs'. The TechDocs tab is not rendering the documentation. What is the most likely issue?

   • AThe annotation key is misspelled.
   • BThe value should be 'dir:.' instead of a URL.
   • CThe entity needs a 'github.com/project-slug' annotation.
   • DThe URL is not accessible from the Backstage backend.
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   What is the correct value format for the `github.com/project-slug` annotation?

   • AA slug in the format owner/repo, for example my-org/my-repo
   • BA full URL such as https://github.com/my-org/my-repo
   • CA repository name only, for example my-repo
   • DA Git remote URL such as git@github.com:my-org/my-repo.git
   Reveal Solution Discussion Select an answer first
6. 20foundation · easy

   What happens if an annotation key is not prefixed with a valid namespace, such as `backstage.io/` or `github.com/`?

   • AThe entity is rejected by the catalog and cannot be ingested
   • BThe annotation is ignored by Backstage features that expect a specific namespace
   • CThe annotation is automatically prefixed with `backstage.io/`
   • DThe entity is displayed with a warning in the catalog UI
   Reveal Solution Discussion Select an answer first