EX300 Exam Dumps - Red Hat Certified Engineer - RHCE (v6+v7)
In accordance with the following requirements to deploy ssh login service:
- harry belongs to example.com which can remote login your systems.
- However, users of remote.test cannot use ssh login to your machine.
RHCE Test Configuration Instructions
Information for the two systems you will use in test is the following:
system1.group3.example.com: is one of the main sever. system2.group3.example.com: mainly used as a client.
Password for both of the two systems is atenorth
System’s IP is provided by DHCP, you can regard it as normal, or you can reset to Static IP in accordance with the following requirements:
system1.group3.example.com: 172.24.3.5
system2.group3.example.com: 172.24.3.10
The subnet mask is 255.255.255.0
Your system is a member of DNS domain group3.example.com. All systems in DNS domain group3.example.com are all in subnet 172.24.3.0/255.255.255.0, the same all systems in this subnet are also in group3.example.com, unless specialized, all network services required to be configured can be accessed by systems of domain group3.
host.group3.example.com provides a centralized authentication service domain
GROUP3.EXAMPLE.COM, both system1 and system2 have already been pre-configured to be the client for this domain, this domain provides the following user account:
Firewall is enabled by default, you can turn it off when deemed appropriate, other settings about firewall may be in separate requirements.
Your system will be restarted before scoring, so please ensure that all modifications and service configurations you made still can be operated after the restart without manual intervention, virtual machine instances of all examinations must be able to enter the correct multi-user level after restart without manual assistance, it will be scored zero if the test using virtual machine system cannot be restarted or be properly restarted.
Corresponding distribution packages for the testing using operating system Red Hat Enterprise Linux version can be found in the following link:
http://server1.group3.example.com/rhel
Part of the requirements include host security, ensure your host security limit does not prevent the request to allow the host and network, although you correctly configured the network service but would have to allow the host or network is blocked, this also does not score.
You will notice that some requirements which clearly do not allow services be accessed by service domain my133t.org, systems of this domain are in subnet 172.25.1.0/252.255.255.0, and systems of these subnets also belong to my 133t.org domain.
PS: Notice that some test questions may depend on other exam questions, for example, you might be asked to perform a series of restrictions on a user, but this user creation may be required in other questions. For convenient identification, each exam question has some radio buttons to help you identify which questions you have already completed or not completed. Certainly, you do not need to care these buttons if you don’t need them.
Configure SELINUX
Modify the state of selinux to Enforcing mode.
Use VIM /etc/selinux
RHCE Test Configuration Instructions
Information for the two systems you will use in test is the following:
system1.group3.example.com: is one of the main sever. system2.group3.example.com: mainly used as a client.
Password for both of the two systems is atenorth
System’s IP is provided by DHCP, you can regard it as normal, or you can reset to Static IP in accordance with the following requirements:
system1.group3.example.com: 172.24.3.5
system2.group3.example.com: 172.24.3.10
The subnet mask is 255.255.255.0
Your system is a member of DNS domain group3.example.com. All systems in DNS domain group3.example.com are all in subnet 172.24.3.0/255.255.255.0, the same all systems in this subnet are also in group3.example.com, unless specialized, all network services required to be configured can be accessed by systems of domain group3.
host.group3.example.com provides a centralized authentication service domain
GROUP3.EXAMPLE.COM, both system1 and system2 have already been pre-configured to be the client for this domain, this domain provides the following user account:
Firewall is enabled by default, you can turn it off when deemed appropriate, other settings about firewall may be in separate requirements.
Your system will be restarted before scoring, so please ensure that all modifications and service configurations you made still can be operated after the restart without manual intervention, virtual machine instances of all examinations must be able to enter the correct multi-user level after restart without manual assistance, it will be scored zero if the test using virtual machine system cannot be restarted or be properly restarted.
Corresponding distribution packages for the testing using operating system Red Hat Enterprise Linux version can be found in the following link:
http://server1.group3.example.com/rhel
Part of the requirements include host security, ensure your host security limit does not prevent the request to allow the host and network, although you correctly configured the network service but would have to allow the host or network is blocked, this also does not score.
You will notice that some requirements which clearly do not allow services be accessed by service domain my133t.org, systems of this domain are in subnet 172.25.1.0/252.255.255.0, and systems of these subnets also belong to my 133t.org domain.
PS: Notice that some test questions may depend on other exam questions, for example, you might be asked to perform a series of restrictions on a user, but this user creation may be required in other questions. For convenient identification, each exam question has some radio buttons to help you identify which questions you have already completed or not completed. Certainly, you do not need to care these buttons if you don’t need them.
Create a script
Create a script named /root/foo.sh on the system1, make it provide the following characteristics:
- When running /root/foo.sh redhat, the output is fedora
- When running /root/foo.sh fedora, the output is redhat
- When there is no parameter or parameter is not redhat or fedora, the following information will be generated by the error output: /root/foo.sh redhat:fedora
RHCE Test Configuration Instructions
Information for the two systems you will use in test is the following:
system1.group3.example.com: is one of the main sever. system2.group3.example.com: mainly used as a client.
Password for both of the two systems is atenorth
System’s IP is provided by DHCP, you can regard it as normal, or you can reset to Static IP in accordance with the following requirements:
system1.group3.example.com: 172.24.3.5
system2.group3.example.com: 172.24.3.10
The subnet mask is 255.255.255.0
Your system is a member of DNS domain group3.example.com. All systems in DNS domain group3.example.com are all in subnet 172.24.3.0/255.255.255.0, the same all systems in this subnet are also in group3.example.com, unless specialized, all network services required to be configured can be accessed by systems of domain group3.
host.group3.example.com provides a centralized authentication service domain
GROUP3.EXAMPLE.COM, both system1 and system2 have already been pre-configured to be the client for this domain, this domain provides the following user account:
Firewall is enabled by default, you can turn it off when deemed appropriate, other settings about firewall may be in separate requirements.
Your system will be restarted before scoring, so please ensure that all modifications and service configurations you made still can be operated after the restart without manual intervention, virtual machine instances of all examinations must be able to enter the correct multi-user level after restart without manual assistance, it will be scored zero if the test using virtual machine system cannot be restarted or be properly restarted.
Corresponding distribution packages for the testing using operating system Red Hat Enterprise Linux version can be found in the following link:
http://server1.group3.example.com/rhel
Part of the requirements include host security, ensure your host security limit does not prevent the request to allow the host and network, although you correctly configured the network service but would have to allow the host or network is blocked, this also does not score.
You will notice that some requirements which clearly do not allow services be accessed by service domain my133t.org, systems of this domain are in subnet 172.25.1.0/252.255.255.0, and systems of these subnets also belong to my 133t.org domain.
PS: Notice that some test questions may depend on other exam questions, for example, you might be asked to perform a series of restrictions on a user, but this user creation may be required in other questions. For convenient identification, each exam question has some radio buttons to help you identify which questions you have already completed or not completed. Certainly, you do not need to care these buttons if you don’t need them.
Configure Multi-User SMB Mounts.
Share the directory /devops through SMB on the systeml, as required:
1. The share name is devops
2. The shared directory devops just can be used by clients in domain11.example.com
3. The shared directory devop must be able to be browsed
4. User silene must be able to access this share through read, access code is redhat
5. User akira must be able to access this share through read and write, access code is redhat
6. This share permanently mount to system2. domain11.example.com the user /mnt/dev, make user silene as authentication any users can get temporary write permissions from akira
There were two systems:
- system1, main system on which most of the configuration take place
- system2, some configuration here
Script2.
- Create a script on serverX called /root/createusers
- When this script is called with the argument, it should add all the users from the file
- Download the file from station.network0.example.c">http://station.network0.example.com/pub/testfile
- All users should have the login shell as /bin/false, password not required
- When this script is called with any other argument, it should print the message as “Input File Not Foundâ€
- When this script is run without any argument, it should display “Usage:/root/createusersâ€
- NOTE: if the users are added no need to delete
There were two systems:
- system1, main system on which most of the configuration take place
- system2, some configuration here
Virtual hosting.
- Setup a virtual host with an alternate document root.
- Extend your web to include a virtual for the site vhostsX.example.com">http://vhostsX.example.com
- Set the document root as /usr/local/vhosts
- Download station.network0.example.com/pub/rhce/vhost/html">http://station.network0.example.com/pub/rhce/vhost/html
- Rename it as index.html
- Place this document root of the virtual host
- Note: the other websites configures for your server must still accessible. vhosts.networkX.example.com is already provided by the name server on example.com
There were two systems:
- system1, main system on which most of the configuration take place
- system2, some configuration here
Script1.
- Create a script on serverX called /root/random with the following details
- When run as /root/random postconf, should bring the output as “postrollâ€
- When run as /root/random postroll, should bring the output as “postconfâ€
- When run with any other argument or without argument, should bring any other argument or without argument, should bring the stderr as “/root/random postconf|postrollâ€
There were two systems:
- system1, main system on which most of the configuration take place
- system2, some configuration here
Configure IPv6 network.
- Configure eth0 with a static IPv6 addresses as follows
- Configure a Static IPv6 address in serverX as fddb:fe2a:ab1e::c0a8:64/64
- Configure a Static IPv6 address in desktopX as fddb:fe2a:ab1e::c0a8:02/64
- Both machines are able to communicate within the network fddb:fe2a:able/64
- The changes should be permanent even after the reboot
On ServerX:
On DesktopX:
