SIMULATION

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.5system2.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 Security Web Service

Configure a TLS encryption for the site http://systeml.domain11.example.com, encrypt/, get a signed certificate from http://host.domain11.example.com/materials/system1.crt. Get the certificate key from http://host.domain11.example.com/materials/system1.key. Get the signature authorization information of the certificate from http://host.domain11.example.com/materials/domain11.crt

SIMULATION

According to the following requirements, deploy your ftp login rule:

Users in example.com domain must be able to login to your ftp server as an anonymous user.

But users outside the example.com domain are unable to login to your server

SIMULATION

One Logical Volume is created named as myvol under vo volume group and is mounted. The Initial Size of that Logical Volume is 400MB. Make successfully that the size of Logical Volume 200MB without losing any data. The size of logical volume 200MB to 210MB will be acceptable.

SIMULATION

Install the Cron Schedule for jeff user to display "Hello" on daily 5:30.

SIMULATION

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”