Professional Documents
Culture Documents
Rhce Exam V6
Rhce Exam V6
make sure that both servers have an operational firewall that is allowing access to all
services mentioned in this test exam.
1. Configure server1 to offer the contents of the /repo directory as a reposi-
tory, using an FTP server. Configure server1 and server2 to use the
repository that is offered on server1.
2. Set up both servers to authenticate using Kerberos against the labipa.
example.com server. A CA certificate is available in the home directory of
the root user on the labipa server. To test successful setup, you can use the
LDAP user lisa on the labipa server.
3. Set up a Kerberized NFS share on server1. The directory /srv/secure
should be shared and secured with the best possible Kerberos security
settings. A keytab file is available on the labipa.example.com server in the
/var/ftp/pub directory.
4. On server2, configure a mount to the Kerberized NFS share on server1.
The mount should be made automatically on the /mnt/secure directory
when the server boots.
5. Configure an Apache web server. Two virtual hosts should be configured:
sales.example.com and account.example.com. Create a documentroot for
these servers in /web/account and /web/sales. In the document root, cre-
ate an index.html file containing the text “this is the sales webserver” or
“this is the account webserver.”
6. Secure the Apache web server sales.example.com virtual host. It should
only be accessible to user florence, using the password password. This
user account has to be used for Apache authentication only and does not
have to be created in any other way.
7. Write a script and give it the name /root/foobar. The script should offer
support for two different parameters when launched. When using the
parameter foo, it should create the file /tmp/foo; when using the param-
eter bar, it should create the file /tmp/bar. When using any other param-
eter, it should show an error message explaining to the user who launched
it that an unsupported parameter was used.
8. Enable packet forwarding on server1.
9. Set up both servers with an aggregated network interface and make sure
the IP addresses of the servers bind to these interfaces. You may use
bonding or teaming at your convenience.
On server2, set up a caching only DNS name server. This name server
10.
should forward all DNS requests to labipa.example.com.