Question 331 of 518
Manage automation security and operationsmediumMultiple ChoiceObjective-mapped

EX294 Manage automation security and operations Practice Question

This EX294 practice question tests your understanding of manage automation security and operations. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.

An Ansible automation controller job template uses a custom credential type that requires a secret token. The token is stored as an extra variable in the job template definition. A security audit reveals the token is visible in plaintext in the job output. Which action should the administrator take to secure the secret?

Question 1mediummultiple choice
Read the full Ansible explanation →

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

Define the variable in the job template's 'extra variables' field with 'no_log: true' set in the playbook for that variable.

Option A is correct because setting `no_log: true` on the variable in the playbook prevents Ansible from printing the value of that variable in any output, including job logs. This is the standard method to hide sensitive data like tokens when they are passed as extra variables, as it works at the task level to suppress logging of the variable's content.

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.

  • Define the variable in the job template's 'extra variables' field with 'no_log: true' set in the playbook for that variable.

    Why this is correct

    Setting no_log on the variable prevents it from being displayed in logs and job output, meeting the security requirement.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Vault-encrypt the variable in the playbook and reference it with {{ vault_var }}.

    Why it's wrong here

    Vault encryption protects the value at rest but does not hide it from job output when passed as an extra variable.

  • Create a custom credential type that injects the token as an environment variable, and remove the extra variable from the job template.

    Why it's wrong here

    This is a good practice but does not address the existing extra variable; the token would still be visible if the extra variable remains.

  • Store the token in a file on the controller with 600 permissions and use 'lookup' in the playbook.

    Why it's wrong here

    This does not prevent the token from being displayed in job output if it is used as a variable without no_log.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often assume vault encryption alone hides secrets in output, but vault only encrypts at rest; Ansible decrypts at runtime and the plaintext can still appear in logs unless `no_log` is explicitly set.

Trap categories for this question

  • Command / output trap

    Vault encryption protects the value at rest but does not hide it from job output when passed as an extra variable.

Detailed technical explanation

How to think about this question

The `no_log: true` directive is a task-level parameter that tells Ansible to suppress all output from that task, including the values of variables used in `register`, `debug`, or `msg` statements. Under the hood, Ansible uses a callback plugin to filter out any task marked with `no_log`, ensuring that sensitive data never reaches the log stream. In real-world scenarios, combining `no_log` with vault encryption provides defense in depth, but `no_log` alone is sufficient to prevent exposure in job output.

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.

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.

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: Define the variable in the job template's 'extra variables' field with 'no_log: true' set in the playbook for that variable. — Option A is correct because setting `no_log: true` on the variable in the playbook prevents Ansible from printing the value of that variable in any output, including job logs. This is the standard method to hide sensitive data like tokens when they are passed as extra variables, as it works at the task level to suppress logging of the variable's content.

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.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More EX294 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.