EX294 Practice Question: Create content collections and execution environments
An automation team is designing a content collection to distribute internal Ansible modules across the organization. The collection should be installed from a private Galaxy server. To minimize namespace conflicts and ensure discoverability, which naming convention should be used for the collection?
⚠ Common exam trap
A common mix-up: candidates confuse the dot separator with other common naming conventions (like underscores or hyphens used in Python packages or Ansible roles), but Ansible collections strictly require the `namespace.collection_name` format with a dot.
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
✓
namespace.collection_name
In Ansible, collections are distributed using a fully qualified collection name (FQCN) in the format `namespace.collection_name`. This naming convention is required by the Ansible Galaxy server and the `ansible-galaxy collection install` command to uniquely identify and install collections, minimizing namespace conflicts and ensuring discoverability across the organization.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
collection_name.namespace
Why it's wrong here
The order is reversed: the namespace precedes the collection, separated by a dot, giving namespace.collection. Writing collection_name.namespace misplaces the organisational identifier, breaking Galaxy resolution. It tempts because both components are present, but namespace-first ordering is what prevents conflicts and enables discoverability.
- ✗
namespace_collection_name
Why it's wrong here
Ansible collection names use a dot separator between namespace and collection, not an underscore. Underscores are valid inside each component but cannot replace the dot. The format tempts because it resembles Python package naming, yet Galaxy resolves collections strictly on the namespace.collection pattern.
- ✗
namespace-collection_name
Why it's wrong here
A hyphen cannot separate namespace from collection; the required delimiter is a dot. Hyphens are permitted within a component name but not as the namespace/collection separator. The format tempts as a readable alternative, yet Galaxy's parser expects namespace.collection and rejects the hyphenated form.
- ✓
namespace.collection_name
Why this is correct
The namespace.collection_name format is mandatory for Galaxy-hosted collections, where the namespace scopes ownership and prevents conflicts between organisations. This satisfies the stem's requirement to minimise namespace conflicts and ensure discoverability on a private Galaxy server.
Go deeper
Related to this question
About these practice questions
One of 392 original EX294 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.