EX294 Practice Question: Create content collections and execution environments
A developer is preparing a collection for distribution and must declare its metadata, including version, license, and the list of collections it depends on. Which file at the collection root contains these declarations?
⚠ Common exam trap
The trap here is mixing up a collection's own manifest with a consumer `requirements.yml` that merely lists collections to install into an environment.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
galaxy.yml
The manifest that describes a collection to Galaxy and to dependency resolution is `galaxy.yml`, which holds version, license, and the `dependencies` mapping. Runtime requirements live elsewhere, and consumer-side requirement files are unrelated to how the collection itself is described when packaged.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
requirements.yml
Why it's wrong here
`requirements.yml` is a consumer-side file used with `ansible-galaxy collection install -r` to list collections to fetch into an environment. It is not part of a collection's own source tree and is not packaged or read during the build of the collection itself. Dependencies declared there affect only the machine running the install.
- ✗
meta/runtime.yml
Why it's wrong here
`meta/runtime.yml` declares the required Ansible core version and, optionally, redirects for renamed or moved plugins. It does not hold version, license, or collection dependency lists. Putting those values here would have no effect on packaging or resolution, so it cannot serve as the manifest for the collection.
- ✗
plugins/README.md
Why it's wrong here
`plugins/README.md` is only a placeholder note generated by `collection init` describing the plugins directory. It carries no structured metadata and is never parsed by the build or Galaxy tooling. Relying on it to declare version or dependencies would leave the collection without a valid manifest, causing the build to fail.
- ✓
galaxy.yml
Why this is correct
`galaxy.yml` is the collection manifest. It carries the namespace, name, version, authors, license, tags, and a `dependencies` mapping that lists other collections and their version constraints. When the collection is built and published, this file supplies the metadata the Galaxy server records and the resolver uses to pull dependent collections.
Go deeper
Related to this question
About these practice questions
This EX294 question is part of Courseiva's 392-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Red Hat exam blueprint
This EX294 practice question is part of Courseiva's free Red Hat certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the EX294 exam.