Question 300
To apply certain kernel security fixes while minimizing immediate reboot downtime, which solution should be adopted?
- Signed package repositories
- AIDE integrity baseline
- GPG package verification
- Kernel live patching
- Rootkit detection review
Explanation
Correct Answer
D:Live patch services replace supported in-memory code paths, not every possible kernel or userland flaw; this mechanism directly supports the requirement to apply certain kernel security fixes while minimizing immediate reboot downtime.
Incorrect Answers
A:Package-manager signature validation authenticates update sources and detects metadata alteration; that is useful when the task is to stop installation of packages whose repository metadata fails trusted signature checks, not the stated requirement to apply certain kernel security fixes while minimizing immediate reboot downtime.
B:File hashes and attributes expose tampering only when the baseline and reports are themselves protected; a team would select it to detect changed critical system binaries against an approved file database, which does not provide the particular result to apply certain kernel security fixes while minimizing immediate reboot downtime.
C:Trusted public keys authenticate the signed artifact independently of transport encryption; its operational purpose is to verify an externally supplied package against a trusted maintainer signature, not to achieve the specific requirement to apply certain kernel security fixes while minimizing immediate reboot downtime.
E:Host integrity and kernel indicators can flag stealth activity, with findings requiring independent verification; it addresses the different need to investigate suspicious hidden processes or modified system tools, leaving the requested ability to apply certain kernel security fixes while minimizing immediate reboot downtime unresolved.
Question 301
To detect changed critical system binaries against an approved file database, which of the available controls is suitable?
- AIDE integrity baseline
- Systemd service hardening
- Kernel live patching
- Rootkit detection review
Explanation
Correct Answer
A:File hashes and attributes expose tampering only when the baseline and reports are themselves protected; it supplies the specific control needed to detect changed critical system binaries against an approved file database.
Incorrect Answers
B:Service unit sandbox directives narrow process authority without rewriting the application's code; that is useful when the task is to restrict filesystem, capabilities and namespace privileges of one daemon, not the stated requirement to detect changed critical system binaries against an approved file database.
C:Live patch services replace supported in-memory code paths, not every possible kernel or userland flaw; a team would select it to apply certain kernel security fixes while minimizing immediate reboot downtime, which does not provide the particular result to detect changed critical system binaries against an approved file database.
D:Host integrity and kernel indicators can flag stealth activity, with findings requiring independent verification; its operational purpose is to investigate suspicious hidden processes or modified system tools, not to achieve the specific requirement to detect changed critical system binaries against an approved file database.
Question 302
To investigate suspicious hidden processes or modified system tools, which option is the direct technical match?
- Immutable file attribute
- Signed package repositories
- Rootkit detection review
- Kernel live patching
Explanation
Correct Answer
C:Host integrity and kernel indicators can flag stealth activity, with findings requiring independent verification; that is why it addresses the operational task to investigate suspicious hidden processes or modified system tools.
Incorrect Answers
A:The immutable flag inhibits modification until an authorized privileged operator removes the attribute; although relevant to resist accidental overwrites of a static security configuration, it does not by itself achieve the required task to investigate suspicious hidden processes or modified system tools.
B:Package-manager signature validation authenticates update sources and detects metadata alteration; it could help someone trying to stop installation of packages whose repository metadata fails trusted signature checks, but the problem is instead to investigate suspicious hidden processes or modified system tools.
D:Live patch services replace supported in-memory code paths, not every possible kernel or userland flaw; a team would select it to apply certain kernel security fixes while minimizing immediate reboot downtime, which does not provide the particular result to investigate suspicious hidden processes or modified system tools.
Question 303
To verify an externally supplied package against a trusted maintainer signature, which approach should a Linux systems administrator choose?
- GPG package verification
- Immutable file attribute
- Secure boot chain
- Auditd file watch
Explanation
Correct Answer
A:Trusted public keys authenticate the signed artifact independently of transport encryption; its relevant protective or investigative effect is to verify an externally supplied package against a trusted maintainer signature.
Incorrect Answers
B:The immutable flag inhibits modification until an authorized privileged operator removes the attribute; although relevant to resist accidental overwrites of a static security configuration, it does not by itself achieve the required task to verify an externally supplied package against a trusted maintainer signature.
C:UEFI and loader validation help preserve the pre-kernel trust chain rather than relying on file permissions; it could help someone trying to reject unsigned or untrusted boot components on supported Linux systems, but the problem is instead to verify an externally supplied package against a trusted maintainer signature.
D:Kernel audit rules record defined events with subject context when audit infrastructure is healthy; that is useful when the task is to log access or changes to a high-value Linux credential file, not the stated requirement to verify an externally supplied package against a trusted maintainer signature.
Question 304
To restrict filesystem, capabilities and namespace privileges of one daemon, which method is designed for the task?
- Auditd file watch
- Secure boot chain
- Unattended security updates
- Linux kernel parameter hardening
- Systemd service hardening
- Immutable file attribute
Explanation
Correct Answer
E:Service unit sandbox directives narrow process authority without rewriting the application's code; the requested outcome is precisely to restrict filesystem, capabilities and namespace privileges of one daemon.
Incorrect Answers
A:Kernel audit rules record defined events with subject context when audit infrastructure is healthy; its mechanism supports log access or changes to a high-value Linux credential file, while the requested control must be able to restrict filesystem, capabilities and namespace privileges of one daemon.
B:UEFI and loader validation help preserve the pre-kernel trust chain rather than relying on file permissions; the outcome it supports is to reject unsigned or untrusted boot components on supported Linux systems, whereas this scenario asks defenders to restrict filesystem, capabilities and namespace privileges of one daemon.
C:Automated patch jobs narrow exposure windows but need monitoring and reboot planning; although relevant to install approved Linux vulnerability fixes without manual package commands, it does not by itself achieve the required task to restrict filesystem, capabilities and namespace privileges of one daemon.
D:Kernel tunables can govern forwarding, redirect acceptance or address-space behavior at the host layer; it could help someone trying to reduce unsafe networking behavior with persistent sysctl settings, but the problem is instead to restrict filesystem, capabilities and namespace privileges of one daemon.
F:The immutable flag inhibits modification until an authorized privileged operator removes the attribute; a team would select it to resist accidental overwrites of a static security configuration, which does not provide the particular result to restrict filesystem, capabilities and namespace privileges of one daemon.
Question 305
To log access or changes to a high-value Linux credential file, what technique should the team use?
- Secure boot chain
- Linux kernel parameter hardening
- Auditd file watch
- GPG package verification
- Rootkit detection review
Explanation
Correct Answer
C:Kernel audit rules record defined events with subject context when audit infrastructure is healthy; this choice fits the scenario because the team must log access or changes to a high-value Linux credential file.
Incorrect Answers
A:UEFI and loader validation help preserve the pre-kernel trust chain rather than relying on file permissions; the technique works for situations involving reject unsigned or untrusted boot components on supported Linux systems, rather than this need to log access or changes to a high-value Linux credential file.
B:Kernel tunables can govern forwarding, redirect acceptance or address-space behavior at the host layer; its mechanism supports reduce unsafe networking behavior with persistent sysctl settings, while the requested control must be able to log access or changes to a high-value Linux credential file.
D:Trusted public keys authenticate the signed artifact independently of transport encryption; although relevant to verify an externally supplied package against a trusted maintainer signature, it does not by itself achieve the required task to log access or changes to a high-value Linux credential file.
E:Host integrity and kernel indicators can flag stealth activity, with findings requiring independent verification; it could help someone trying to investigate suspicious hidden processes or modified system tools, but the problem is instead to log access or changes to a high-value Linux credential file.
Question 306
To resist accidental overwrites of a static security configuration, which protective or investigative measure applies?
- Immutable file attribute
- Systemd service hardening
- Secure boot chain
- Linux kernel parameter hardening
Explanation
Correct Answer
A:The immutable flag inhibits modification until an authorized privileged operator removes the attribute; this mechanism directly supports the requirement to resist accidental overwrites of a static security configuration.
Incorrect Answers
B:Service unit sandbox directives narrow process authority without rewriting the application's code; the technique works for situations involving restrict filesystem, capabilities and namespace privileges of one daemon, rather than this need to resist accidental overwrites of a static security configuration.
C:UEFI and loader validation help preserve the pre-kernel trust chain rather than relying on file permissions; its mechanism supports reject unsigned or untrusted boot components on supported Linux systems, while the requested control must be able to resist accidental overwrites of a static security configuration.
D:Kernel tunables can govern forwarding, redirect acceptance or address-space behavior at the host layer; the outcome it supports is to reduce unsafe networking behavior with persistent sysctl settings, whereas this scenario asks defenders to resist accidental overwrites of a static security configuration.
Question 307
To reduce unsafe networking behavior with persistent sysctl settings and to reject unsigned or untrusted boot components on supported Linux systems, which TWO measures should the defender select? Choose TWO.
- Rootkit detection review
- Secure boot chain
- Auditd file watch
- Linux kernel parameter hardening
- Immutable file attribute
Explanation
Correct Answers
B:UEFI and loader validation help preserve the pre-kernel trust chain rather than relying on file permissions; its contribution to the combined design is specifically to reject unsigned or untrusted boot components on supported Linux systems.
D:Kernel tunables can govern forwarding, redirect acceptance or address-space behavior at the host layer; its contribution to the combined design is specifically to reduce unsafe networking behavior with persistent sysctl settings.
Incorrect Answers
A:Host integrity and kernel indicators can flag stealth activity, with findings requiring independent verification; applying it would serve investigate suspicious hidden processes or modified system tools without directly satisfying the goal to reduce unsafe networking behavior with persistent sysctl settings and to reject unsigned or untrusted boot components on supported Linux systems.
C:Kernel audit rules record defined events with subject context when audit infrastructure is healthy; the technique works for situations involving log access or changes to a high-value Linux credential file, rather than this need to reduce unsafe networking behavior with persistent sysctl settings and to reject unsigned or untrusted boot components on supported Linux systems.
E:The immutable flag inhibits modification until an authorized privileged operator removes the attribute; the outcome it supports is to resist accidental overwrites of a static security configuration, whereas this scenario asks defenders to reduce unsafe networking behavior with persistent sysctl settings and to reject unsigned or untrusted boot components on supported Linux systems.
Question 308
A Linux workstation is configured with a trust policy for production executables. After startup, administrators want attempts to open modified or unsigned protected binaries to be denied instead of merely logged. Which Linux facility applies that file-integrity decision at access time?
- UEFI Secure Boot validation
- Linux IMA appraisal policy
- Auditd execve event monitoring
- Scheduled AIDE integrity comparison
Explanation
Correct Answer
B:An enforcing Integrity Measurement Architecture appraisal policy can validate file hashes or signatures during access and deny use of files that fail the policy. Configuration and labeling must match the files being protected.
Incorrect Answers
A:UEFI Secure Boot checks trusted boot-stage images and related loader components. It does not by itself enforce file-specific signature or integrity rules when arbitrary protected user-space binaries are opened later.
C:Auditd can record process execution attempts and associated security events for review. Recording an attempt does not implement a mandatory allow-or-deny integrity decision each time the protected file is accessed.
D:AIDE can compare current files with a trusted baseline and report modifications during scheduled scans. Its offline comparison does not automatically reject every attempt to use an altered executable at the moment of access.
Question 309
To permit established return traffic while rejecting unsolicited inbound flows, what should defenders select?
- SSHD authentication logging
- SSH host-key verification
- Firewalld zone policy
- Nftables stateful filtering
Explanation
Correct Answer
D:Connection tracking classifies existing sessions, simplifying default-deny host firewall design; its relevant protective or investigative effect is to permit established return traffic while rejecting unsolicited inbound flows.
Incorrect Answers
A:Secure authentication records provide evidence of guessing and unexpected access patterns; a team would select it to correlate remote login successes and failures by source and user, which does not provide the particular result to permit established return traffic while rejecting unsolicited inbound flows.
B:Validating the expected host key detects impersonation before sensitive interactive commands are exchanged; its operational purpose is to prevent remote administrators from accepting a counterfeit server silently, not to achieve the specific requirement to permit established return traffic while rejecting unsolicited inbound flows.
C:Zone associations group allowed services and exposure according to network context; applying it would serve apply differing Linux firewall rules to interfaces with different trust levels without directly satisfying the goal to permit established return traffic while rejecting unsolicited inbound flows.
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.