EX294 Exam Dumps – Our Features

Create user accounts--------------------------> A list of users to be created can be found in the file called user_list.ymlsave to /home/admin/ansible/--> Using the password vault created elsewhere in this exam, create a playbook calledcreate_user.ymlthat creates user accounts as follows:--> Users with a job description of developer should be:--> created on managed nodes in the 'dev' and 'test' host groups assigned thepassword from the 'dev_pass'variable and these user should be member of supplementary group 'devops'.--> Users with a job description of manager should be:--> created on managed nodes in the 'prod' host group assigned the password fromthe 'mgr_pass' variableand these user should be member of supplementary group 'opsmgr'--> Passwords should use the 'SHA512' hash format. Your playbook should work usingthe vault password filecreated elsewhere in this exam.while practising you to create these file hear. But in exam have to download as perquestation.user_list.yml file consist:---user:- name: user1job: developer- name: user2job: manager

• Explanation: Solution as: # pwd /home/admin/ansible # wget http://classroom.example.com/user_list.yml # cat user_list.yml # vim create_user.yml --- - name: hosts: all vars_files: - ./user_list.yml - ./vault.yml tasks: - name: creating groups group: name: '{{ item }}' state: present loop: - devops - opsmgr - name: creating user: name: '{{ item.name }}' state: present groups: devops password: '{{ dev_pass|password_hash ('sha512') }}' loop: '{{ user }}' when: (inventory_hostname in groups['dev'] or inventory_hostname in groups['test']) and item.job == 'developer' - name: creating user: name: '{{ item.name }}' state: present groups: opsmgr password: '{{ mgr_pass|password_hash ('sha512') }}' loop: '{{ user }}' when: inventory_hostname in groups['prod'] and item.job == 'manager' :wq! # ansible-playbook create_user.yml ---vault-password-file=password.txt ---syntax-check # ansible-playbook create_user.yml ---vault-password-file=password.txt

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.

• Explanation: /home/sandy/ansible/apache.yml /home/sandy/ansible/roles/sample-apache/tasks/main.yml /home/sandy/ansible/roles/sample-apache/templates/index.html.j2 In /home/sandy/ansible/roles/sample-apache/handlers/main.yml

Create a playbook called web.yml as follows:* The playbook runs on managed nodes in the 'dev' host group* Create the directory /webdev with the following requirements:--> membership in the apache group--> regular permissions: owner=r+w+execute, group=r+w+execute, other=r+executes.p=set group-id* Symbolically link /var/www/html/webdev to /webdev* Create the file /webdev/index.html with a single line of text that reads:''Development''

• Explanation: Solution as: # pwd /home/admin/ansible/ # vim web.yml --- - name: hosts: dev tasks: - name: create group yum: name: httpd state: latest - name: create group: name: apache state: present - name: creating directiory file: path: /webdev state: directory mode: '2775' group: apache - sefcontext: target: '/webdev/index.html' setype: httpd_sys_content_t state: present - name: Apply new SELinux file context to filesystem command: restorecon -irv - name: creating symbolic link file: src: /webdev dest: /var/www/html/webdev state: link force: yes - name: creating file: path: /webdev/index.html sate: touch - name: Adding content to index.html file copy: dest: /webdev/index.html content: 'Development' - name: add service to the firewall firewalld: service: http permanent: yes state: enabled immediate: yes - name: active http service: name: httpd state: restarted enabled: yes :wq # ansible-playbook web.yml ---syntax-check # ansible-playbook web.yml

Create Logical volumes with lvm.yml in all nodes according to followingrequirements.----------------------------------------------------------------------------------------* Create a new Logical volume named as 'data'* LV should be the member of 'research' Volume Group* LV size should be 1500M* It should be formatted with ext4 file-system.--> If Volume Group does not exist then it should print the message 'VG Not found'--> If the VG can not accommodate 1500M size then it should print 'LV Can not becreated withfollowing size', then the LV should be created with 800M of size.--> Do not perform any mounting for this LV.

• Explanation: Solution as: # pwd /home/admin/ansible # vim lvm.yml --- - name: hosts: all ignore_errors: yes tasks: - name: lvol: lv: data vg: research size: '1500' - debug: msg: 'VG Not found' when: ansible_lvm.vgs.research is not defined - debug: msg: 'LV Can not be created with following size' when: ansible_lvm.vgs.research.size_g < '1.5' - name: lvol: lv: data vg: research size: '800' when: ansible_lvm.vgs.research.size_g < '1.5' - name: filesystem: fstype: ext4 dev: /dev/research/data :wq! # ansible-playbook lvm.yml ---syntax-check # ansible-playbook lvm.yml

Create and run an Ansible ad-hoc command.--> As a system administrator, you will need to install software on the managednodes.--> Create a shell script called yum-pack.sh that runs an Ansible ad-hoc command tocreate yum-repository on each of the managed nodes as follows:--> repository1-----------1. The name of the repository is EX4072. The description is 'Ex407 Description'4. GPG signature checking is enabledrelease6. The repository is enabled--> repository2-----------1. The name of the repository is EXX4072. The description is 'Exx407 Description'4. GPG signature checking is enabledrelease6. The repository is enabled

• Explanation: Solution as: # pwd /home/admin/ansible # vim yum-pack.sh #!/bin/bash ansible all -m yum_repository -a 'name=EX407 description='Ex407 Description' baseurl=http://content.example.com/rhel8.0/x86_64/dvd/BaseOS/ gpgcheck=yes gpgkey=http://content.example.com/rhel8.0/x86_64/dvd/RPM-GPG-KEY-redhat-release enabled=yes' ansible all -m yum_repository -a 'name=EXX407 description='Exx407 Description' baseurl=http://content.example.com/rhel8.0/x86_64/dvd/AppStream/ gpgcheck=yes gpgkey=http://content.example.com/rhel8.0/x86_64/dvd/RPM-GPG-KEY-redhat-release enabled=yes' :!wq # chmod +x yum-pack.sh # bash yum-pack.sh # ansible all -m command -a 'yum repolist all'

Install and configure ansibleUser sandy has been created on your control node with the appropriate permissions already, do not change or modify ssh keys. Install the necessary packages to run ansible on the control node. Configure ansible.cfg to be in folder /home/sandy/ansible/ansible.cfg and configure to access remote machines via the sandy user. All roles should be in the path /home/sandy/ansible/roles. The inventory path should be in /home/sandy/ansible/invenlory.You will have access to 5 nodes.node3.example.comConfigure these nodes to be in an inventory file where node I is a member of group dev. nodc2 is a member of group test, node3 is a member of group proxy, nodc4 and node 5 are members of group prod. Also, prod is a member of group webservers.

• Explanation: In/home/sandy/ansible/ansible.cfg [defaults] inventory=/home/sandy/ansible/inventory roles_path=/home/sandy/ansible/roles remote_user= sandy host_key_checking=false [privilegeescalation] become=true become_user=root become_method=sudo become_ask_pass=false In /home/sandy/ansible/inventory [dev] node 1 .example.com [test] node2.example.com [proxy] node3 .example.com [prod] node4.example.com node5 .example.com [webservers:children] prod

Create an ansible vault password file called lock.yml with the password reallysafepw in the /home/sandy/ansible directory. In the lock.yml file define two variables. One is pw_dev and the password is 'dev' and the other is pw_mgr and the password is 'mgr' Create a regular file called secret.txt which contains the password for lock.yml.

• Explanation: ansible-vault create lock.yml New Vault Password: reallysafepw Confirm: reallysafepw

Create a playbook called timesvnc.yml in /home/sandy/ansible using rhel system role timesync. Set the time to use currently configured nip with the server 0.uk.pool.ntp.org. Enable burst. Do this on all hosts.

• Explanation: Solution as:

Create a playbook called balance.yml as follows:* The playbook contains a play that runs on hosts in balancers host group and usesthe balancer role.--> This role configures a service to loadbalance webserver requests between hostsin the webservers host group.curl--> When implemented, browsing to hosts in the balancers host group (for exampleWelcome to node3.example.com on 192.168.10.z--> Reloading the browser should return output from the alternate web server:Welcome to node4.example.com on 192.168.10.a* The playbook contains a play that runs on hosts in webservers host group and usesthe phphello role.--> When implemented, browsing to hosts in the webservers host group with the URL /hello.php should produce the following output:Hello PHP World from FQDN--> where FQDN is the fully qualified domain name of the host. For example,Hello PHP World from node3.example.comfollowing output:Hello PHP World from node4.example.com

• Explanation: Solution as: # pwd /home/admin/ansible/ # vim balancer.yml --- - name: Including phphello role hosts: webservers roles: - ./roles/phphello - name: Including balancer role hosts: balancer roles: - ./roles/balancer :wq! # ansible-playbook balancer.yml --syntax-check # ansible-playbook balancer.yml

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.

• Explanation: chmod 0777 adhoc.sh vim adhoc.sh #I/bin/bash ansible all -m yum_repository -a 'name=EPEL description=RHEL8 baseurl=https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rmp gpgcheck=no enabled=yes'