How should I use these Manage automation security and operations 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.

EX294 · topic practice

Manage automation security and operations practice questions

Q: Can I practise just Manage automation security and operations 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 Manage automation security and operations domain.

Practise Red Hat Certified Engineer EX294 Manage automation security and operations 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: Manage automation security and operations

Practice 10 questions Browse domain →

What the exam tests

What to know about Manage automation security and operations

Manage automation security and operations 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 Manage automation security and operations 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

Manage automation security and operations questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full Ansible explanation →

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?

Trap 1: Vault-encrypt the variable in the playbook and reference it with {{…

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

Trap 2: Create a custom credential type that injects the token as an…

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

Trap 3: Store the token in a file on the controller with 600 permissions…

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

Study all Manage automation security and operations common traps →

A
Define the variable in the job template's 'extra variables' field with 'no_log: true' set in the playbook for that variable.
Setting no_log on the variable prevents it from being displayed in logs and job output, meeting the security requirement.
B
Vault-encrypt the variable in the playbook and reference it with {{ vault_var }}.
Why wrong: Vault encryption protects the value at rest but does not hide it from job output when passed as an extra variable.
C
Create a custom credential type that injects the token as an environment variable, and remove the extra variable from the job template.
Why wrong: This is a good practice but does not address the existing extra variable; the token would still be visible if the extra variable remains.
D
Store the token in a file on the controller with 600 permissions and use 'lookup' in the playbook.
Why wrong: This does not prevent the token from being displayed in job output if it is used as a variable without no_log.

Full breakdown with real-world context →

Question 2hardmultiple choice

Read the full Ansible explanation →

A Red Hat Ansible Automation Platform deployment uses automation mesh to manage remote nodes across a high-latency WAN. An administrator notices that some job runs fail intermittently due to connection timeouts. The administrator wants to improve reliability without changing network infrastructure. Which configuration change is most effective?

Trap 1: Increase the 'retries' parameter for each task.

Retries handle transient failures but do not extend the time allowed for a single connection.

Trap 2: Increase the 'forks' value in ansible.cfg to 50.

Forks control the number of parallel connections, not timeout behavior.

Trap 3: Set 'async: 600' and 'poll: 10' in the playbook.

Async/poll is for long-running tasks, not for general connection timeouts.

Study all Manage automation security and operations common traps →

A
Increase the 'timeout' value in the [defaults] section of ansible.cfg to 60 seconds.
This extends the connection timeout, accommodating high-latency links.
B
Increase the 'retries' parameter for each task.
Why wrong: Retries handle transient failures but do not extend the time allowed for a single connection.
C
Increase the 'forks' value in ansible.cfg to 50.
Why wrong: Forks control the number of parallel connections, not timeout behavior.
D
Set 'async: 600' and 'poll: 10' in the playbook.
Why wrong: Async/poll is for long-running tasks, not for general connection timeouts.

Full breakdown with real-world context →

Question 3easymultiple choice

Read the full Ansible explanation →

An organization requires that all Ansible playbooks be executed using a specific service account that has limited permissions. The account can only run playbooks from a specific directory. Which approach best enforces this requirement in automation controller?

Trap 1: Use an inventory that contains only the allowed hosts.

Inventory does not restrict which playbooks can be run.

Trap 2: Configure an execution environment that mounts the authorized…

Execution environments provide runtime dependencies, not execution path restrictions.

Trap 3: Assign the service account a machine credential that connects to…

Machine credentials provide authentication, not path restrictions.

Study all Manage automation security and operations common traps →

A
Use an inventory that contains only the allowed hosts.
Why wrong: Inventory does not restrict which playbooks can be run.
B
Configure an execution environment that mounts the authorized directory as read-only.
Why wrong: Execution environments provide runtime dependencies, not execution path restrictions.
C
Create a project that syncs only the authorized directory, and assign the service account as the only user with execute permissions on that project.
Projects control source of playbooks; RBAC can restrict execution to that project.
D
Assign the service account a machine credential that connects to the controller via SSH.
Why wrong: Machine credentials provide authentication, not path restrictions.

Full breakdown with real-world context →

Question 4hardmultiple choice

Read the full Ansible explanation →

A managed node is not responding to Ansible automation. The administrator verifies that the node is reachable via SSH and that the SSH key is correctly deployed. However, 'ansible all -m ping' fails with 'UNREACHABLE'. The automation controller uses a custom execution environment. What is the most likely cause?

Trap 1: The SSH private key has incorrect permissions on the controller.

The administrator verified the SSH key is correctly deployed.

Trap 2: The remote user specified in the credential does not have sudo…

The ping module does not require sudo.

Trap 3: The automation controller is behind a firewall that blocks SSH.

The administrator verified the node is reachable via SSH, so firewall is not blocking.

Study all Manage automation security and operations common traps →

A
The SSH private key has incorrect permissions on the controller.
Why wrong: The administrator verified the SSH key is correctly deployed.
B
The remote user specified in the credential does not have sudo access.
Why wrong: The ping module does not require sudo.
C
The custom execution environment is missing the 'python3' or 'python' package.
Ansible requires Python on the control node (execution environment) to execute modules; missing Python causes unreachable errors.
D
The automation controller is behind a firewall that blocks SSH.
Why wrong: The administrator verified the node is reachable via SSH, so firewall is not blocking.

Full breakdown with real-world context →

Question 5mediummultiple choice

Read the full Ansible explanation →

An Ansible playbook uses 'become: yes' to install packages. The playbook works when run manually by the administrator but fails when run from automation controller with 'Missing sudo password'. The administrator has configured a machine credential with the SSH key and the 'Become password' field is blank. What is the most likely issue?

Trap 1: The become method is set to 'su' instead of 'sudo'.

The playbook works manually, so the become method is correct.

Trap 2: The remote user is not in the sudoers file.

If the user were not in sudoers, the manual run would also fail.

Trap 3: The SSH private key is not loaded into the automation controller.

The administrator configured a machine credential with the SSH key, and manual SSH works.

Study all Manage automation security and operations common traps →

A
The machine credential does not include the become password.
The become password must be supplied in the credential's 'Become password' field when the remote user requires a password for privilege escalation.
B
The become method is set to 'su' instead of 'sudo'.
Why wrong: The playbook works manually, so the become method is correct.
C
The remote user is not in the sudoers file.
Why wrong: If the user were not in sudoers, the manual run would also fail.
D
The SSH private key is not loaded into the automation controller.
Why wrong: The administrator configured a machine credential with the SSH key, and manual SSH works.

Full breakdown with real-world context →

Question 6mediummulti select

Read the full Ansible explanation →

An automation controller administrator must ensure that a playbook's output does not expose sensitive data. Which TWO actions should be taken? (Choose exactly two.)

Trap 1: Set 'stdout_callback = actionable' in ansible.cfg.

This changes callback but does not hide sensitive data.

Trap 2: Use 'name: "Sensitive task"' but keep the task body visible.

The task name does not hide output.

Trap 3: Use 'tags: never' on sensitive tasks.

Tags control task execution, not output visibility.

Study all Manage automation security and operations common traps →

A
Set 'no_log: true' on tasks that handle sensitive data.
This prevents the output of those tasks from being displayed.
B
Set 'stdout_callback = actionable' in ansible.cfg.
Why wrong: This changes callback but does not hide sensitive data.
C
Use 'name: "Sensitive task"' but keep the task body visible.
Why wrong: The task name does not hide output.
D
Add 'display_args_to_stdout = false' to the execution environment's ansible.cfg.
This prevents task arguments from being displayed, which may contain sensitive values.
E
Use 'tags: never' on sensitive tasks.
Why wrong: Tags control task execution, not output visibility.

Full breakdown with real-world context →

Question 7hardmulti select

Read the full Manage automation security and operations explanation →

An organization has multiple automation controller clusters spread across different geographic regions. The security policy requires that job artifacts (such as logs and assets) must remain in the region where the job ran. Which THREE configurations support this requirement? (Choose exactly three.)

Trap 1: Use a custom execution environment that writes artifacts to a…

Network shares could be in another region, violating the policy.

Trap 2: Configure automation mesh to route jobs to the nearest execution…

Mesh routing does not control artifact storage location.

Study all Manage automation security and operations common traps →

A
Disable the 'Enable remote logging' option in the controller configuration for each cluster.
Remote logging would send logs to a central server, violating regional retention.
B
Use a custom execution environment that writes artifacts to a network share.
Why wrong: Network shares could be in another region, violating the policy.
C
Assign each cluster its own inventory and restrict node membership to that region's hosts.
This ensures jobs only run on nodes in the same region, keeping artifacts regional.
D
Set the 'local' execution node for each cluster and configure the controller to store artifacts on the local filesystem.
Local execution and local storage ensure artifacts do not leave the region.
E
Configure automation mesh to route jobs to the nearest execution node.
Why wrong: Mesh routing does not control artifact storage location.

Full breakdown with real-world context →

Question 8hardmultiple choice

Read the full Ansible explanation →

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?

Trap 1: Remove the 'env' task from the playbook and ensure no other tasks…

This does not prevent future accidental exposure; the root cause is lack of no_log on the credential type.

Trap 2: Configure the automation controller's 'Settings' to enable 'Display…

There is no such global setting; secrets are hidden only if no_log is set on the specific variable.

Trap 3: Change the custom credential type to use the built-in 'Vault…

The built-in vault password credential type still injects the password as a variable that can be printed if not protected.

Study all Manage automation security and operations common traps →

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.

Full breakdown with real-world context →

Question 9easymulti select

Read the full Ansible explanation →

A managed node is configured with an Ansible vault-encrypted variable file. When running a playbook that uses these variables, the user receives a 'decryption failed' error. Which two steps should the user take to resolve the issue?

Trap 1: Verify the file permissions are set to 600.

File permissions do not affect Ansible vault decryption.

Trap 2: Check that the SSH private key has access to the managed node.

SSH key is not related to vault decryption.

Trap 3: Make sure the vault password file contains the path to the vault…

Vault password file should contain the password, not the file path.

Study all Manage automation security and operations common traps →

A
Verify the file permissions are set to 600.
Why wrong: File permissions do not affect Ansible vault decryption.
B
Check that the SSH private key has access to the managed node.
Why wrong: SSH key is not related to vault decryption.
C
Make sure the vault password file contains the path to the vault file.
Why wrong: Vault password file should contain the password, not the file path.
D
Ensure the vault ID matches the one used when encrypting the file.
Vault ID must match if used during encryption.
E
Verify the correct vault password is being provided.
The vault password is required for decryption.

Full breakdown with real-world context →

Question 10hardmultiple choice

Read the full Ansible explanation →

Your team manages a fleet of 200 Red Hat Enterprise Linux 8 servers. Security policy requires that all servers have a specific set of security configurations: (1) SELinux must be enforcing, (2) the firewall must allow only SSH and HTTPS, (3) SSH root login must be disabled, and (4) the 'auditd' service must be running and enabled. You have created an Ansible role 'security-hardening' that applies these settings. The role is idempotent and uses the 'lineinfile' module to modify /etc/ssh/sshd_config, the 'firewalld' module to configure firewall rules, the 'selinux' module to set SELinux to enforcing, and the 'service' module to enable and start auditd. You run the playbook against a test group of 10 servers, and it reports 'changed=0' for all tasks, indicating the servers are already compliant. However, a subsequent manual audit reveals that on two servers, SELinux is permissive and SSH root login is still permitted. What is the most likely cause of this discrepancy?

Trap 1: The 'become' privilege escalation is not configured, so the tasks…

If become was not working, tasks would fail with permission errors, not report changed=0.

Trap 2: The playbook was run with the '--check' flag, which simulates…

If run with --check, the output would indicate 'check mode' and not actual changes; but the scenario says 'changed=0', which means actual run.

Trap 3: The Ansible modules used in the role are not installed on the…

If modules were missing, the playbook would fail with an error, not report changed=0.

Study all Manage automation security and operations common traps →

A
The 'become' privilege escalation is not configured, so the tasks cannot modify system files.
Why wrong: If become was not working, tasks would fail with permission errors, not report changed=0.
B
The playbook was run with the '--check' flag, which simulates changes without applying them.
Why wrong: If run with --check, the output would indicate 'check mode' and not actual changes; but the scenario says 'changed=0', which means actual run.
C
The inventory hostnames for those two servers are incorrect, causing Ansible to connect to different hosts that are already compliant.
Ansible reported changes on the hosts it connected to, but those are not the actual servers needing changes.
D
The Ansible modules used in the role are not installed on the control node.
Why wrong: If modules were missing, the playbook would fail with an error, not report changed=0.

Full breakdown with real-world context →

Question 11mediumdrag order

Read the full Manage automation security and operations explanation →

Drag and drop the steps to configure a container using Podman with a custom Dockerfile 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 12mediummatching

Read the full Manage automation security and operations explanation →

Match each Linux command to its function.

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

Concepts

Matches

Socket statistics

Query systemd journal

Show current SELinux mode

Manage firewalld rules

Extend a logical volume

Question 13easymultiple choice

Read the full Ansible explanation →

An automation team wants to securely store SSH private keys for use in playbooks. Which Ansible feature should they use?

Trap 1: Ansible Collections

Collections are module packages, not for secret storage.

Trap 2: Ansible Fact Cache

Fact cache caches gathered facts, not secrets.

Trap 3: Ansible Galaxy

Galaxy distributes roles/collections, not for secrets.

Study all Manage automation security and operations common traps →

A
Ansible Collections
Why wrong: Collections are module packages, not for secret storage.
B
Ansible Vault
Ansible Vault encrypts sensitive data.
C
Ansible Fact Cache
Why wrong: Fact cache caches gathered facts, not secrets.
D
Ansible Galaxy
Why wrong: Galaxy distributes roles/collections, not for secrets.

Full breakdown with real-world context →

Question 14mediummultiple choice

Read the full Ansible explanation →

A playbook fails with 'ERROR! 'become' is not a valid attribute for a Play'. What is the most likely cause?

Trap 1: The playbook lacks a hosts line

Missing hosts causes a different error.

Trap 2: The become directive is misspelled

The correct attribute name is 'become', not misspelling.

Trap 3: become is allowed only in tasks, not plays

become can be set at play level.

Study all Manage automation security and operations common traps →

A
The playbook lacks a hosts line
Why wrong: Missing hosts causes a different error.
B
The become directive is misspelled
Why wrong: The correct attribute name is 'become', not misspelling.
C
become is allowed only in tasks, not plays
Why wrong: become can be set at play level.
D
The playbook uses an older syntax that requires 'sudo'
Older Ansible used 'sudo: yes' instead of 'become: yes'.

Full breakdown with real-world context →

Question 15hardmultiple choice

Read the full Manage automation security and operations explanation →

An organization uses Automation Controller with multiple teams. They want to ensure that team members can only launch job templates that are explicitly assigned to their team. Which configuration approach should be used?

Trap 1: Assign each team to an organization and set organization-level…

Organization permissions grant too broad access.

Trap 2: Set 'allow simultaneous' to false on job templates

That controls concurrent runs, not access.

Trap 3: Use an Identity Provider (IdP) to restrict access

IdP handles authentication only.

Study all Manage automation security and operations common traps →

A
Assign each team to an organization and set organization-level permissions
Why wrong: Organization permissions grant too broad access.
B
Set 'allow simultaneous' to false on job templates
Why wrong: That controls concurrent runs, not access.
C
Use an Identity Provider (IdP) to restrict access
Why wrong: IdP handles authentication only.
D
Create roles and assign them at the job template level using team roles
Team roles on job templates restrict launch access.

Full breakdown with real-world context →

Question 16easymultiple choice

Read the full Ansible explanation →

A developer wants to encrypt a string in a playbook variable file. Which command should they use?

Trap 1: ansible-vault rekey

Changes the vault password.

Trap 2: ansible-vault create

Creates a new vault file, not encrypt a string.

Trap 3: ansible-vault edit

Edits an existing vault, not encrypt a string.

Study all Manage automation security and operations common traps →

A
ansible-vault rekey
Why wrong: Changes the vault password.
B
ansible-vault create
Why wrong: Creates a new vault file, not encrypt a string.
C
ansible-vault edit
Why wrong: Edits an existing vault, not encrypt a string.
D
ansible-vault encrypt_string
Encrypts a single string inline.

Full breakdown with real-world context →

Question 17mediummultiple choice

Read the full Ansible explanation →

An Ansible playbook is failing due to an undefined variable. Which approach would best help identify the source of the variable?

Trap 1: Add the 'ignore_errors: yes' directive

Suppresses errors, does not identify source.

Trap 2: Set environment variable ANSIBLE_DEBUG=1

Increases verbosity but may be too noisy.

Trap 3: Use the --syntax-check flag

Only checks syntax, not variable values.

Study all Manage automation security and operations common traps →

A
Add the 'ignore_errors: yes' directive
Why wrong: Suppresses errors, does not identify source.
B
Set environment variable ANSIBLE_DEBUG=1
Why wrong: Increases verbosity but may be too noisy.
C
Add a debug task with var: hostvars[inventory_hostname]
Displays all host variables, helping locate undefined.
D
Use the --syntax-check flag
Why wrong: Only checks syntax, not variable values.

Full breakdown with real-world context →

Question 18hardmultiple choice

Read the full Ansible explanation →

A Red Hat Ansible Automation Platform installation uses a custom execution environment. The playbook runs fail with 'execution environment not found'. The execution environment is stored in a private registry requiring authentication. What must be configured?

Trap 1: Set the execution_environment_image variable in the playbook

That specifies the image name, not registry authentication.

Trap 2: Configure the execution environment in the inventory

Inventory does not set execution environment configuration.

Trap 3: Add the registry to the project's source control

Source control does not manage registry authentication.

Study all Manage automation security and operations common traps →

A
Set the execution_environment_image variable in the playbook
Why wrong: That specifies the image name, not registry authentication.
B
Configure the execution environment in the inventory
Why wrong: Inventory does not set execution environment configuration.
C
Add the registry URL to the automation controller's container registry credentials
Controller needs registry credentials to pull the image.
D
Add the registry to the project's source control
Why wrong: Source control does not manage registry authentication.

Full breakdown with real-world context →

Question 19easymultiple choice

Read the full Manage automation security and operations explanation →

An administrator needs to limit the number of concurrent jobs that can run on a specific automation controller node. Which setting should be adjusted?

Trap 1: The forks parameter in the playbook

Forks controls parallel tasks, not jobs.

Trap 2: The job template's 'allow simultaneous' option

Controls concurrent runs of the same template.

Trap 3: The number of execution environments

Execution environments are not a job throttle.

Study all Manage automation security and operations common traps →

A
The forks parameter in the playbook
Why wrong: Forks controls parallel tasks, not jobs.
B
The job template's 'allow simultaneous' option
Why wrong: Controls concurrent runs of the same template.
C
The number of execution environments
Why wrong: Execution environments are not a job throttle.
D
The max concurrent jobs setting in the node's configuration
Limits jobs on that node.

Full breakdown with real-world context →

Question 20mediummultiple choice

Read the full Ansible explanation →

A playbook using the 'uri' module is timing out when connecting to an external API. The network team confirms connectivity. What Ansible configuration parameter can be adjusted to increase the timeout?

Trap 1: validate_certs

Controls SSL certificate validation, not timeout.

Trap 2: retries

Used in loop retry, not connection timeout.

Trap 3: delay

Used in loop delays, not timeout.

Study all Manage automation security and operations common traps →

A
validate_certs
Why wrong: Controls SSL certificate validation, not timeout.
B
retries
Why wrong: Used in loop retry, not connection timeout.
C
ansible_timeout
Sets the timeout for connections.
D
delay
Why wrong: Used in loop delays, not timeout.

Full breakdown with real-world context →

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 Manage automation security and operations sessions

Start a Manage automation security and operations only practice session

Every question in these sessions is drawn from the Manage automation security and operations domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Manage automation security and operations questions →Mixed EX294 session

Frequently asked questions

What does the EX294 exam test about Manage automation security and operations?: Manage automation security and operations 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 Manage automation security and operations questions in a focused session?: Yes — the session launcher on this page draws every question from the Manage automation security and operations 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.

Manage automation security and operations 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 Manage automation security and operations 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.

Manage automation security and operations practice questions

What to know about Manage automation security and operations

Common Manage automation security and operations exam traps

Manage automation security and operations questions

An organization requires that all Ansible playbooks be executed using a specific service account that has limited permissions. The account can only run playbooks from a specific directory. Which approach best enforces this requirement in automation controller?

An automation controller administrator must ensure that a playbook's output does not expose sensitive data. Which TWO actions should be taken? (Choose exactly two.)

An organization has multiple automation controller clusters spread across different geographic regions. The security policy requires that job artifacts (such as logs and assets) must remain in the region where the job ran. Which THREE configurations support this requirement? (Choose exactly three.)

A managed node is configured with an Ansible vault-encrypted variable file. When running a playbook that uses these variables, the user receives a 'decryption failed' error. Which two steps should the user take to resolve the issue?

Drag and drop the steps to configure a container using Podman with a custom Dockerfile in the correct order.

Match each Linux command to its function.

An automation team wants to securely store SSH private keys for use in playbooks. Which Ansible feature should they use?

A playbook fails with 'ERROR! 'become' is not a valid attribute for a Play'. What is the most likely cause?

An organization uses Automation Controller with multiple teams. They want to ensure that team members can only launch job templates that are explicitly assigned to their team. Which configuration approach should be used?

A developer wants to encrypt a string in a playbook variable file. Which command should they use?

An Ansible playbook is failing due to an undefined variable. Which approach would best help identify the source of the variable?

A Red Hat Ansible Automation Platform installation uses a custom execution environment. The playbook runs fail with 'execution environment not found'. The execution environment is stored in a private registry requiring authentication. What must be configured?

An administrator needs to limit the number of concurrent jobs that can run on a specific automation controller node. Which setting should be adjusted?

A playbook using the 'uri' module is timing out when connecting to an external API. The network team confirms connectivity. What Ansible configuration parameter can be adjusted to increase the timeout?

Track your progress over time

Start a Manage automation security and operations 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

Create content collections and execution environments practice questions

Implement advanced Ansible automation practice questions