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.
Question 321
To send Linux security events to a protected centralized collection server, which control achieves the target outcome?
- Journald persistent storage
- Rsyslog remote forwarding
- Sudo I/O logging
- Bash history limitations
Explanation
Correct Answer
B:Network log shipping preserves accessible evidence when a local system is compromised or wiped; its relevant protective or investigative effect is to send Linux security events to a protected centralized collection server.
Incorrect Answers
A:Persistent journal configuration keeps collected entries on disk subject to storage and access policy; it could help someone trying to retain systemd service records across an unexpected machine reboot, but the problem is instead to send Linux security events to a protected centralized collection server.
C:When configured, sudo can retain input and output evidence useful for reconstructing sensitive changes; a team would select it to record privileged interactive sessions with contextual attribution, which does not provide the particular result to send Linux security events to a protected centralized collection server.
D:Interactive shell histories may be modified or disabled and do not capture every process execution; its operational purpose is to avoid relying on shell history as a complete privileged-command audit, not to achieve the specific requirement to send Linux security events to a protected centralized collection server.
Question 322
To prevent continuously growing logs from exhausting a server's filesystem, which solution should be adopted?
- Logrotate configuration
- Process accounting deployment
- Crontab persistence review
- Journald persistent storage
Explanation
Correct Answer
A:Rotation and retention policies manage storage while respecting forensic and compliance requirements; the requested outcome is precisely to prevent continuously growing logs from exhausting a server's filesystem.
Incorrect Answers
B:Kernel process accounting retains command execution summaries for review when enabled and safeguarded; it could help someone trying to record which executable names users launched even outside interactive shell history, but the problem is instead to prevent continuously growing logs from exhausting a server's filesystem.
C:Cron schedules launch periodic activity that may represent legitimate maintenance or attacker persistence; that is useful when the task is to identify unexpected scheduled commands running under service accounts, not the stated requirement to prevent continuously growing logs from exhausting a server's filesystem.
D:Persistent journal configuration keeps collected entries on disk subject to storage and access policy; a team would select it to retain systemd service records across an unexpected machine reboot, which does not provide the particular result to prevent continuously growing logs from exhausting a server's filesystem.
Question 323
To avoid relying on shell history as a complete privileged-command audit, which of the available controls is suitable?
- Core dump privacy controls
- Sudo I/O logging
- Process accounting deployment
- Bash history limitations
- Systemd unit persistence audit
- Rsyslog remote forwarding
Explanation
Correct Answer
D:Interactive shell histories may be modified or disabled and do not capture every process execution; this choice fits the scenario because the team must avoid relying on shell history as a complete privileged-command audit.
Incorrect Answers
A:Core-dump limits reduce storage exposure of credentials and in-process confidential material; the outcome it supports is to prevent application memory containing secrets from being written broadly to disk, whereas this scenario asks defenders to avoid relying on shell history as a complete privileged-command audit.
B:When configured, sudo can retain input and output evidence useful for reconstructing sensitive changes; although relevant to record privileged interactive sessions with contextual attribution, it does not by itself achieve the required task to avoid relying on shell history as a complete privileged-command audit.
C:Kernel process accounting retains command execution summaries for review when enabled and safeguarded; it could help someone trying to record which executable names users launched even outside interactive shell history, but the problem is instead to avoid relying on shell history as a complete privileged-command audit.
E:Unit file creation and enablement can provide persistence independent of user crontabs; a team would select it to find an unauthorized daemon enabled to restart after boot, which does not provide the particular result to avoid relying on shell history as a complete privileged-command audit.
F:Network log shipping preserves accessible evidence when a local system is compromised or wiped; its operational purpose is to send Linux security events to a protected centralized collection server, not to achieve the specific requirement to avoid relying on shell history as a complete privileged-command audit.
Question 324
To record which executable names users launched even outside interactive shell history, which option is the direct technical match?
- Rsyslog remote forwarding
- Sudo I/O logging
- Process accounting deployment
- Crontab persistence review
Explanation
Correct Answer
C:Kernel process accounting retains command execution summaries for review when enabled and safeguarded; this mechanism directly supports the requirement to record which executable names users launched even outside interactive shell history.
Incorrect Answers
A:Network log shipping preserves accessible evidence when a local system is compromised or wiped; its mechanism supports send Linux security events to a protected centralized collection server, while the requested control must be able to record which executable names users launched even outside interactive shell history.
B:When configured, sudo can retain input and output evidence useful for reconstructing sensitive changes; the outcome it supports is to record privileged interactive sessions with contextual attribution, whereas this scenario asks defenders to record which executable names users launched even outside interactive shell history.
D:Cron schedules launch periodic activity that may represent legitimate maintenance or attacker persistence; it could help someone trying to identify unexpected scheduled commands running under service accounts, but the problem is instead to record which executable names users launched even outside interactive shell history.
Question 325
To record privileged interactive sessions with contextual attribution, which approach should a Linux systems administrator choose?
- Sudo I/O logging
- Bash history limitations
- Logrotate configuration
- LUKS full-disk encryption
- Rsyslog remote forwarding
Explanation
Correct Answer
A:When configured, sudo can retain input and output evidence useful for reconstructing sensitive changes; it supplies the specific control needed to record privileged interactive sessions with contextual attribution.
Incorrect Answers
B:Interactive shell histories may be modified or disabled and do not capture every process execution; its mechanism supports avoid relying on shell history as a complete privileged-command audit, while the requested control must be able to record privileged interactive sessions with contextual attribution.
C:Rotation and retention policies manage storage while respecting forensic and compliance requirements; the outcome it supports is to prevent continuously growing logs from exhausting a server's filesystem, whereas this scenario asks defenders to record privileged interactive sessions with contextual attribution.
D:Volume encryption protects offline data when key handling and unlock procedures remain secure; although relevant to protect a Linux laptop's filesystem after physical device theft, it does not by itself achieve the required task to record privileged interactive sessions with contextual attribution.
E:Network log shipping preserves accessible evidence when a local system is compromised or wiped; it could help someone trying to send Linux security events to a protected centralized collection server, but the problem is instead to record privileged interactive sessions with contextual attribution.
Question 326
To find an unauthorized daemon enabled to restart after boot, which method is designed for the task?
- Systemd unit persistence audit
- Crontab persistence review
- LUKS full-disk encryption
- Core dump privacy controls
Explanation
Correct Answer
A:Unit file creation and enablement can provide persistence independent of user crontabs; that is why it addresses the operational task to find an unauthorized daemon enabled to restart after boot.
Incorrect Answers
B:Cron schedules launch periodic activity that may represent legitimate maintenance or attacker persistence; the technique works for situations involving identify unexpected scheduled commands running under service accounts, rather than this need to find an unauthorized daemon enabled to restart after boot.
C:Volume encryption protects offline data when key handling and unlock procedures remain secure; its mechanism supports protect a Linux laptop's filesystem after physical device theft, while the requested control must be able to find an unauthorized daemon enabled to restart after boot.
D:Core-dump limits reduce storage exposure of credentials and in-process confidential material; the outcome it supports is to prevent application memory containing secrets from being written broadly to disk, whereas this scenario asks defenders to find an unauthorized daemon enabled to restart after boot.
Question 327
To identify unexpected scheduled commands running under service accounts, what technique should the team use?
- Sudo I/O logging
- Bash history limitations
- Crontab persistence review
- Rescue-mode authentication
Explanation
Correct Answer
C:Cron schedules launch periodic activity that may represent legitimate maintenance or attacker persistence; its relevant protective or investigative effect is to identify unexpected scheduled commands running under service accounts.
Incorrect Answers
A:When configured, sudo can retain input and output evidence useful for reconstructing sensitive changes; applying it would serve record privileged interactive sessions with contextual attribution without directly satisfying the goal to identify unexpected scheduled commands running under service accounts.
B:Interactive shell histories may be modified or disabled and do not capture every process execution; it addresses the different need to avoid relying on shell history as a complete privileged-command audit, leaving the requested ability to identify unexpected scheduled commands running under service accounts unresolved.
D:Bootloader passwords, encryption and physical controls narrow unauthorized offline system changes; its mechanism supports prevent local console recovery options from bypassing administrative protections, while the requested control must be able to identify unexpected scheduled commands running under service accounts.
Question 328
To prevent application memory containing secrets from being written broadly to disk, which protective or investigative measure applies?
- Core dump privacy controls
- Process accounting deployment
- Systemd unit persistence audit
- Crontab persistence review
Explanation
Correct Answer
A:Core-dump limits reduce storage exposure of credentials and in-process confidential material; the requested outcome is precisely to prevent application memory containing secrets from being written broadly to disk.
Incorrect Answers
B: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 prevent application memory containing secrets from being written broadly to disk.
C:Unit file creation and enablement can provide persistence independent of user crontabs; it addresses the different need to find an unauthorized daemon enabled to restart after boot, leaving the requested ability to prevent application memory containing secrets from being written broadly to disk unresolved.
D:Cron schedules launch periodic activity that may represent legitimate maintenance or attacker persistence; the technique works for situations involving identify unexpected scheduled commands running under service accounts, rather than this need to prevent application memory containing secrets from being written broadly to disk.
Question 329
To protect a Linux laptop's filesystem after physical device theft, what is the most direct option?
- LUKS full-disk encryption
- Crontab persistence review
- Systemd unit persistence audit
- Rescue-mode authentication
Explanation
Correct Answer
A:Volume encryption protects offline data when key handling and unlock procedures remain secure; this choice fits the scenario because the team must protect a Linux laptop's filesystem after physical device theft.
Incorrect Answers
B:Cron schedules launch periodic activity that may represent legitimate maintenance or attacker persistence; its operational purpose is to identify unexpected scheduled commands running under service accounts, not to achieve the specific requirement to protect a Linux laptop's filesystem after physical device theft.
C:Unit file creation and enablement can provide persistence independent of user crontabs; applying it would serve find an unauthorized daemon enabled to restart after boot without directly satisfying the goal to protect a Linux laptop's filesystem after physical device theft.
D:Bootloader passwords, encryption and physical controls narrow unauthorized offline system changes; it addresses the different need to prevent local console recovery options from bypassing administrative protections, leaving the requested ability to protect a Linux laptop's filesystem after physical device theft unresolved.
Question 330
To prevent local console recovery options from bypassing administrative protections, which measure best meets the requirement?
- Core dump privacy controls
- Rescue-mode authentication
- Crontab persistence review
- Sudo I/O logging
- LUKS full-disk encryption
Explanation
Correct Answer
B:Bootloader passwords, encryption and physical controls narrow unauthorized offline system changes; this mechanism directly supports the requirement to prevent local console recovery options from bypassing administrative protections.
Incorrect Answers
A:Core-dump limits reduce storage exposure of credentials and in-process confidential material; that is useful when the task is to prevent application memory containing secrets from being written broadly to disk, not the stated requirement to prevent local console recovery options from bypassing administrative protections.
C:Cron schedules launch periodic activity that may represent legitimate maintenance or attacker persistence; its operational purpose is to identify unexpected scheduled commands running under service accounts, not to achieve the specific requirement to prevent local console recovery options from bypassing administrative protections.
D:When configured, sudo can retain input and output evidence useful for reconstructing sensitive changes; applying it would serve record privileged interactive sessions with contextual attribution without directly satisfying the goal to prevent local console recovery options from bypassing administrative protections.
E:Volume encryption protects offline data when key handling and unlock procedures remain secure; it addresses the different need to protect a Linux laptop's filesystem after physical device theft, leaving the requested ability to prevent local console recovery options from bypassing administrative protections unresolved.