A Fully Updated 2026 EX374 Exam Dumps - PDF Questions and Testing Engine
Easy Success RedHat EX374 Exam in First Try
NEW QUESTION # 117
Create an advanced inventory that includes both static and dynamic sources.
Answer:
Explanation:
# inventory_combined.yml plugin: constructed sources:
- static_inventory.yml
- dynamic_inventory.py
Explanation:
Combining static and dynamic inventories ensures flexibility, allowing static definitions while dynamically fetching additional hosts.
NEW QUESTION # 118
Create a source control credential in Automation Controller.
Answer:
Explanation:
1. Navigate to Credentials.
2. Add a new credential: o Type: Source Control o Username: git_user
o Password/Token: secure_token
3. Save the credential.
Explanation:
Source control credentials in Automation Controller enable automated access to repositories for pulling playbooks or roles.
NEW QUESTION # 119
Inspect the logs of an EE build process.
Answer:
Explanation:
podman logs $(podman ps -aq --filter ancestor=my_execution_env:1.0)
Explanation:
Inspecting logs helps troubleshoot issues that occur during the build process, ensuring a functional EE.
NEW QUESTION # 120
Sort a dictionary by its keys using a filter and display the result.
Answer:
Explanation:
- name: Sort dictionary by keys hosts: localhost
vars:
my_dict:
b: 2
a: 1
c: 3
tasks:
- name: Sort dictionary debug:
var: "{{ my_dict | dictsort }}"
Explanation:
Sorting dictionaries by keys organizes data, ensuring predictable and consistent outputs.
NEW QUESTION # 121
Use the Vault file to configure credentials for inventory hosts.
Answer:
Explanation:
# inventory_with_vault.yml
all:
hosts:
web1:
ansible_user: "{{ ansible_user }}"
ansible_password: "{{ ansible_password }}"
Run with:
ansible-playbook site.yml --vault-password-file vault_pass.txt
Explanation:
Integrating Vault variables into inventory files ensures secure use of sensitive credentials during task execution.
NEW QUESTION # 122
Automate the update process for EEs in Automation Controller.
Answer:
Explanation:
1. Use the awx-manage command:
awx-manage update_execution_environments --url registry.example.com/my_execution_env --username user --password pass
2. Schedule this command as a cron job.
Explanation:
Automating EE updates ensures they remain current without manual intervention, reducing maintenance overhead.
NEW QUESTION # 123
Create a .gitignore file to exclude all .log files and commit the change.
Answer:
Explanation:
echo "*.log" > .gitignore
git add .gitignore
git commit -m "Add .gitignore to exclude log files"
Explanation:
The .gitignore file specifies patterns for files Git should ignore, preventing unnecessary files from cluttering the repository.
NEW QUESTION # 124
List the layers of an EE image to analyze its build structure.
Answer:
Explanation:
podman history my_execution_env:1.0
Explanation:
The podman history command displays the layers of the image, helping analyze the build process and track changes across layers.
NEW QUESTION # 125
Automate inventory updates with a cron job.
Answer:
Explanation:
crontab -e
Add:
0 * * * * ansible-inventory -i dynamic_inventory.py --list > inventory_cache.json
Explanation:
Automating inventory updates ensures the inventory stays current without manual intervention.
NEW QUESTION # 126
Configure a custom execution environment as the default in Automation Controller.
Answer:
Explanation:
1. Go to Automation Controller settings.
2. Set the default EE image to registry.example.com/my_execution_env:1.0.
Explanation:
Setting a default EE ensures all playbooks use a consistent runtime unless otherwise specified.
NEW QUESTION # 127
Create a static inventory with groups web and db, each containing two hosts.
Answer:
Explanation:
# inventory.yml
web:
hosts:
web1:
ansible_host: 192.168.1.10 web2:
ansible_host: 192.168.1.11 db:
hosts:
db1:
ansible_host: 192.168.1.20 db2:
ansible_host: 192.168.1.21
Explanation:
A static inventory organizes hosts into groups for targeted playbook execution, enabling efficient host management.
NEW QUESTION # 128
Generate a list of numbers from 1 to 10 using filters.
Answer:
Explanation:
- name: Generate number range hosts: localhost
tasks:
- name: Create range debug:
var: "{{ range(1, 11) | list }}"
Explanation:
The range filter generates sequential numbers, useful for looping or numerical data generation.
NEW QUESTION # 129
Set up a playbook to display ansible_user for web1 using the inventory from inventory.yml.
Answer:
Explanation:
# playbook.yml
- name: Display ansible_user hosts: web1
tasks:
- debug:
var: ansible_user
Execution:
ansible-playbook -i inventory.yml playbook.yml
Explanation:
The debug module helps display variable values, verifying the correct assignment of ansible_user from the inventory.
NEW QUESTION # 130
Create an inventory to manage multiple environments like staging and production.
Answer:
Explanation:
# inventory.yml
staging:
hosts:
web1:
ansible_host: 192.168.1.11 production:
hosts:
web1:
ansible_host: 192.168.1.20
Explanation:
Environment-specific inventories simplify deployments and maintenance across diverse infrastructure setups.
NEW QUESTION # 131
Use a delegated task to add a DNS entry for a host.
Answer:
Explanation:
- name: Add DNS entry hosts: web1
tasks:
- name: Update DNS records
command: echo "web1 IN A 192.168.1.10" >> /etc/dns/zone.file
delegate_to: dns_server
Explanation:
Delegating DNS management tasks to a specific server ensures centralized and consistent DNS configuration.
NEW QUESTION # 132
Schedule a playbook run in Automation Controller.
Answer:
Explanation:
1. Open a job template.
2. Click Schedules > Add.
3. Set the frequency and time for the playbook execution.
Explanation:
Scheduling automates recurring tasks, reducing manual intervention and ensuring consistency.
NEW QUESTION # 133
Use block to group tasks and apply privilege escalation only to the group.
Answer:
Explanation:
- name: Block example hosts: all
tasks:
- block:
- name: Update package cache apt:
update_cache: yes
- name: Install nginx
apt:
name: nginx
state: present
become: yes
Explanation:
Blocks apply common parameters like become to grouped tasks, reducing repetition and improving clarity.
NEW QUESTION # 134
Publish the collection to Ansible Galaxy.
Answer:
Explanation:
ansible-galaxy collection publish my_namespace-my_collection-1.0.0.tar.gz --api-key <your_galaxy_api_key>
Explanation:
The publish command uploads the collection to Ansible Galaxy, making it accessible to the community or other users.
NEW QUESTION # 135
......
EX374 Study Material, Preparation Guide and PDF Download: https://testking.braindumpsit.com/EX374-latest-dumps.html