The task calls for a permanent rich rule scoped to the 'public' zone that combines four elements:
priority=10 to set a specific evaluation order (lower numbers have higher precedence).
family="ipv4" plus source address="192.0.2.0/24" to match only the specified network.
service name="httpss" to match TCP port 443.
log prefix="https_in" level="info" followed by accept to allow and log the traffic.
Only the first command includes every element in the right context and syntax inside a single rich-rule string and uses the --permanent switch so the rule survives a reload.
The second command places accept before log; this violates the rich-rule grammar, as the action must be the final element, and will be rejected by firewalld.
The third command omits both --permanent and priority=10, so the rule is not persistent and is not prioritized as requested.
The fourth command uses separate options like --add-service and --source, which cannot be combined with custom logging prefixes, levels, or priority settings in a single command, so it cannot satisfy all requirements.
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 firewalld and how does it differ from iptables?
Open an interactive chat with Bash
What is a rich rule in firewalld?
Open an interactive chat with Bash
Why is the 'priority=10' parameter important in firewalld rich rules?
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