EX294 · topic practice

Create content collections and execution environments practice questions

Q: How should I use these Create content collections and execution environments practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Q: Can I practise just Create content collections and execution environments questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Create content collections and execution environments domain.

Practise Red Hat Certified Engineer EX294 Create content collections and execution environments practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: Create content collections and execution environments

Practice 10 questions Browse domain →

What the exam tests

What to know about Create content collections and execution environments

Create content collections and execution environments questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Create content collections and execution environments exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Create content collections and execution environments questions

20 questions · select your answer, then reveal the explanation

Question 1hardmultiple choice

Read the full Ansible explanation →

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?

Trap 1: collection_name.namespace

Reverses the order; namespace must come first.

Trap 2: namespace_collection_name

Underscore is not used as a separator; dot is required.

Trap 3: namespace-collection_name

Hyphen is not a valid separator in collection names; dot is used.

Study all Create content collections and execution environments common traps →

A
collection_name.namespace
Why wrong: Reverses the order; namespace must come first.
B
namespace_collection_name
Why wrong: Underscore is not used as a separator; dot is required.
C
namespace-collection_name
Why wrong: Hyphen is not a valid separator in collection names; dot is used.
D
namespace.collection_name
Standard Ansible Galaxy naming convention for collections.

Full breakdown with real-world context →

Question 2mediummultiple choice

Read the full Ansible explanation →

When building an execution environment with ansible-builder, a developer notices that the build process fails with an error about missing dependencies. The developer wants to ensure all required Python packages are installed in the execution environment. Which file should be used to specify additional Python packages?

Trap 1: meta/runtime.yml

Defines Ansible runtime requirements, not Python packages.

Trap 2: galaxy.yml

Defines collection metadata; not used for Python packages.

Trap 3: bindep.txt

Used for system-level package requirements, not Python.

Study all Create content collections and execution environments common traps →

A
meta/runtime.yml
Why wrong: Defines Ansible runtime requirements, not Python packages.
B
galaxy.yml
Why wrong: Defines collection metadata; not used for Python packages.
C
bindep.txt
Why wrong: Used for system-level package requirements, not Python.
D
requirements.txt
Standard file for Python dependencies in execution environments.

Full breakdown with real-world context →

Question 3easymultiple choice

Read the full Ansible explanation →

A system administrator wants to publish a custom Ansible collection to a private Automation Hub. What is the correct command to build the collection before publishing?

Trap 1: ansible-galaxy collection init mycollection

Initializes a new collection skeleton.

Trap 2: ansible-galaxy collection publish ./mycollection-1.0.0.tar.gz

Publishes an already-built collection.

Trap 3: ansible-galaxy collection install .

Installs the collection, does not build a tarball.

Study all Create content collections and execution environments common traps →

A
ansible-galaxy collection init mycollection
Why wrong: Initializes a new collection skeleton.
B
ansible-galaxy collection publish ./mycollection-1.0.0.tar.gz
Why wrong: Publishes an already-built collection.
C
ansible-galaxy collection install .
Why wrong: Installs the collection, does not build a tarball.
D
ansible-galaxy collection build
Builds a collection tarball from the current directory.

Full breakdown with real-world context →

Question 4mediummultiple choice

Read the full Ansible explanation →

An organization uses custom Ansible plugins stored in a collection. A junior admin reports that after updating the collection to version 2.0.0, a playbook that uses a custom filter plugin fails with 'undefined filter'. What is the most likely cause?

Trap 1: The playbook uses an outdated syntax that is incompatible with the…

Version updates typically maintain backward compatibility for filter syntax.

Trap 2: The playbook does not use the fully qualified collection name…

FQCN is not required if the collection is listed in the playbook's collections keyword.

Trap 3: The collection's metadata file galaxy.yml is missing a dependency…

Missing dependencies would cause a different error.

Study all Create content collections and execution environments common traps →

A
The playbook uses an outdated syntax that is incompatible with the new collection.
Why wrong: Version updates typically maintain backward compatibility for filter syntax.
B
The filter plugin was placed in the wrong directory inside the collection.
Filter plugins must reside in plugins/filter/ directory.
C
The playbook does not use the fully qualified collection name (FQCN) for the filter.
Why wrong: FQCN is not required if the collection is listed in the playbook's collections keyword.
D
The collection's metadata file galaxy.yml is missing a dependency declaration.
Why wrong: Missing dependencies would cause a different error.

Full breakdown with real-world context →

Question 5hardmultiple choice

Read the full Ansible explanation →

A DevOps engineer is creating an execution environment for a team that needs both Ansible and the 'requests' Python library. The engineer creates an execution environment definition file (EE.yml) with the following content: --- version: 3 images: base_image: name: registry.redhat.io/ansible-automation-platform-22/ee-minimal-rhel8:latest options: package_manager_path: /usr/bin/microdnf dependencies: python: requirements.txt system: bindep.txt

What is missing from this definition to ensure the 'requests' library is installed?

Trap 1: The package_manager_path should be /usr/bin/yum.

RHEL8 minimal uses microdnf.

Trap 2: The galaxy.yml file must be added to the dependencies section.

Galaxy collections are separate from Python packages.

Trap 3: The base image should be ee-supported-rhel8 instead.

ee-minimal is appropriate for custom builds.

Study all Create content collections and execution environments common traps →

A
The package_manager_path should be /usr/bin/yum.
Why wrong: RHEL8 minimal uses microdnf.
B
The requirements.txt file must contain 'requests'.
The requirements.txt file is referenced but the content is not shown; it must list requests.
C
The galaxy.yml file must be added to the dependencies section.
Why wrong: Galaxy collections are separate from Python packages.
D
The base image should be ee-supported-rhel8 instead.
Why wrong: ee-minimal is appropriate for custom builds.

Full breakdown with real-world context →

Question 6hardmulti select

Read the full Ansible explanation →

Which TWO statements about Ansible content collections are correct?

Trap 1: Collections can be installed only from Galaxy.

They can be installed from Automation Hub, Galaxy, or even a local tarball.

Trap 2: The collection name must be a single word without namespace.

Collection names follow namespace.collection format.

Trap 3: A collection can contain only roles and playbooks.

Collections can contain modules, plugins, roles, playbooks, etc.

Study all Create content collections and execution environments common traps →

A
Collections can be installed only from Galaxy.
Why wrong: They can be installed from Automation Hub, Galaxy, or even a local tarball.
B
The collection name must be a single word without namespace.
Why wrong: Collection names follow namespace.collection format.
C
Collections can be distributed via Automation Hub or Galaxy.
Both are valid distribution platforms for collections.
D
A collection can contain only roles and playbooks.
Why wrong: Collections can contain modules, plugins, roles, playbooks, etc.
E
A collection must have a galaxy.yml file in its root directory.
galaxy.yml is required for metadata.

Full breakdown with real-world context →

Question 7mediummulti select

Read the full Ansible explanation →

Which THREE files are commonly used when building an execution environment with ansible-builder?

Trap 1: ansible.cfg

This is an Ansible configuration file, not used in building EEs.

Trap 2: galaxy.yml

Used for collection metadata, not EE builds.

Study all Create content collections and execution environments common traps →

A
bindep.txt
Lists system-level package dependencies.
B
ansible.cfg
Why wrong: This is an Ansible configuration file, not used in building EEs.
C
galaxy.yml
Why wrong: Used for collection metadata, not EE builds.
D
execution-environment.yml
Main definition file for ansible-builder.
E
requirements.txt
Lists Python dependencies.

Full breakdown with real-world context →

Question 8easymultiple choice

Read the full Ansible explanation →

A user wants to run a playbook that uses a module from 'myorg.mycollection'. The playbook is located in /home/user/projects. Which of the following is true about the collection discovery?

Exhibit

Refer to the exhibit.

$ ansible-galaxy collection list

# /home/user/.ansible/collections/ansible_collections
Collection                       Version
-------------------------------- -------
community.general                5.0.0
myorg.mycollection               1.2.3

# /usr/share/ansible/collections/ansible_collections
Collection                       Version
-------------------------------- -------
redhat.insights                  1.0.0

Trap 1: The user must set the ANSIBLE_COLLECTIONS_PATH environment variable.

The default path includes the user's home directory, so no change needed.

Trap 2: The collection is not installed, so the playbook will fail.

The collection is installed under /home/user/.ansible/collections.

Trap 3: Ansible will look only in /usr/share/ansible/collections.

Ansible searches multiple default paths.

Study all Create content collections and execution environments common traps →

A
The user must set the ANSIBLE_COLLECTIONS_PATH environment variable.
Why wrong: The default path includes the user's home directory, so no change needed.
B
The collection is not installed, so the playbook will fail.
Why wrong: The collection is installed under /home/user/.ansible/collections.
C
Ansible will look only in /usr/share/ansible/collections.
Why wrong: Ansible searches multiple default paths.
D
Ansible will automatically find the collection in the default search path.
Ansible searches ~/.ansible/collections by default.

Full breakdown with real-world context →

Question 9hardmultiple choice

Read the full Create content collections and execution environments explanation →

What is the most likely cause of the build failure?

Exhibit

Refer to the exhibit.

$ cat execution-environment.yml
---
version: 3
images:
  base_image:
    name: registry.redhat.io/ansible-automation-platform-22/ee-minimal-rhel8:latest
options:
  package_manager_path: /usr/bin/microdnf
dependencies:
  galaxy: requirements.yml
  python: requirements.txt
  system: bindep.txt

$ cat requirements.txt
ansible
requests

$ cat bindep.txt
python3-devel [platform:rpm]
gcc [platform:rpm]

$ ansible-builder build -f execution-environment.yml

Build fails with: 'Error: No matching package to install: python3-devel'.

Trap 1: The package_manager_path should be /usr/bin/dnf.

RHEL8 minimal uses microdnf.

Trap 2: The version field in execution-environment.yml is incorrect.

Version 3 is correct for this format.

Trap 3: The base image name is misspelled.

The image name appears correct.

Study all Create content collections and execution environments common traps →

A
The base image already includes python3-devel, causing a conflict with the bindep.txt entry.
ee-minimal images often include development packages; duplicate request fails.
B
The package_manager_path should be /usr/bin/dnf.
Why wrong: RHEL8 minimal uses microdnf.
C
The version field in execution-environment.yml is incorrect.
Why wrong: Version 3 is correct for this format.
D
The base image name is misspelled.
Why wrong: The image name appears correct.

Full breakdown with real-world context →

Question 10hardmultiple choice

Read the full Ansible explanation →

You are an automation engineer at a large enterprise. The company uses Ansible Automation Platform 2.x and has a private Automation Hub server. The security team mandates that all execution environments must be built from a hardened base image that has been approved by the security team. The base image is stored in a private container registry at registry.internal.company.com/hardened-ee:latest. You need to create an execution environment that includes a custom collection 'company.tools' which is hosted on the private Automation Hub. Additionally, the execution environment must include the Python library 'cryptography' version 3.4.8. You have created the following files:

execution-environment.yml: --- version: 3 images: base_image: name: registry.internal.company.com/hardened-ee:latest options: package_manager_path: /usr/bin/microdnf dependencies: galaxy: requirements.yml python: requirements.txt

requirements.yml: --- collections: - name: company.tools source: https://automationhub.company.com/api/galaxy/content/private/

requirements.txt:

cryptography==3.4.8

When you run 'ansible-builder build -f execution-environment.yml', the build fails with an error: 'Error: Failed to resolve dependency cryptography==3.4.8'. Based on this scenario, what is the most likely cause of the failure?

Trap 1: The requirements.yml file has an incorrect source URL for the…

The error is about Python package, not Galaxy collection.

Trap 2: The execution-environment.yml is missing the 'system' dependency…

Missing system deps would cause a different error about system packages.

Trap 3: The package_manager_path should be /usr/bin/dnf instead of microdnf.

The error is about pip, not the package manager.

Study all Create content collections and execution environments common traps →

A
The requirements.yml file has an incorrect source URL for the private Automation Hub.
Why wrong: The error is about Python package, not Galaxy collection.
B
The base image already includes cryptography but not version 3.4.8, causing a version conflict.
The pinned version may conflict with the base image's package, causing pip to fail.
C
The execution-environment.yml is missing the 'system' dependency section for bindep.txt.
Why wrong: Missing system deps would cause a different error about system packages.
D
The package_manager_path should be /usr/bin/dnf instead of microdnf.
Why wrong: The error is about pip, not the package manager.

Full breakdown with real-world context →

Question 11easymultiple choice

Read the full Ansible explanation →

An admin wants to build an execution environment using ansible-builder. Which file is required to define the base image and additional Python dependencies?

Trap 1: requirements.yml

requirements.yml is for Ansible Galaxy collection dependencies, not for the base image.

Trap 2: galaxy.yml

galaxy.yml is for collection metadata, not for execution environment definition.

Trap 3: Dockerfile

Dockerfile is generated by ansible-builder, not manually written.

Study all Create content collections and execution environments common traps →

A
execution-environment.yml
execution-environment.yml is the correct file to define the base image and dependencies.
B
requirements.yml
Why wrong: requirements.yml is for Ansible Galaxy collection dependencies, not for the base image.
C
galaxy.yml
Why wrong: galaxy.yml is for collection metadata, not for execution environment definition.
D
Dockerfile
Why wrong: Dockerfile is generated by ansible-builder, not manually written.

Full breakdown with real-world context →

Question 12hardmultiple choice

Read the full Ansible explanation →

A team develops an Ansible collection and wants to distribute it internally. They have a private Automation Hub. Which approach best ensures that collection dependencies from external sources are also available?

Trap 1: Manually install each dependency on the control node

This is not scalable and error-prone.

Trap 2: Include all dependencies directly in the collection's repository

This duplicates dependencies and doesn't leverage Automation Hub.

Trap 3: Use ansible-galaxy collection download and then upload to private…

This works but is not the best approach; it doesn't automate dependency resolution across environments.

Study all Create content collections and execution environments common traps →

A
Manually install each dependency on the control node
Why wrong: This is not scalable and error-prone.
B
Define a requirements.yml in the execution environment that references both the private hub and external sources
This ensures all dependencies are available from trusted sources.
C
Include all dependencies directly in the collection's repository
Why wrong: This duplicates dependencies and doesn't leverage Automation Hub.
D
Use ansible-galaxy collection download and then upload to private hub
Why wrong: This works but is not the best approach; it doesn't automate dependency resolution across environments.

Full breakdown with real-world context →

Question 13mediummulti select

Read the full Ansible explanation →

Which TWO statements are true about Ansible content collections?

Trap 1: Collections cannot contain playbooks.

Collections can contain playbooks.

Trap 2: A role stored in a collection can be referenced by its short name…

Roles require the fully qualified collection name (FQCN).

Trap 3: Execution environments are required to use collections.

Execution environments are optional for collections.

Study all Create content collections and execution environments common traps →

A
Collections can be installed from Automation Hub, Galaxy, or a Git repository.
Collections support multiple installation sources.
B
Collections cannot contain playbooks.
Why wrong: Collections can contain playbooks.
C
A role stored in a collection can be referenced by its short name without the collection prefix.
Why wrong: Roles require the fully qualified collection name (FQCN).
D
Execution environments are required to use collections.
Why wrong: Execution environments are optional for collections.
E
Fully qualified collection names (FQCN) help avoid naming conflicts.
FQCN uniquely identifies a collection.

Full breakdown with real-world context →

Question 14hardmultiple choice

Study the full Python automation breakdown →

An admin attempts to build an execution environment using the exhibited files. The build fails with an error about incompatible Python dependency. What is the most likely cause?

Exhibit

Refer to the exhibit.

$ cat execution-environment.yml
---
version: 1
build_arg_defaults:
  EE_BASE_IMAGE: 'registry.redhat.io/ansible-automation-platform-21/ee-minimal-rhel8:latest'
dependencies:
  galaxy: requirements.yml
  python: requirements.txt

$ cat requirements.yml
---
collections:
  - name: redhat.insights
  - name: community.general

$ cat requirements.txt
ansible==2.9.27

Trap 1: The execution-environment.yml file uses incorrect syntax for the…

The syntax is correct.

Trap 2: The collections in requirements.yml are not fully qualified.

redhat.insights and community.general are fully qualified.

Trap 3: The base image 'ee-minimal-rhel8' is not a valid execution…

It is a valid Red Hat base image.

Study all Create content collections and execution environments common traps →

A
The Python requirements.txt tries to install a version of Ansible that conflicts with the version in the base image.
The base image already contains Ansible; specifying a version causes conflict.
B
The execution-environment.yml file uses incorrect syntax for the 'dependencies' section.
Why wrong: The syntax is correct.
C
The collections in requirements.yml are not fully qualified.
Why wrong: redhat.insights and community.general are fully qualified.
D
The base image 'ee-minimal-rhel8' is not a valid execution environment base image.
Why wrong: It is a valid Red Hat base image.

Full breakdown with real-world context →

Question 15mediummultiple choice

Read the full Ansible explanation →

Your organization uses Ansible Automation Platform 2.2 with private Automation Hub. You have developed a custom collection named 'my_company.network' that depends on 'cisco.ios' and 'vyos.vyos'. The collection is published in your private hub. You are building an execution environment using ansible-builder. The execution-environment.yml specifies 'EE_BASE_IMAGE: registry.redhat.io/ansible-automation-platform-22/ee-supported-rhel8:latest'. The dependencies section points to a requirements.yml file that includes your collection. When you run 'ansible-builder build', the build succeeds, but when running a playbook that uses modules from 'cisco.ios', you get an error 'module not found'. What is the most likely reason and the correct action to resolve it?

Trap 1: Reinstall the collection on the controller node using…

The issue is in the execution environment, not the controller.

Trap 2: Use a different base image that includes 'cisco.ios'

While possible, the best practice is to specify dependencies explicitly.

Trap 3: Update the collection metadata to include dependencies and rebuild

Collection metadata does not automatically get pulled into execution environment builds.

Study all Create content collections and execution environments common traps →

A
Reinstall the collection on the controller node using 'ansible-galaxy collection install'
Why wrong: The issue is in the execution environment, not the controller.
B
Use a different base image that includes 'cisco.ios'
Why wrong: While possible, the best practice is to specify dependencies explicitly.
C
Update the collection metadata to include dependencies and rebuild
Why wrong: Collection metadata does not automatically get pulled into execution environment builds.
D
Add 'cisco.ios' to the requirements.yml file used during the execution environment build
Explicitly listing the dependency ensures it is included in the execution environment.

Full breakdown with real-world context →

Question 16mediummulti select

Read the full Ansible explanation →

Which TWO statements about Ansible Execution Environments (EE) are true?

Trap 1: Execution environments are primarily used for developing new…

Incorrect: EEs are runtime environments, not development tools.

Trap 2: Execution environments use ansible-navigator as the default…

Incorrect: The entrypoint is ansible-runner.

Trap 3: Execution environments can only be used with the ansible-navigator…

Incorrect: EEs can be used with AWX, Tower, and ansible-runner.

Study all Create content collections and execution environments common traps →

A
Execution environments are primarily used for developing new Ansible modules.
Why wrong: Incorrect: EEs are runtime environments, not development tools.
B
Execution environments use ansible-navigator as the default entrypoint.
Why wrong: Incorrect: The entrypoint is ansible-runner.
C
Execution environments are container images built with ansible-builder.
Correct: ansible-builder is used to create EE images.
D
Execution environments package Ansible Core, collections, and Python dependencies.
Correct: EEs bundle the entire runtime environment.
E
Execution environments can only be used with the ansible-navigator command-line tool.
Why wrong: Incorrect: EEs can be used with AWX, Tower, and ansible-runner.

Full breakdown with real-world context →

Question 17hardmultiple choice

Read the full Ansible explanation →

A user runs the commands shown in the exhibit. The execution environment (EE) builds successfully but the playbook run fails with the error. What is the most likely cause?

Network Topology

Trap 1: The collections_path in ansible.cfg points to a non-existent…

Incorrect: The directory exists as shown by 'ls'.

Trap 2: The execution environment image tag is incorrect.

Incorrect: The image tag 'my-ee:latest' matches the build.

Trap 3: The --pp never flag prevents the EE from being pulled.

Incorrect: --pp never just disables pull policy, but the EE is already local.

Study all Create content collections and execution environments common traps →

A
The collections_path in ansible.cfg points to a non-existent directory.
Why wrong: Incorrect: The directory exists as shown by 'ls'.
B
The execution environment image tag is incorrect.
Why wrong: Incorrect: The image tag 'my-ee:latest' matches the build.
C
The --pp never flag prevents the EE from being pulled.
Why wrong: Incorrect: --pp never just disables pull policy, but the EE is already local.
D
The collection 'community.general' was not included in the execution environment definition file.
Correct: The execution-environment.yml only sets build args, but does not list collections to install. Without a 'galaxy' section or requirements.yml, collections are not added to the EE.

Full breakdown with real-world context →

Question 18easymultiple choice

Read the full Ansible explanation →

You are a Red Hat Certified Engineer tasked with creating a content collection for your organization. The collection will contain roles and modules used by multiple teams. The requirements are: (1) The collection must follow the Ansible community structure. (2) It must include a module that manages network devices. (3) The collection must be versioned and published to Automation Hub. (4) You must provide a minimal working example for other developers. After initial development, you run 'ansible-galaxy collection build' and it fails with 'ERROR! Unknown file type in collection: .gitkeep'. The collection directory contains:

- galaxy.yml - plugins/modules/network_config.py - roles/network/ - tests/ - .gitkeep (in tests/)

What single action should you take to resolve the build error?

Trap 1: Add a 'namespace' field to galaxy.yml.

Incorrect: galaxy.yml already exists and likely has the required fields; the error is about an unknown file, not missing metadata.

Trap 2: Create a .galaxy_ignore.yml file to exclude .gitkeep.

Incorrect: There is no such ignore mechanism; the file must be removed physically.

Trap 3: Move the network_config.py module to a subdirectory named 'modules'.

Incorrect: The module is already in the correct location (plugins/modules/).

Study all Create content collections and execution environments common traps →

A
Add a 'namespace' field to galaxy.yml.
Why wrong: Incorrect: galaxy.yml already exists and likely has the required fields; the error is about an unknown file, not missing metadata.
B
Create a .galaxy_ignore.yml file to exclude .gitkeep.
Why wrong: Incorrect: There is no such ignore mechanism; the file must be removed physically.
C
Remove the .gitkeep file from the collection.
Correct: ansible-galaxy collection build only accepts certain file types (e.g., .yml, .py, .rst). .gitkeep is unrecognized and must be removed.
D
Move the network_config.py module to a subdirectory named 'modules'.
Why wrong: Incorrect: The module is already in the correct location (plugins/modules/).

Full breakdown with real-world context →

Question 19mediumdrag order

Read the full Create content collections and execution environments explanation →

Drag and drop the steps to configure SELinux to allow Apache to read a custom web directory in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 20mediummatching

Read the full Create content collections and execution environments explanation →

Match each firewall zone to its default behavior.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Default zone, untrusted network

Private network, slightly trusted

Demilitarized zone, limited access

All traffic accepted

All incoming packets dropped

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Create content collections and execution environments sessions

Start a Create content collections and execution environments only practice session

Every question in these sessions is drawn from the Create content collections and execution environments domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Create content collections and execution environments questions →Mixed EX294 session

Frequently asked questions

What does the EX294 exam test about Create content collections and execution environments?: Create content collections and execution environments questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Create content collections and execution environments questions in a focused session?: Yes — the session launcher on this page draws every question from the Create content collections and execution environments domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other EX294 topics?: Use the topic links above to move to related areas, or go back to the EX294 question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the EX294 exam covers. They are not copied from any real exam or dump site.

Create content collections and execution environments only

10 questions 20 questions 30 questions 50 questions

Mixed EX294 session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All EX294 questions Create content collections and execution environments domain overview EX294 exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Create content collections and execution environments practice questions

What to know about Create content collections and execution environments

Common Create content collections and execution environments exam traps

Create content collections and execution environments questions

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?

A system administrator wants to publish a custom Ansible collection to a private Automation Hub. What is the correct command to build the collection before publishing?

An organization uses custom Ansible plugins stored in a collection. A junior admin reports that after updating the collection to version 2.0.0, a playbook that uses a custom filter plugin fails with 'undefined filter'. What is the most likely cause?

Which TWO statements about Ansible content collections are correct?

Which THREE files are commonly used when building an execution environment with ansible-builder?

A user wants to run a playbook that uses a module from 'myorg.mycollection'. The playbook is located in /home/user/projects. Which of the following is true about the collection discovery?

Exhibit

What is the most likely cause of the build failure?

Exhibit

An admin wants to build an execution environment using ansible-builder. Which file is required to define the base image and additional Python dependencies?

A team develops an Ansible collection and wants to distribute it internally. They have a private Automation Hub. Which approach best ensures that collection dependencies from external sources are also available?

Which TWO statements are true about Ansible content collections?

An admin attempts to build an execution environment using the exhibited files. The build fails with an error about incompatible Python dependency. What is the most likely cause?

Exhibit

Which TWO statements about Ansible Execution Environments (EE) are true?

A user runs the commands shown in the exhibit. The execution environment (EE) builds successfully but the playbook run fails with the error. What is the most likely cause?

Drag and drop the steps to configure SELinux to allow Apache to read a custom web directory in the correct order.

Match each firewall zone to its default behavior.

Track your progress over time

Start a Create content collections and execution environments only practice session

Related EX294 topic practice pages

Deploy Ansible Automation Platform practice questions

Manage inventories and credentials practice questions

Manage task execution and roles practice questions

Coordinate rolling updates practice questions

Transform data with filters and plugins practice questions