Question 220 of 528
Manage automation security and operationshardMultiple ChoiceObjective-mapped

How to Create a Custom Credential Type That Combines Multiple Inputs into a Base64-Encoded Token

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.

An organization uses a proprietary API service that requires token-based authentication with a base64-encoded payload including username, password, and tenant ID. The administrator wants to create a custom credential type in automation controller so that users can input these three values separately, and the playbook receives the final token. Which input configuration fields should be defined?

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

Three separate text fields (username, password, tenant ID) with a custom injector template that concatenates and base64-encodes them.

Option A is correct because automation controller custom credential types allow defining multiple input fields (username, password, tenant ID) and a custom injector template that can concatenate and base64-encode these values into a single token. The injector template uses Jinja2 syntax to combine the inputs and apply the `b64encode` filter, so the playbook receives the final base64-encoded token as a single credential variable.

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.

  • Three separate text fields (username, password, tenant ID) with a custom injector template that concatenates and base64-encodes them.

    Why this is correct

    Allows separate inputs and injector creates the final token.

    Related concept

    Read the scenario before looking for a memorised answer.

  • One text field for the token, and inject it as an environment variable.

    Why it's wrong here

    Does not allow separate inputs for components.

  • Two fields: username and password, and use a lookup plugin to fetch tenant ID.

    Why it's wrong here

    Tenant ID is missing from user input; lookup plugin may not be suitable.

  • Create a single multiline text field where users paste the base64 string.

    Why it's wrong here

    Not user-friendly; requires base64 encoding knowledge.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may think a single text field for the token (Option B) is sufficient, overlooking the requirement for separate input fields and automated encoding, or they may confuse custom credential types with simple credential fields that only store static values.

Detailed technical explanation

How to think about this question

Under the hood, automation controller custom credential types use a Jinja2-based injector template that can reference input field names (e.g., `{{ username }}`, `{{ password }}`, `{{ tenant_id }}`) and apply filters like `b64encode` to produce a single credential value. The injector template can also set environment variables or extra vars, but the key is that the template executes on the controller side before the job runs, so the playbook receives the precomputed token. A real-world scenario is integrating with REST APIs that require a base64-encoded 'username:password:tenant' string for OAuth2 token requests, where the playbook must pass the encoded string in an HTTP header.

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: Three separate text fields (username, password, tenant ID) with a custom injector template that concatenates and base64-encodes them. — Option A is correct because automation controller custom credential types allow defining multiple input fields (username, password, tenant ID) and a custom injector template that can concatenate and base64-encode these values into a single token. The injector template uses Jinja2 syntax to combine the inputs and apply the `b64encode` filter, so the playbook receives the final base64-encoded token as a single credential variable.

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: 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.