Zertifizierungsinhalte ändern sich – und die Unterlagen von ITZert ändern sich mit. Nach dem Kauf der EX407 Prüfungsfragen erhalten Sie 365 Tage lang kostenlose Updates, sodass Sie auch im Jahr 2026 stets mit dem aktuellen Stand zur RedHat Red Hat Certified Specialist in Ansible Automation Prüfung lernen.

RedHat EX407 Prüfungsübersicht:

Zertifizierungsanbieter:	Red Hat
Prüfungsname:	Red Hat Certified Specialist in Ansible-Automatisierung
Prüfungsnummer:	EX407
Prüfungsformat:	Praxisorientiert / Anwendungsbezogen
Prüfungsdauer:	240 Minuten
Verwandte Zertifizierungen:	Red Hat Certified Engineer in Ansible (RHCE über EX294) Red Hat Certified Architect (RHCA) Red Hat Certified System Administrator (RHCSA)
Verfügbare Sprachen:	Englisch
Beispielfragen:
Prüfungsmethode:	Präsenzprüfung in einem zugelassenen Red Hat-Prüfungszentrum oder praxisorientierte Online-Prüfung mit Fernaufsicht. :contentReference[oaicite:2]{index=2}
Voraussetzungen:	Red Hat empfiehlt praktische Erfahrung mit der Ansible Automation Platform sowie der Administration von Red Hat Enterprise Linux. Eine RHCSA-Zertifizierung oder gleichwertige Kenntnisse werden empfohlen, sind aber keine zwingende Voraussetzung. Die Teilnahme an der Schulung Automation with Ansible (DO407) wird angeraten. :contentReference[oaicite:1]{index=1}
Offizielle Syllabus-URL:	https://www.redhat.com/en/services/training/ex407-red-hat-certified-specialist-in-ansible-automation-exam

RedHat EX407 Prüfungsthemen:

Fragen und Antworten rund um die EX407 Prüfung von RedHat

RedHat Red Hat Certified Specialist in Ansible Automation EX407 Prüfungsfragen mit Lösungen

Frage #1

Create a file called adhoc.sh in /home/sandy/ansible which will use adhoc commands to set up a new repository. The name of the repo will be 'EPEL' the description 'RHEL8' the baseurl is 'https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rmp' there is no gpgcheck, but you should enable the repo.
* You should be able to use an bash script using adhoc commands to enable repos. Depending on your lab setup, you may need to make this repo "state=absent" after you pass this task.

Frage #2

Create a file called requirements.yml in /home/sandy/ansible/roles a file called role.yml in /home/sandy/ansible/.
The haproxy-role should be used on the proxy host. And when you curl http://node3.example.com it should display "Welcome to node4.example.com" and when you curl again "Welcome to node5.example.com" The php-role should be used on the prod host.

Frage #3

===================================================================================
control.realmX.example.com _ workstation.lab.example.com
node1.realmX.example.com _ servera.lab.example.com
node2.realmX.example.com _ serverb.lab.example.com
node3.realmX.example.com _ serverc.lab.example.com
node4.realmX.example.com _ serverd.lab.example.com
node5.realmX.example.com
- username:root, password:redhat
- username:admin, password:redhat
note1. don't change 'root' or 'admin' password.
note2. no need to create ssh-keygen for access, its pre-defined
note3. SELinux is in enforcing mode and firewalld is disabled/stop on whole managed hosts.
Create a playbook called hwreport.yml that produces an output file called /root/
hwreport.txt on all managed nodes with the following information:
------------------------------------------------------------------------------------------------------
--> Inventory host name
--> Total memory in MB
--> BIOS version
--> Size of disk device vda
--> Size of disk device vdb
Each line of the output file contains a single key-value pair.
* Your playbook should:
--> Download the file hwreport.empty from the URL http://classroom.example.com/
hwreport.empty and
save it as /root/hwreport.txt
--> Modify with the correct values.
note: If a hardware item does not exist, the associated value should be set to NONE
----------------------------------------------------------------------------------------------
while practising you to create these file hear. But in exam have to download as per
questation.
hwreport.txt file consists.
my_sys=hostname
my_BIOS=biosversion
my_MEMORY=memory
my_vda=vdasize
my_vdb=vdbsize

Frage #4

In /home/sandy/ansible/ create a playbook called logvol.yml. In the play create a logical volume called Iv0 and make it of size 1500MiB on volume group vgO If there is not enough space in the volume group print a message "Not enough space for logical volume" and then make a 800MiB Iv0 instead. If the volume group still doesn't exist, create a message "Volume group doesn't exist" Create an xfs filesystem on all Iv0 logical volumes. Don't mount the logical volume.

Frage #5

Create a role called sample-apache in /home/sandy/ansible/roles that enables and starts httpd, enables and starts the firewall and allows the webserver service. Create a template called index.html.j2 which creates and serves a message from /var/www/html/index.html Whenever the content of the file changes, restart the webserver service.
Welcome to [FQDN] on [IP]
Replace the FQDN with the fully qualified domain name and IP with the ip address of the node using ansible facts. Lastly, create a playbook in /home/sandy/ansible/ called apache.yml and use the role to serve the index file on webserver hosts.

Fragen und Antworten: