A CentOS Stream 9 host is protected by firewalld. You have temporarily opened TCP port 8080 in the current ruleset to test a new micro-service. The test is successful, and you now need the rule to survive future reboots without replacing the active rules in the kernel (that is, you do not want to reload or restart firewalld). Which pair of commands satisfies these requirements?
The first command adds the rule to the runtime configuration, making it effective immediately. The second command copies the entire runtime configuration into the permanent XML files, ensuring the rule is retained when firewalld is restarted at the next boot. Because no reload or restart occurs, the running ruleset remains untouched except for the port that was just opened. The other choices all fail at least one requirement: adding --permanent alone does not affect the runtime rules; adding --permanent followed by reload replaces the current ruleset; restarting firewalld discards any runtime-only changes.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is the difference between runtime and permanent configurations in firewalld?
Open an interactive chat with Bash
Why is reloading or restarting firewalld not ideal in this scenario?
Open an interactive chat with Bash
What happens if you only use the --permanent option with firewall-cmd?
Open an interactive chat with Bash
CompTIA Linux+ XK0-006 (V8)
Security
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access