A systems administrator configured firewall rules using firewalld. However, after the system is rebooted, the firewall rules are not present: The systems administrator makes additional checks: Which…

The correct answer is D. The firewalld service is not enabled. The reason the firewall rules are not active is that the firewalld service is not enabled. This means that the service will not start automatically at boot time or after a system reload. To enable the firewalld service, the systems administrator needs to use the command sudo…

System Management

Question

A systems administrator configured firewall rules using firewalld. However, after the system is rebooted, the firewall rules are not present:

The systems administrator makes additional checks:

Which of the following is the reason the firewall rules are not active?

Options

Aiptables is conflicting with firewalld.
BThe wrong system target is activated.
CFIREWALL_ARGS has no value assigned.
DThe firewalld service is not enabled.

How the community answered

(34 responses)

A
3% (1)
B
3% (1)
C
9% (3)
D
85% (29)

Explanation

The reason the firewall rules are not active is that the firewalld service is not enabled. This means that the service will not start automatically at boot time or after a system reload. To enable the firewalld service, the systems administrator needs to use the command sudo systemct1 enable firewalld. This will create a symbolic link from the firewalld service file to the appropriate systemd target, such as multi-user.target. Enabling the service does not start it immediately, so the systems administrator also needs to use the command sudo systemct1 start firewalld or sudo systemct1 reload firewalld to activate the firewall rules.

Topics

#firewalld#systemd#Service management#Firewall persistence

Community Discussion

No community discussion yet for this question.

Full XK0-005 Practice