- A
Remove the 'env' task from the playbook and ensure no other tasks print environment variables.
Why wrong: This does not prevent future accidental exposure; the root cause is lack of no_log on the credential type.
- B
Configure the automation controller's 'Settings' to enable 'Display secrets' = false.
Why wrong: There is no such global setting; secrets are hidden only if no_log is set on the specific variable.
- C
Change the custom credential type to use the built-in 'Vault password' credential type and remove the custom credential type.
Why wrong: The built-in vault password credential type still injects the password as a variable that can be printed if not protected.
- D
Edit the custom credential type's input injection to set 'no_log: true' for the environment variable that carries the vault password.
This ensures the vault password is never displayed in job output, while still being available for vault decryption.
EX294 Manage automation security and operations Practice Question
This EX294 practice question tests your understanding of manage automation security and operations. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are managing an Ansible Automation Platform deployment that uses automation mesh with one control node and two execution nodes. The control node is in the DMZ, and the execution nodes are in a private network. The organization's security policy requires that all secrets (e.g., SSH keys, API tokens) be encrypted at rest and never transmitted in plaintext. You have configured vault-encrypted credentials and set the vault password as a credential on the control node. However, a recent audit reveals that when a job runs, the vault password is visible in the job output on the execution nodes. The execution nodes are configured to stream job events back to the control node. The automation controller version is 4.3. The following settings are in place: 'no_log' is not set for any variables; the vault password is stored as a 'Vault password' credential type. The job template uses a custom credential type that injects the vault password as an environment variable. The execution nodes have access to the vault password via that environment variable. The audit shows the environment variable is printed in the job output because the playbook uses the 'env' module to display environment variables for debugging. You must prevent the vault password from appearing in any job output without breaking the ability to decrypt vault-encrypted variables. Which action should you take?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"never"Why it matters: Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
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
Edit the custom credential type's input injection to set 'no_log: true' for the environment variable that carries the vault password.
Option D is correct because setting `no_log: true` on the environment variable injection in the custom credential type prevents Ansible from logging the value of that variable in job output, while still allowing the vault password to be used by the playbook to decrypt vault-encrypted variables. This directly addresses the audit finding without removing debugging capabilities or changing the credential type.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Remove the 'env' task from the playbook and ensure no other tasks print environment variables.
Why it's wrong here
This does not prevent future accidental exposure; the root cause is lack of no_log on the credential type.
- ✗
Configure the automation controller's 'Settings' to enable 'Display secrets' = false.
Why it's wrong here
There is no such global setting; secrets are hidden only if no_log is set on the specific variable.
- ✗
Change the custom credential type to use the built-in 'Vault password' credential type and remove the custom credential type.
Why it's wrong here
The built-in vault password credential type still injects the password as a variable that can be printed if not protected.
- ✓
Edit the custom credential type's input injection to set 'no_log: true' for the environment variable that carries the vault password.
Why this is correct
This ensures the vault password is never displayed in job output, while still being available for vault decryption.
Clue confirmation
The clue word "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think removing the debugging task (Option A) is sufficient, but they miss that the underlying issue is the credential injection method, and that `no_log` is the proper way to prevent secret exposure in Ansible Automation Platform.
Detailed technical explanation
How to think about this question
When a custom credential type injects a secret as an environment variable, the `no_log: true` attribute in the injector configuration tells Ansible to mask that variable's value in all job event data, including stdout, stderr, and logs, while still allowing the variable to be used by the playbook. This is implemented at the Ansible runner level, which filters out any variable marked with `no_log` before sending job events back to the controller. In real-world scenarios, this is critical for compliance with standards like PCI-DSS or SOC2, where secrets must never appear in logs.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the EX294 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Manage automation security and operations — study guide chapter
Learn the concepts, then practise the questions
- →
Manage automation security and operations practice questions
Targeted practice on this topic area only
- →
All EX294 questions
518 questions across all exam domains
- →
Red Hat Certified Engineer EX294 study guide
Full concept coverage aligned to exam objectives
- →
EX294 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related EX294 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Deploy Ansible Automation Platform practice questions
Practise EX294 questions linked to Deploy Ansible Automation Platform.
Manage inventories and credentials practice questions
Practise EX294 questions linked to Manage inventories and credentials.
Manage task execution and roles practice questions
Practise EX294 questions linked to Manage task execution and roles.
Coordinate rolling updates practice questions
Practise EX294 questions linked to Coordinate rolling updates.
Transform data with filters and plugins practice questions
Practise EX294 questions linked to Transform data with filters and plugins.
Create content collections and execution environments practice questions
Practise EX294 questions linked to Create content collections and execution environments.
Implement advanced Ansible automation practice questions
Practise EX294 questions linked to Implement advanced Ansible automation.
Manage automation security and operations practice questions
Practise EX294 questions linked to Manage automation security and operations.
EX294 fundamentals practice questions
Practise EX294 questions linked to EX294 fundamentals.
EX294 scenario practice questions
Practise EX294 questions linked to EX294 scenario.
EX294 troubleshooting practice questions
Practise EX294 questions linked to EX294 troubleshooting.
Practice this exam
Start a free EX294 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this EX294 question test?
Manage automation security and operations — This question tests Manage automation security and operations — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Edit the custom credential type's input injection to set 'no_log: true' for the environment variable that carries the vault password. — Option D is correct because setting `no_log: true` on the environment variable injection in the custom credential type prevents Ansible from logging the value of that variable in job output, while still allowing the vault password to be used by the playbook to decrypt vault-encrypted variables. This directly addresses the audit finding without removing debugging capabilities or changing the credential type.
What should I do if I get this EX294 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "never". Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.