Question 310
To apply differing Linux firewall rules to interfaces with different trust levels, which mechanism best fits?
- Fail2ban banning
- NFS export restrictions
- Firewalld zone policy
- Nftables stateful filtering
- Disable legacy rsh services
Explanation
Correct Answer
C:Zone associations group allowed services and exposure according to network context; the requested outcome is precisely to apply differing Linux firewall rules to interfaces with different trust levels.
Incorrect Answers
A:Log-driven response updates filtering rules after a threshold but must accommodate shared or spoofed sources; that is useful when the task is to temporarily block IPs showing repeated authentication failures in logs, not the stated requirement to apply differing Linux firewall rules to interfaces with different trust levels.
B:Export definitions control authorized hosts and mapping behavior; network segmentation adds another layer; a team would select it to allow only intended client hosts to mount a shared filesystem, which does not provide the particular result to apply differing Linux firewall rules to interfaces with different trust levels.
D:Connection tracking classifies existing sessions, simplifying default-deny host firewall design; applying it would serve permit established return traffic while rejecting unsolicited inbound flows without directly satisfying the goal to apply differing Linux firewall rules to interfaces with different trust levels.
E:Eliminating unauthenticated or weakly authenticated remote services shrinks unnecessary exposure; it addresses the different need to remove plaintext remote command protocols from Linux hosts, leaving the requested ability to apply differing Linux firewall rules to interfaces with different trust levels unresolved.
Question 311
To prevent remote administrators from accepting a counterfeit server silently, which measure best meets the requirement?
- Disable legacy rsh services
- Nftables stateful filtering
- SSH host-key verification
- NFS export restrictions
Explanation
Correct Answer
C:Validating the expected host key detects impersonation before sensitive interactive commands are exchanged; this choice fits the scenario because the team must prevent remote administrators from accepting a counterfeit server silently.
Incorrect Answers
A:Eliminating unauthenticated or weakly authenticated remote services shrinks unnecessary exposure; it could help someone trying to remove plaintext remote command protocols from Linux hosts, but the problem is instead to prevent remote administrators from accepting a counterfeit server silently.
B:Connection tracking classifies existing sessions, simplifying default-deny host firewall design; that is useful when the task is to permit established return traffic while rejecting unsolicited inbound flows, not the stated requirement to prevent remote administrators from accepting a counterfeit server silently.
D:Export definitions control authorized hosts and mapping behavior; network segmentation adds another layer; its operational purpose is to allow only intended client hosts to mount a shared filesystem, not to achieve the specific requirement to prevent remote administrators from accepting a counterfeit server silently.
Question 312
To correlate remote login successes and failures by source and user, what control should be selected?
- NFS export restrictions
- DNS resolver configuration audit
- SSHD authentication logging
- Nftables stateful filtering
Explanation
Correct Answer
C:Secure authentication records provide evidence of guessing and unexpected access patterns; this mechanism directly supports the requirement to correlate remote login successes and failures by source and user.
Incorrect Answers
A:Export definitions control authorized hosts and mapping behavior; network segmentation adds another layer; although relevant to allow only intended client hosts to mount a shared filesystem, it does not by itself achieve the required task to correlate remote login successes and failures by source and user.
B:Resolver settings and egress policy indicate whether lookup traffic follows monitored infrastructure; it could help someone trying to detect an endpoint using unexpected external DNS servers, but the problem is instead to correlate remote login successes and failures by source and user.
D:Connection tracking classifies existing sessions, simplifying default-deny host firewall design; a team would select it to permit established return traffic while rejecting unsolicited inbound flows, which does not provide the particular result to correlate remote login successes and failures by source and user.
Question 313
To temporarily block IPs showing repeated authentication failures in logs, which security control is most appropriate?
- SSHD authentication logging
- Fail2ban banning
- SSH host-key verification
- Disable legacy rsh services
Explanation
Correct Answer
B:Log-driven response updates filtering rules after a threshold but must accommodate shared or spoofed sources; it supplies the specific control needed to temporarily block IPs showing repeated authentication failures in logs.
Incorrect Answers
A:Secure authentication records provide evidence of guessing and unexpected access patterns; the outcome it supports is to correlate remote login successes and failures by source and user, whereas this scenario asks defenders to temporarily block IPs showing repeated authentication failures in logs.
C:Validating the expected host key detects impersonation before sensitive interactive commands are exchanged; it could help someone trying to prevent remote administrators from accepting a counterfeit server silently, but the problem is instead to temporarily block IPs showing repeated authentication failures in logs.
D:Eliminating unauthenticated or weakly authenticated remote services shrinks unnecessary exposure; that is useful when the task is to remove plaintext remote command protocols from Linux hosts, not the stated requirement to temporarily block IPs showing repeated authentication failures in logs.
Question 314
To remove plaintext remote command protocols from Linux hosts, what would a Linux systems administrator implement or use?
- Disable legacy rsh services
- DNS resolver configuration audit
- NFS export restrictions
- Fail2ban banning
Explanation
Correct Answer
A:Eliminating unauthenticated or weakly authenticated remote services shrinks unnecessary exposure; that is why it addresses the operational task to remove plaintext remote command protocols from Linux hosts.
Incorrect Answers
B:Resolver settings and egress policy indicate whether lookup traffic follows monitored infrastructure; the outcome it supports is to detect an endpoint using unexpected external DNS servers, whereas this scenario asks defenders to remove plaintext remote command protocols from Linux hosts.
C:Export definitions control authorized hosts and mapping behavior; network segmentation adds another layer; although relevant to allow only intended client hosts to mount a shared filesystem, it does not by itself achieve the required task to remove plaintext remote command protocols from Linux hosts.
D:Log-driven response updates filtering rules after a threshold but must accommodate shared or spoofed sources; it could help someone trying to temporarily block IPs showing repeated authentication failures in logs, but the problem is instead to remove plaintext remote command protocols from Linux hosts.
Question 315
To allow only intended client hosts to mount a shared filesystem, which practice addresses that objective?
- Chrony time-source validation
- NFS export restrictions
- Disable legacy rsh services
- Fail2ban banning
- NFS root squashing
Explanation
Correct Answer
B:Export definitions control authorized hosts and mapping behavior; network segmentation adds another layer; its relevant protective or investigative effect is to allow only intended client hosts to mount a shared filesystem.
Incorrect Answers
A:Trusted synchronization lowers timeline ambiguity in distributed event review; the technique works for situations involving preserve consistent timestamps among systems used for security correlation, rather than this need to allow only intended client hosts to mount a shared filesystem.
C:Eliminating unauthenticated or weakly authenticated remote services shrinks unnecessary exposure; the outcome it supports is to remove plaintext remote command protocols from Linux hosts, whereas this scenario asks defenders to allow only intended client hosts to mount a shared filesystem.
D:Log-driven response updates filtering rules after a threshold but must accommodate shared or spoofed sources; although relevant to temporarily block IPs showing repeated authentication failures in logs, it does not by itself achieve the required task to allow only intended client hosts to mount a shared filesystem.
E:Root squashing maps remote superuser requests to a less privileged anonymous identity; it could help someone trying to prevent remote client root identities from acting as server root on a share, but the problem is instead to allow only intended client hosts to mount a shared filesystem.
Question 316
To prevent remote client root identities from acting as server root on a share, which tool, policy, or technique is appropriate?
- NFS root squashing
- Disable legacy rsh services
- Chrony time-source validation
- TCP wrappers limitation
Explanation
Correct Answer
A:Root squashing maps remote superuser requests to a less privileged anonymous identity; the requested outcome is precisely to prevent remote client root identities from acting as server root on a share.
Incorrect Answers
B:Eliminating unauthenticated or weakly authenticated remote services shrinks unnecessary exposure; the technique works for situations involving remove plaintext remote command protocols from Linux hosts, rather than this need to prevent remote client root identities from acting as server root on a share.
C:Trusted synchronization lowers timeline ambiguity in distributed event review; its mechanism supports preserve consistent timestamps among systems used for security correlation, while the requested control must be able to prevent remote client root identities from acting as server root on a share.
D:Legacy libwrap checks apply only where applications still link them and are not a universal host filter; the outcome it supports is to avoid relying on obsolete service-specific access libraries as a firewall, whereas this scenario asks defenders to prevent remote client root identities from acting as server root on a share.
Question 317
To detect an endpoint using unexpected external DNS servers, what safeguard would be most applicable?
- Chrony time-source validation
- DNS resolver configuration audit
- TCP wrappers limitation
- Fail2ban banning
Explanation
Correct Answer
B:Resolver settings and egress policy indicate whether lookup traffic follows monitored infrastructure; this choice fits the scenario because the team must detect an endpoint using unexpected external DNS servers.
Incorrect Answers
A:Trusted synchronization lowers timeline ambiguity in distributed event review; applying it would serve preserve consistent timestamps among systems used for security correlation without directly satisfying the goal to detect an endpoint using unexpected external DNS servers.
C:Legacy libwrap checks apply only where applications still link them and are not a universal host filter; the technique works for situations involving avoid relying on obsolete service-specific access libraries as a firewall, rather than this need to detect an endpoint using unexpected external DNS servers.
D:Log-driven response updates filtering rules after a threshold but must accommodate shared or spoofed sources; its mechanism supports temporarily block IPs showing repeated authentication failures in logs, while the requested control must be able to detect an endpoint using unexpected external DNS servers.
Question 318
To preserve consistent timestamps among systems used for security correlation, what is the relevant defensive action?
- Chrony time-source validation
- NFS root squashing
- Disable legacy rsh services
- SSHD authentication logging
Explanation
Correct Answer
A:Trusted synchronization lowers timeline ambiguity in distributed event review; this mechanism directly supports the requirement to preserve consistent timestamps among systems used for security correlation.
Incorrect Answers
B:Root squashing maps remote superuser requests to a less privileged anonymous identity; applying it would serve prevent remote client root identities from acting as server root on a share without directly satisfying the goal to preserve consistent timestamps among systems used for security correlation.
C:Eliminating unauthenticated or weakly authenticated remote services shrinks unnecessary exposure; it addresses the different need to remove plaintext remote command protocols from Linux hosts, leaving the requested ability to preserve consistent timestamps among systems used for security correlation unresolved.
D:Secure authentication records provide evidence of guessing and unexpected access patterns. This can help to correlate remote login successes and failures by source and user, but it does not provide the particular mechanism required to preserve consistent timestamps among systems used for security correlation.
Question 319
To detect an endpoint using unexpected external DNS servers, to preserve consistent timestamps among systems used for security correlation, and to avoid relying on obsolete service-specific access libraries as a firewall, which THREE measures should the team select? Choose THREE.
- TCP wrappers limitation
- Chrony time-source validation
- DNS resolver configuration audit
- NFS root squashing
- NFS export restrictions
- Disable legacy rsh services
Explanation
Correct Answers
A:Legacy libwrap checks apply only where applications still link them and are not a universal host filter; its contribution to the combined design is specifically to avoid relying on obsolete service-specific access libraries as a firewall.
B:Trusted synchronization lowers timeline ambiguity in distributed event review; its contribution to the combined design is specifically to preserve consistent timestamps among systems used for security correlation.
C:Resolver settings and egress policy indicate whether lookup traffic follows monitored infrastructure; its contribution to the combined design is specifically to detect an endpoint using unexpected external DNS servers.
Incorrect Answers
D:Root squashing maps remote superuser requests to a less privileged anonymous identity; it addresses the different need to prevent remote client root identities from acting as server root on a share, leaving the requested ability to detect an endpoint using unexpected external DNS servers, to preserve consistent timestamps among systems used for security correlation, and to avoid relying on obsolete service-specific access libraries as a firewall unresolved.
E:Export definitions control authorized hosts and mapping behavior; network segmentation adds another layer; the technique works for situations involving allow only intended client hosts to mount a shared filesystem, rather than this need to detect an endpoint using unexpected external DNS servers, to preserve consistent timestamps among systems used for security correlation, and to avoid relying on obsolete service-specific access libraries as a firewall.
F:Eliminating unauthenticated or weakly authenticated remote services shrinks unnecessary exposure; its mechanism supports remove plaintext remote command protocols from Linux hosts, while the requested control must be able to detect an endpoint using unexpected external DNS servers, to preserve consistent timestamps among systems used for security correlation, and to avoid relying on obsolete service-specific access libraries as a firewall.
Question 320
To retain systemd service records across an unexpected machine reboot, which option most directly provides the capability?
- Bash history limitations
- Logrotate configuration
- Journald persistent storage
- Process accounting deployment
- Sudo I/O logging
Explanation
Correct Answer
C:Persistent journal configuration keeps collected entries on disk subject to storage and access policy; that is why it addresses the operational task to retain systemd service records across an unexpected machine reboot.
Incorrect Answers
A:Interactive shell histories may be modified or disabled and do not capture every process execution; that is useful when the task is to avoid relying on shell history as a complete privileged-command audit, not the stated requirement to retain systemd service records across an unexpected machine reboot.
B:Rotation and retention policies manage storage while respecting forensic and compliance requirements; a team would select it to prevent continuously growing logs from exhausting a server's filesystem, which does not provide the particular result to retain systemd service records across an unexpected machine reboot.
D:Kernel process accounting retains command execution summaries for review when enabled and safeguarded; applying it would serve record which executable names users launched even outside interactive shell history without directly satisfying the goal to retain systemd service records across an unexpected machine reboot.
E:When configured, sudo can retain input and output evidence useful for reconstructing sensitive changes; it addresses the different need to record privileged interactive sessions with contextual attribution, leaving the requested ability to retain systemd service records across an unexpected machine reboot unresolved.