Question 421 of 528
Implement advanced Ansible automationeasyMultiple ChoiceObjective-mapped

How to Prevent Sensitive Data from Printing with no_log

This EX294 practice question tests your understanding of implement advanced ansible automation. 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.

A team wants to ensure that a sensitive variable, such as a database password, is not printed when ansible-playbook runs with -v (verbose). What is the best method to achieve this?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "best"

    Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

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

Use the 'no_log: true' directive on the task.

Option C is correct because the `no_log: true` directive explicitly prevents Ansible from printing the value of any variable used in that task to the console, even when verbosity is increased with `-v`. This is the most direct and secure method to ensure sensitive data like passwords are not exposed in output logs, as it overrides the default logging behavior at the task level.

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.

  • Set the password as an environment variable on the control node.

    Why it's wrong here

    Incorrect: Environment variables can be exposed via logging or process listing; not a direct solution to verbose output.

  • Store the password in a file with 0600 permissions and use lookup('file', ...).

    Why it's wrong here

    Incorrect: Storing securely is good, but if the task prints the variable, it will still be logged in verbose output.

  • Use the 'no_log: true' directive on the task.

    Why this is correct

    Correct: 'no_log: true' suppresses logging of task input/output, protecting sensitive data.

    Clue confirmation

    The clue word "best" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use the 'ansible-vault encrypt_string' command and reference the variable from a vault file.

    Why it's wrong here

    Incorrect: Vault encrypts the variable at rest, but if the task prints the decrypted value, it will appear in verbose logs.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Red Hat often tests the misconception that encrypting data at rest (e.g., with vault or file permissions) is sufficient to prevent exposure during execution, but the real risk is runtime output in verbose logs, which only `no_log: true` addresses.

Trap categories for this question

  • Command / output trap

    Incorrect: Environment variables can be exposed via logging or process listing; not a direct solution to verbose output.

Detailed technical explanation

How to think about this question

Under the hood, `no_log: true` sets a flag on the task's result object that instructs the Ansible callback plugins to mask the task's `stdout`, `stderr`, and `msg` fields with `***` before writing to the log or console. This is enforced at the callback level, meaning even custom callback plugins must respect this flag. A subtle behavior is that `no_log` applies to the entire task result, not just specific variables, so it can inadvertently hide non-sensitive output if used broadly; for finer control, you can use `no_log: true` only on specific parameters via the `loop_control` or by splitting tasks.

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?

Implement advanced Ansible automation — This question tests Implement advanced Ansible automation — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use the 'no_log: true' directive on the task. — Option C is correct because the `no_log: true` directive explicitly prevents Ansible from printing the value of any variable used in that task to the console, even when verbosity is increased with `-v`. This is the most direct and secure method to ensure sensitive data like passwords are not exposed in output logs, as it overrides the default logging behavior at the task level.

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: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

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: Jul 4, 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.