Question 200
An SSH server receives repeated failed login attempts from a small number of addresses and needs short-term automated blocking. Which Linux network protection should be deployed?
- Fail2ban service protection
- Nftables packet filtering
- Tcpdump capture
- Reverse-path filtering
- Disable IP forwarding
Explanation
Correct Answer
A:Fail2ban parses service logs and applies temporary bans through firewall actions according to jail rules. It complements strong authentication.
Incorrect Answers
B:Nftables defines kernel packet-filtering and translation rules; it handles Linux host packet filter policy, while the decisive evidence in the question is log-triggered temporary IP bans.
C:Tcpdump records interface traffic using capture filters for focused examination in a setting defined by direct inspection of interface packets; the observed issue is log-triggered temporary IP bans.
D:Reverse-path checks compare the incoming interface with routing expectations for a claimed source when analysts encounter rejection of implausible source paths; this question instead describes log-triggered temporary IP bans.
E:Disabling kernel IP forwarding prevents routine transit routing through a host when analysts encounter unwanted packet forwarding between interfaces; this question instead describes log-triggered temporary IP bans.
Question 201
A daemon fails shortly after boot, and staff want its structured messages and unit-associated errors for a specific time window. Which Linux logging and process-monitoring action resolves the evidence gap?
- Journalctl service investigation
- Open socket enumeration
- Persistent journald storage
- Rsyslog remote forwarding
Explanation
Correct Answer
A:Journalctl queries systemd journal records by unit, time and priority where journald is in use. Persistent storage must be configured if history is needed.
Incorrect Answers
B:Tools such as ss report local TCP and UDP sockets and associated processes with suitable privileges when analysts encounter socket-to-process relationship inspection; this question instead describes systemd service logs by time.
C:Persistent journald storage retains journal data across reboots subject to configured size and rotation controls; this characterizes retention of logs across restarts, whereas the reported condition is systemd service logs by time.
D:Rsyslog can forward selected messages to a remote system using authenticated encrypted transport when configured for situations characterized by off-host copies of Linux system logs; the case points instead to systemd service logs by time.
Question 202
Rebooting a server erases event history that responders need to reconstruct an intermittent compromise. Which Linux logging and process-monitoring action resolves the evidence gap?
- Persistent journald storage
- Rsyslog remote forwarding
- Open socket enumeration
- Journalctl service investigation
Explanation
Correct Answer
A:Persistent journald storage retains journal data across reboots subject to configured size and rotation controls. Off-host forwarding provides stronger resilience.
Incorrect Answers
B:Rsyslog can forward selected messages to a remote system using authenticated encrypted transport when configured; its distinguishing scope is off-host copies of Linux system logs, not the reported retention of logs across restarts.
C:Tools such as ss report local TCP and UDP sockets and associated processes with suitable privileges in a setting defined by socket-to-process relationship inspection; the observed issue is retention of logs across restarts.
D:Journalctl queries systemd journal records by unit, time and priority where journald is in use in a setting defined by systemd service logs by time; the observed issue is retention of logs across restarts.
Question 203
Investigators worry that an attacker with root privileges can erase local logs and want contemporaneous copies at a central collector. In a separate workstream, the team must also handle socket-to-process relationship inspection. Which TWO of the listed methods or controls correspond to these distinct requirements? Choose TWO.
- Open socket enumeration
- Persistent journald storage
- Process-accounting evidence
- Rsyslog remote forwarding
Explanation
Correct Answers
A:Tools such as ss report local TCP and UDP sockets and associated processes with suitable privileges; this specifically explains socket-to-process relationship inspection among the independent requirements in the combined case.
D:Rsyslog can forward selected messages to a remote system using authenticated encrypted transport when configured; for this multi-part scenario, the pertinent observation is off-host copies of Linux system logs.
Incorrect Answers
B:Persistent journald storage retains journal data across reboots subject to configured size and rotation controls when the underlying evidence concerns retention of logs across restarts rather than the stated off-host copies of Linux system logs and socket-to-process relationship inspection.
C:Linux process-accounting facilities can record executed commands and usage when enabled, though details and coverage are limited; the operational difference is historical executed-command accounting versus the scenario's off-host copies of Linux system logs and socket-to-process relationship inspection.
Question 204
Auditors need a record of commands executed by users even when interactive shell history is cleared. Which Linux logging and process-monitoring action resolves the evidence gap?
- Persistent journald storage
- Open socket enumeration
- Rsyslog remote forwarding
- Process-accounting evidence
Explanation
Correct Answer
D:Linux process-accounting facilities can record executed commands and usage when enabled, though details and coverage are limited. Auditd may provide richer context.
Incorrect Answers
A:Persistent journald storage retains journal data across reboots subject to configured size and rotation controls when the underlying evidence concerns retention of logs across restarts rather than the stated historical executed-command accounting.
B:Tools such as ss report local TCP and UDP sockets and associated processes with suitable privileges; its distinguishing scope is socket-to-process relationship inspection, not the reported historical executed-command accounting.
C:Rsyslog can forward selected messages to a remote system using authenticated encrypted transport when configured when the underlying evidence concerns off-host copies of Linux system logs rather than the stated historical executed-command accounting.
Question 205
An endpoint's telemetry shows unexplained outbound connections, and the admin needs to map listening sockets and connections to processes. Which Linux logging and process-monitoring action resolves the evidence gap?
- Journalctl service investigation
- Rsyslog remote forwarding
- Persistent journald storage
- Open socket enumeration
- Process-accounting evidence
Explanation
Correct Answer
D:Tools such as ss report local TCP and UDP sockets and associated processes with suitable privileges. They reveal runtime exposure rather than firewall intent.
Incorrect Answers
A:Journalctl queries systemd journal records by unit, time and priority where journald is in use in a setting defined by systemd service logs by time; the observed issue is socket-to-process relationship inspection.
B:Rsyslog can forward selected messages to a remote system using authenticated encrypted transport when configured when the underlying evidence concerns off-host copies of Linux system logs rather than the stated socket-to-process relationship inspection.
C:Persistent journald storage retains journal data across reboots subject to configured size and rotation controls; that is relevant to retention of logs across restarts but does not directly account for socket-to-process relationship inspection.
E:Linux process-accounting facilities can record executed commands and usage when enabled, though details and coverage are limited; it handles historical executed-command accounting, while the decisive evidence in the question is socket-to-process relationship inspection.
Question 206
Attackers attempt to load an unauthorized bootloader before the Linux kernel starts, undermining operating-system integrity. Which Linux boot or persistence safeguard most directly addresses the issue?
- Restricted bootloader editing
- Kernel module loading restrictions
- UEFI Secure Boot
- Full-disk encryption with LUKS
Explanation
Correct Answer
C:Secure Boot verifies signed boot components against trusted keys when properly configured. Its chain must include the relevant boot stages.
Incorrect Answers
A:Bootloader access controls and physical security can restrict unauthorized changes to boot parameters when analysts encounter unauthorized kernel command-line alteration; this question instead describes verification of boot-time executable trust.
B:Kernel module restrictions reduce opportunities for runtime kernel extension when the underlying evidence concerns prevention of late arbitrary kernel modules rather than the stated verification of boot-time executable trust.
D:LUKS protects block-device contents with encryption and managed unlocking secrets for situations characterized by confidentiality of powered-off Linux storage; the case points instead to verification of boot-time executable trust.
Question 207
A decommissioned Linux laptop could be stolen while powered off and contains sensitive data in its root filesystem. Which Linux boot or persistence safeguard most directly addresses the issue?
- Full-disk encryption with LUKS
- Immutable configuration deployment
- Restricted bootloader editing
- Kernel module loading restrictions
Explanation
Correct Answer
A:LUKS protects block-device contents with encryption and managed unlocking secrets. Live systems can still expose decrypted data to authorized processes.
Incorrect Answers
B:Immutable or image-based deployment rebuilds from a controlled baseline, reducing configuration drift and persistence opportunities; the operational difference is restoration of vetted baseline at restart versus the scenario's confidentiality of powered-off Linux storage.
C:Bootloader access controls and physical security can restrict unauthorized changes to boot parameters; its distinguishing scope is unauthorized kernel command-line alteration, not the reported confidentiality of powered-off Linux storage.
D:Kernel module restrictions reduce opportunities for runtime kernel extension; that is relevant to prevention of late arbitrary kernel modules but does not directly account for confidentiality of powered-off Linux storage.
Question 208
Physical users can edit kernel boot arguments to enter a rescue mode that bypasses normal login controls. Which Linux boot or persistence safeguard most directly addresses the issue?
- Immutable configuration deployment
- Restricted bootloader editing
- UEFI Secure Boot
- Full-disk encryption with LUKS
Explanation
Correct Answer
B:Bootloader access controls and physical security can restrict unauthorized changes to boot parameters. Encryption may be needed against offline modification.
Incorrect Answers
A:Immutable or image-based deployment rebuilds from a controlled baseline, reducing configuration drift and persistence opportunities; the operational difference is restoration of vetted baseline at restart versus the scenario's unauthorized kernel command-line alteration.
C:Secure Boot verifies signed boot components against trusted keys when properly configured; it handles verification of boot-time executable trust, while the decisive evidence in the question is unauthorized kernel command-line alteration.
D:LUKS protects block-device contents with encryption and managed unlocking secrets when the underlying evidence concerns confidentiality of powered-off Linux storage rather than the stated unauthorized kernel command-line alteration.
Question 209
A hardened appliance should not accept arbitrary kernel modules after initialization because malicious modules could extend privileged code. Which Linux boot or persistence safeguard most directly addresses the issue?
- UEFI Secure Boot
- Full-disk encryption with LUKS
- Immutable configuration deployment
- Kernel module loading restrictions
Explanation
Correct Answer
D:Kernel module restrictions reduce opportunities for runtime kernel extension. Verify required drivers are loaded before enforcing strict policies.
Incorrect Answers
A:Secure Boot verifies signed boot components against trusted keys when properly configured when analysts encounter verification of boot-time executable trust; this question instead describes prevention of late arbitrary kernel modules.
B:LUKS protects block-device contents with encryption and managed unlocking secrets; this characterizes confidentiality of powered-off Linux storage, whereas the reported condition is prevention of late arbitrary kernel modules.
C:Immutable or image-based deployment rebuilds from a controlled baseline, reducing configuration drift and persistence opportunities when analysts encounter restoration of vetted baseline at restart; this question instead describes prevention of late arbitrary kernel modules.
Question 210
Linux kiosks must return to a vetted system configuration after each restart rather than accumulating untracked local administrator edits. Which Linux boot or persistence safeguard most directly addresses the issue?
- Restricted bootloader editing
- Full-disk encryption with LUKS
- Immutable configuration deployment
- UEFI Secure Boot
- Kernel module loading restrictions
Explanation
Correct Answer
C:Immutable or image-based deployment rebuilds from a controlled baseline, reducing configuration drift and persistence opportunities. State and updates need planned handling.
Incorrect Answers
A:Bootloader access controls and physical security can restrict unauthorized changes to boot parameters for situations characterized by unauthorized kernel command-line alteration; the case points instead to restoration of vetted baseline at restart.
B:LUKS protects block-device contents with encryption and managed unlocking secrets when the underlying evidence concerns confidentiality of powered-off Linux storage rather than the stated restoration of vetted baseline at restart.
D:Secure Boot verifies signed boot components against trusted keys when properly configured for situations characterized by verification of boot-time executable trust; the case points instead to restoration of vetted baseline at restart.
E:Kernel module restrictions reduce opportunities for runtime kernel extension; its distinguishing scope is prevention of late arbitrary kernel modules, not the reported restoration of vetted baseline at restart.