Question 340
A Linux administrator evaluates: A firewall migration from iptables to nftables needs proof that connection tracking and policy order still work. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A firewall migration from iptables to nftables needs proof that connection tracking and policy order still work), the acceptance evidence is: nft list ruleset and controlled new/established connection tests demonstrate the intended forwarding boundaries. This verifies the action (Design an nftables ruleset with appropriate state, interface and address matches; enable IP forwarding only for a documented routed use case.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Accepting unrestricted forwarding or dropping established return packets can either expose networks or break allowed flows.
The observed Linux condition is: A firewall migration from iptables to nftables needs proof that connection tracking and policy order still work. The recommended direct administrative response is: Design an nftables ruleset with appropriate state, interface and address matches; enable IP forwarding only for a documented routed use case. The relevant failure or security risk is: Accepting unrestricted forwarding or dropping established return packets can either expose networks or break allowed flows. Validate success with: nft list ruleset and controlled new/established connection tests demonstrate the intended forwarding boundaries.
Incorrect Answers
OpenSSH server key authentication and root login hardening (3.3) would demonstrate or implement: Disabling all authentication methods before testing keys can lock out administrators, while root password login enlarges exposure. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: nft list ruleset and controlled new/established connection tests demonstrate the intended forwarding boundaries.
SELinux context and boolean troubleshooting (3.3) addresses another technical failure: Changing enforcing to disabled hides the mislabeled resource and weakens access controls for unrelated services. The required paired action and test concerns Stateful nftables filtering and IP forwarding; a passing result for this alternative could leave that requirement unresolved.
PAM and SSSD identity authentication diagnosis (3.1) would demonstrate or implement: getent, id and controlled authentication tests identify the intended directory user and show permitted login under policy. The paired-answer requirement concerns Stateful nftables filtering and IP forwarding; this alternative does not provide the matching intervention and separate acceptance evidence.