EX294 Practice Question: Create content collections and execution environments
A collection version is already published on Automation Hub. The developer needs to update the collection with a new feature. What must be done to the version number before publishing again?
⚠ Common exam trap
Watch out — candidates often assume Automation Hub behaves like a mutable artifact repository (e.g., overwriting on re-upload), but Red Hat enforces immutability to ensure version integrity and reproducibility across environments.
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
✓
Increment the patch or minor version number.
Automation Hub enforces immutable collection versions; once a version is published, it cannot be overwritten or deleted. To publish a new feature, you must increment the patch (e.g., 1.0.0 → 1.0.1) or minor (e.g., 1.0.0 → 1.1.0) version number in the galaxy.yml file, following semantic versioning (semver) as required by Ansible collections.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
No change needed; Automation Hub overwrites.
Why it's wrong here
Automation Hub enforces immutability: once a version is published, that exact version string cannot be overwritten or republished. Overwriting is tempting because local builds allow it, but the correct action is to increment the version number, using a minor bump for a new feature, before uploading.
- ✓
Increment the patch or minor version number.
Why this is correct
Automation Hub rejects republishing an existing version, so the version field in galaxy.yml must be incremented before rebuilding and publishing. A patch bump suits a feature addition only if the project's convention allows it; otherwise a minor increment is used to signal new functionality.
- ✗
Increment the major version number.
Why it's wrong here
A new feature is a backwards-compatible addition, so the minor version must be incremented, not the major. Raising the major version signals breaking changes to existing playbooks, which this update does not introduce; that would be correct only when removing or altering existing module interfaces.
- ✗
Change the version to a pre-release identifier.
Why it's wrong here
Automation Hub rejects a version already published, but a pre-release identifier such as 1.0.0-beta does not satisfy the requirement for a new feature release; pre-release versions are for testing before a stable release. A new feature demands an incremented minor version, for example 1.1.0.
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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.