Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

RedHat EX200 Exam - Topic 1 Question 70 Discussion

Part 1 (on Node1 Server)Task 14 [Managing SELinux Security]You will configure a web server running on your system serving content using a non-standard port (82)
A) Explanation: * [root@node1 ~]# curl http://node1.domain15.example.com curl: (7) Failed to connect to node1.domain15.example.com port 80: Connection refused [root@node1 ~]# yum install httpd [root@node1 ~]# systemctl enable --now httpd Created symlink /etc/systemd/system/multi-user.target.wants/httpd.service /usr/lib/systemd/system/httpd.service. [root@node1 ~]# systemctl start httpd [root@node1 ~]# systemctl status httpd Status: 'Running, listening on: port 80' * [root@node1 ~]# wget http://node1.domain15.example.com 2021-03-23 13:27:28 ERROR 403: Forbidden. [root@node1 ~]# semanage port -l | grep http http_port_t tcp 80, 81, 443, 488, 8008, 8009, 8443, 9000 [root@node1 ~]# semanage port -a -t http_port_t -p tcp 82 [root@node1 ~]# semanage port -l | grep http http_port_t tcp 82, 80, 81, 443, 488, 8008, 8009, 8443, 9000 [root@node1 ~]# firewall-cmd --zone=public --list-all [root@node1 ~]# firewall-cmd --permanent --zone=public --add-port=82/tcp [root@node1 ~]# firewall-cmd --reload [root@node1 ~]# curl http://node1.domain15.example.com OK * root@node1 ~]# wget http://node1.domain15.example.com:82 Connection refused. [root@node1 ~]# vim /etc/httpd/conf/httpd.conf Listen 82 [root@node1 ~]# systemctl restart httpd [root@node1 ~]# wget http://node1.domain15.example.com:82 2021-03-23 13:31:41 ERROR 403: Forbidden. [root@node1 ~]# curl http://node1.domain15.example.com:82 OK

RedHat EX200 Exam - Topic 1 Question 70 Discussion

Actual exam question for RedHat's EX200 exam
Question #: 70
Topic #: 1
[All EX200 Questions]

Part 1 (on Node1 Server)

Task 14 [Managing SELinux Security]

You will configure a web server running on your system serving content using a non-standard port (82)

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Lauran
8 months ago
I thought httpd only listens on standard ports by default?
upvoted 0 times
...
Katina
8 months ago
Just make sure your firewall allows port 82 too!
upvoted 0 times
...
Elza
9 months ago
Wait, why is it still giving a 403 error after changing the port?
upvoted 0 times
...
Thora
9 months ago
Totally agree, SELinux can be tricky with non-standard ports!
upvoted 0 times
...
Rebbecca
9 months ago
You need to add port 82 to SELinux for http.
upvoted 0 times
...
Lashaunda
9 months ago
I practiced adding firewall rules before, and I think I need to use `firewall-cmd` to allow traffic on port 82, but I hope I don't forget to reload the firewall.
upvoted 0 times
...
Nicolette
9 months ago
I definitely remember that we had to modify the `httpd.conf` file to listen on the new port, but I’m a bit uncertain about the exact syntax.
upvoted 0 times
...
Dominque
9 months ago
I think I recall needing to use `semanage` to add the non-standard port, but I might mix up the commands.
upvoted 0 times
...
Marica
9 months ago
I remember we had a similar practice question about configuring SELinux for a web server, but I’m not sure if I got the port settings right.
upvoted 0 times
...
Christa
9 months ago
Okay, let me see... The question mentions the FHS, so I'm guessing the answer has to do with the Filesystem Hierarchy Standard. I think /usr/share/doc is the right answer, but I'll double-check the FHS to be sure.
upvoted 0 times
...
Trina
9 months ago
Hmm, this is a tricky one. I'm not entirely sure about the differences between preventive, detective, and predictive capabilities. I'll need to review my notes to refresh my memory on those concepts.
upvoted 0 times
...
Charlena
10 months ago
Hmm, the query output provides a lot of useful information, but I'm not sure I fully understand how to interpret it. I'll need to review the query plan and execution details to make the right choices.
upvoted 0 times
...
Lisha
10 months ago
This looks like a good opportunity to apply my knowledge of Cisco firewall configuration. I'll carefully consider each option and try to eliminate the ones that don't seem correct.
upvoted 0 times
...

Save Cancel