ECCouncil 312-38 (Certified Network Defender) Practice Test 30

Question 290

To isolate a process view of PIDs, mounts or network interfaces, what control should be selected?

  1. chroot limitation
  2. seccomp syscall filter
  3. SELinux enforcing mode
  4. Linux namespaces
  5. Mount nosuid option

Explanation

Correct Answer

D:

Namespace boundaries partition kernel resource views but do not by themselves create a full VM boundary; that is why it addresses the operational task to isolate a process view of PIDs, mounts or network interfaces.

Incorrect Answers

A:

A changed filesystem root restricts path visibility but privileged processes can escape weak isolation designs; that is useful when the task is to avoid mistaking an altered root directory for a complete security sandbox, not the stated requirement to isolate a process view of PIDs, mounts or network interfaces.

B:

System-call allow or deny rules reduce kernel attack surface independently of file-level access controls; a team would select it to prevent a containerized worker from invoking unneeded kernel system calls, which does not provide the particular result to isolate a process view of PIDs, mounts or network interfaces.

C:

Type enforcement evaluates labeled subject and object policy even when ordinary UNIX permissions allow access; its operational purpose is to block a compromised service from reading files outside its permitted security domain, not to achieve the specific requirement to isolate a process view of PIDs, mounts or network interfaces.

E:

Mount-time nosuid treatment prevents filesystem ownership bits granting identity changes from that volume; it addresses the different need to ignore setuid and setgid privilege elevation on removable storage, leaving the requested ability to isolate a process view of PIDs, mounts or network interfaces unresolved.

Question 291

To stop an untrusted service exhausting host CPU or memory, which security control is most appropriate?

  1. Mount noexec option
  2. seccomp syscall filter
  3. chroot limitation
  4. cgroups resource limits

Explanation

Correct Answer

D:

Control groups account for and constrain process resource consumption, supporting denial-of-service containment; its relevant protective or investigative effect is to stop an untrusted service exhausting host CPU or memory.

Incorrect Answers

A:

The noexec mount flag blocks direct execution from that mount, with limits against interpreters and memory execution; it could help someone trying to reduce execution of binaries placed on a temporary filesystem, but the problem is instead to stop an untrusted service exhausting host CPU or memory.

B:

System-call allow or deny rules reduce kernel attack surface independently of file-level access controls; that is useful when the task is to prevent a containerized worker from invoking unneeded kernel system calls, not the stated requirement to stop an untrusted service exhausting host CPU or memory.

C:

A changed filesystem root restricts path visibility but privileged processes can escape weak isolation designs; a team would select it to avoid mistaking an altered root directory for a complete security sandbox, which does not provide the particular result to stop an untrusted service exhausting host CPU or memory.

Question 292

To avoid mistaking an altered root directory for a complete security sandbox, what would a Linux systems administrator implement or use?

  1. Linux namespaces
  2. Mount nodev option
  3. chroot limitation
  4. seccomp syscall filter

Explanation

Correct Answer

C:

A changed filesystem root restricts path visibility but privileged processes can escape weak isolation designs; the requested outcome is precisely to avoid mistaking an altered root directory for a complete security sandbox.

Incorrect Answers

A:

Namespace boundaries partition kernel resource views but do not by themselves create a full VM boundary; although relevant to isolate a process view of PIDs, mounts or network interfaces, it does not by itself achieve the required task to avoid mistaking an altered root directory for a complete security sandbox.

B:

The nodev option reduces device-file abuse on filesystems that should contain ordinary data only; it could help someone trying to stop special-device files on an untrusted mount being interpreted as devices, but the problem is instead to avoid mistaking an altered root directory for a complete security sandbox.

D:

System-call allow or deny rules reduce kernel attack surface independently of file-level access controls; a team would select it to prevent a containerized worker from invoking unneeded kernel system calls, which does not provide the particular result to avoid mistaking an altered root directory for a complete security sandbox.

Question 293

To stop an application from modifying a deployed immutable configuration tree, which practice addresses that objective?

  1. Linux namespaces
  2. cgroups resource limits
  3. Read-only filesystem mount
  4. chroot limitation

Explanation

Correct Answer

C:

Read-only mounts prevent writes in the protected mount context even if a process has broad DAC rights; this choice fits the scenario because the team must stop an application from modifying a deployed immutable configuration tree.

Incorrect Answers

A:

Namespace boundaries partition kernel resource views but do not by themselves create a full VM boundary; the outcome it supports is to isolate a process view of PIDs, mounts or network interfaces, whereas this scenario asks defenders to stop an application from modifying a deployed immutable configuration tree.

B:

Control groups account for and constrain process resource consumption, supporting denial-of-service containment; although relevant to stop an untrusted service exhausting host CPU or memory, it does not by itself achieve the required task to stop an application from modifying a deployed immutable configuration tree.

D:

A changed filesystem root restricts path visibility but privileged processes can escape weak isolation designs; that is useful when the task is to avoid mistaking an altered root directory for a complete security sandbox, not the stated requirement to stop an application from modifying a deployed immutable configuration tree.

Question 294

To reduce execution of binaries placed on a temporary filesystem, which tool, policy, or technique is appropriate?

  1. Mount noexec option
  2. Mount nodev option
  3. Mount nosuid option
  4. Read-only filesystem mount

Explanation

Correct Answer

A:

The noexec mount flag blocks direct execution from that mount, with limits against interpreters and memory execution; this mechanism directly supports the requirement to reduce execution of binaries placed on a temporary filesystem.

Incorrect Answers

B:

The nodev option reduces device-file abuse on filesystems that should contain ordinary data only; the outcome it supports is to stop special-device files on an untrusted mount being interpreted as devices, whereas this scenario asks defenders to reduce execution of binaries placed on a temporary filesystem.

C:

Mount-time nosuid treatment prevents filesystem ownership bits granting identity changes from that volume; although relevant to ignore setuid and setgid privilege elevation on removable storage, it does not by itself achieve the required task to reduce execution of binaries placed on a temporary filesystem.

D:

Read-only mounts prevent writes in the protected mount context even if a process has broad DAC rights; it could help someone trying to stop an application from modifying a deployed immutable configuration tree, but the problem is instead to reduce execution of binaries placed on a temporary filesystem.

Question 295

To ignore setuid and setgid privilege elevation on removable storage and to stop special-device files on an untrusted mount being interpreted as devices, which TWO measures should the defender select? Choose TWO.

  1. Mount nosuid option
  2. Mount noexec option
  3. Read-only filesystem mount
  4. Linux namespaces
  5. Mount nodev option

Explanation

Correct Answers

A:

Mount-time nosuid treatment prevents filesystem ownership bits granting identity changes from that volume; its contribution to the combined design is specifically to ignore setuid and setgid privilege elevation on removable storage.

E:

The nodev option reduces device-file abuse on filesystems that should contain ordinary data only; its contribution to the combined design is specifically to stop special-device files on an untrusted mount being interpreted as devices.

Incorrect Answers

B:

The noexec mount flag blocks direct execution from that mount, with limits against interpreters and memory execution; its mechanism supports reduce execution of binaries placed on a temporary filesystem, while the requested control must be able to ignore setuid and setgid privilege elevation on removable storage and to stop special-device files on an untrusted mount being interpreted as devices.

C:

Read-only mounts prevent writes in the protected mount context even if a process has broad DAC rights; the outcome it supports is to stop an application from modifying a deployed immutable configuration tree, whereas this scenario asks defenders to ignore setuid and setgid privilege elevation on removable storage and to stop special-device files on an untrusted mount being interpreted as devices.

D:

Namespace boundaries partition kernel resource views but do not by themselves create a full VM boundary; although relevant to isolate a process view of PIDs, mounts or network interfaces, it does not by itself achieve the required task to ignore setuid and setgid privilege elevation on removable storage and to stop special-device files on an untrusted mount being interpreted as devices.

Question 296

To stop special-device files on an untrusted mount being interpreted as devices, what is the relevant defensive action?

  1. chroot limitation
  2. Mount nodev option
  3. Mount noexec option
  4. Mount nosuid option

Explanation

Correct Answer

B:

The nodev option reduces device-file abuse on filesystems that should contain ordinary data only; that is why it addresses the operational task to stop special-device files on an untrusted mount being interpreted as devices.

Incorrect Answers

A:

A changed filesystem root restricts path visibility but privileged processes can escape weak isolation designs; it addresses the different need to avoid mistaking an altered root directory for a complete security sandbox, leaving the requested ability to stop special-device files on an untrusted mount being interpreted as devices unresolved.

C:

The noexec mount flag blocks direct execution from that mount, with limits against interpreters and memory execution; its mechanism supports reduce execution of binaries placed on a temporary filesystem, while the requested control must be able to stop special-device files on an untrusted mount being interpreted as devices.

D:

Mount-time nosuid treatment prevents filesystem ownership bits granting identity changes from that volume; the outcome it supports is to ignore setuid and setgid privilege elevation on removable storage, whereas this scenario asks defenders to stop special-device files on an untrusted mount being interpreted as devices.

Question 297

To reduce untrusted userspace mechanisms that could modify a running kernel, what is the relevant defensive action?

  1. Mount noexec option
  2. Kernel lockdown evaluation
  3. Mount nodev option
  4. Read-only filesystem mount

Explanation

Correct Answer

B:

Kernel lockdown restricts selected interfaces under supported secure-boot or integrity configurations; its relevant protective or investigative effect is to reduce untrusted userspace mechanisms that could modify a running kernel.

Incorrect Answers

A:

The noexec mount flag blocks direct execution from that mount, with limits against interpreters and memory execution; applying it would serve reduce execution of binaries placed on a temporary filesystem without directly satisfying the goal to reduce untrusted userspace mechanisms that could modify a running kernel.

C:

The nodev option reduces device-file abuse on filesystems that should contain ordinary data only; the technique works for situations involving stop special-device files on an untrusted mount being interpreted as devices, rather than this need to reduce untrusted userspace mechanisms that could modify a running kernel.

D:

Read-only mounts prevent writes in the protected mount context even if a process has broad DAC rights; its mechanism supports stop an application from modifying a deployed immutable configuration tree, while the requested control must be able to reduce untrusted userspace mechanisms that could modify a running kernel.

Question 298

To stop installation of packages whose repository metadata fails trusted signature checks, which option most directly provides the capability?

  1. Kernel live patching
  2. Unattended security updates
  3. Signed package repositories
  4. AIDE integrity baseline

Explanation

Correct Answer

C:

Package-manager signature validation authenticates update sources and detects metadata alteration; the requested outcome is precisely to stop installation of packages whose repository metadata fails trusted signature checks.

Incorrect Answers

A:

Live patch services replace supported in-memory code paths, not every possible kernel or userland flaw; its operational purpose is to apply certain kernel security fixes while minimizing immediate reboot downtime, not to achieve the specific requirement to stop installation of packages whose repository metadata fails trusted signature checks.

B:

Automated patch jobs narrow exposure windows but need monitoring and reboot planning; applying it would serve install approved Linux vulnerability fixes without manual package commands without directly satisfying the goal to stop installation of packages whose repository metadata fails trusted signature checks.

D:

File hashes and attributes expose tampering only when the baseline and reports are themselves protected; the technique works for situations involving detect changed critical system binaries against an approved file database, rather than this need to stop installation of packages whose repository metadata fails trusted signature checks.

Question 299

To install approved Linux vulnerability fixes without manual package commands, which control achieves the target outcome?

  1. Signed package repositories
  2. Unattended security updates
  3. Kernel live patching
  4. Rootkit detection review

Explanation

Correct Answer

B:

Automated patch jobs narrow exposure windows but need monitoring and reboot planning; this choice fits the scenario because the team must install approved Linux vulnerability fixes without manual package commands.

Incorrect Answers

A:

Package-manager signature validation authenticates update sources and detects metadata alteration; a team would select it to stop installation of packages whose repository metadata fails trusted signature checks, which does not provide the particular result to install approved Linux vulnerability fixes without manual package commands.

C:

Live patch services replace supported in-memory code paths, not every possible kernel or userland flaw; applying it would serve apply certain kernel security fixes while minimizing immediate reboot downtime without directly satisfying the goal to install approved Linux vulnerability fixes without manual package commands.

D:

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 install approved Linux vulnerability fixes without manual package commands unresolved.

Question 300

To apply certain kernel security fixes while minimizing immediate reboot downtime, which solution should be adopted?

  1. Signed package repositories
  2. AIDE integrity baseline
  3. GPG package verification
  4. Kernel live patching
  5. 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.

Certified Network Defender (312-38) Practice Tests