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

Question 280

To force administrators to enter through named accounts before elevation, which option is the direct technical match?

  1. SSH root-login prohibition
  2. Account expiration
  3. POSIX ACL management
  4. SSH AllowGroups restriction
  5. PAM faillock

Explanation

Correct Answer

A:

Disabling direct root SSH entry improves attribution and reduces direct attack opportunities against a shared identity; the requested outcome is precisely to force administrators to enter through named accounts before elevation.

Incorrect Answers

B:

Account aging disables credentials at a configured date, avoiding forgotten long-lived access; a team would select it to remove login capability from temporary contractor accounts after project closure, which does not provide the particular result to force administrators to enter through named accounts before elevation.

C:

Extended ACL entries supplement traditional owner/group/other bits with per-principal permissions; its operational purpose is to give one additional service identity file access without broad group membership, not to achieve the specific requirement to force administrators to enter through named accounts before elevation.

D:

sshd membership checks provide an additional admission layer beyond file permissions or network connectivity; applying it would serve limit which existing Linux accounts may initiate remote shell access without directly satisfying the goal to force administrators to enter through named accounts before elevation.

E:

Failure counting can slow online guessing while administrators account for denial-of-service and unlock behavior; it addresses the different need to temporarily restrict repeated unsuccessful Linux account authentication, leaving the requested ability to force administrators to enter through named accounts before elevation unresolved.

Question 281

To limit which existing Linux accounts may initiate remote shell access, which approach should a Linux systems administrator choose?

  1. SSH AllowGroups restriction
  2. PAM faillock
  3. SSH public-key login
  4. Account expiration

Explanation

Correct Answer

A:

sshd membership checks provide an additional admission layer beyond file permissions or network connectivity; this choice fits the scenario because the team must limit which existing Linux accounts may initiate remote shell access.

Incorrect Answers

B:

Failure counting can slow online guessing while administrators account for denial-of-service and unlock behavior; that is useful when the task is to temporarily restrict repeated unsuccessful Linux account authentication, not the stated requirement to limit which existing Linux accounts may initiate remote shell access.

C:

SSH challenges users to demonstrate private-key possession while encrypting the management session; a team would select it to avoid reusable passwords for administrator remote access, which does not provide the particular result to limit which existing Linux accounts may initiate remote shell access.

D:

Account aging disables credentials at a configured date, avoiding forgotten long-lived access; its operational purpose is to remove login capability from temporary contractor accounts after project closure, not to achieve the specific requirement to limit which existing Linux accounts may initiate remote shell access.

Question 282

To remove login capability from temporary contractor accounts after project closure, which method is designed for the task?

  1. Account expiration
  2. SSH public-key login
  3. SSH AllowGroups restriction
  4. SSH root-login prohibition

Explanation

Correct Answer

A:

Account aging disables credentials at a configured date, avoiding forgotten long-lived access; this mechanism directly supports the requirement to remove login capability from temporary contractor accounts after project closure.

Incorrect Answers

B:

SSH challenges users to demonstrate private-key possession while encrypting the management session; it could help someone trying to avoid reusable passwords for administrator remote access, but the problem is instead to remove login capability from temporary contractor accounts after project closure.

C:

sshd membership checks provide an additional admission layer beyond file permissions or network connectivity. This can help to limit which existing Linux accounts may initiate remote shell access, but it does not provide the particular mechanism required to remove login capability from temporary contractor accounts after project closure.

D:

Disabling direct root SSH entry improves attribution and reduces direct attack opportunities against a shared identity; a team would select it to force administrators to enter through named accounts before elevation, which does not provide the particular result to remove login capability from temporary contractor accounts after project closure.

Question 283

To remove group and world write privileges from a sensitive configuration file and to give one additional service identity file access without broad group membership, which TWO measures should the defender select? Choose TWO.

  1. POSIX ACL management
  2. Capability minimization
  3. SSH AllowGroups restriction
  4. File permission chmod
  5. Setuid audit

Explanation

Correct Answers

A:

Extended ACL entries supplement traditional owner/group/other bits with per-principal permissions; its contribution to the combined design is specifically to give one additional service identity file access without broad group membership.

D:

POSIX permission bits determine access for the file owner, group and others independently of a firewall; its contribution to the combined design is specifically to remove group and world write privileges from a sensitive configuration file.

Incorrect Answers

B:

Linux capabilities divide traditional root authority so processes can receive narrower privilege sets; although relevant to give a Linux daemon one privileged operation without full root identity, it does not by itself achieve the required task to remove group and world write privileges from a sensitive configuration file and to give one additional service identity file access without broad group membership.

C:

sshd membership checks provide an additional admission layer beyond file permissions or network connectivity; it could help someone trying to limit which existing Linux accounts may initiate remote shell access, but the problem is instead to remove group and world write privileges from a sensitive configuration file and to give one additional service identity file access without broad group membership.

E:

Setuid permissions can confer privileged execution and warrant tight ownership, necessity and patch review; a team would select it to find executables that might run with a file owner's elevated effective identity, which does not provide the particular result to remove group and world write privileges from a sensitive configuration file and to give one additional service identity file access without broad group membership.

Question 284

To give one additional service identity file access without broad group membership, which protective or investigative measure applies?

  1. SSH root-login prohibition
  2. POSIX ACL management
  3. SSH public-key login
  4. Account expiration

Explanation

Correct Answer

B:

Extended ACL entries supplement traditional owner/group/other bits with per-principal permissions; that is why it addresses the operational task to give one additional service identity file access without broad group membership.

Incorrect Answers

A:

Disabling direct root SSH entry improves attribution and reduces direct attack opportunities against a shared identity; its mechanism supports force administrators to enter through named accounts before elevation, while the requested control must be able to give one additional service identity file access without broad group membership.

C:

SSH challenges users to demonstrate private-key possession while encrypting the management session; although relevant to avoid reusable passwords for administrator remote access, it does not by itself achieve the required task to give one additional service identity file access without broad group membership.

D:

Account aging disables credentials at a configured date, avoiding forgotten long-lived access; it could help someone trying to remove login capability from temporary contractor accounts after project closure, but the problem is instead to give one additional service identity file access without broad group membership.

Question 285

To find executables that might run with a file owner's elevated effective identity, what is the most direct option?

  1. POSIX ACL management
  2. SSH AllowGroups restriction
  3. Setuid audit
  4. File permission chmod
  5. SSH root-login prohibition
  6. Capability minimization

Explanation

Correct Answer

C:

Setuid permissions can confer privileged execution and warrant tight ownership, necessity and patch review; its relevant protective or investigative effect is to find executables that might run with a file owner's elevated effective identity.

Incorrect Answers

A:

Extended ACL entries supplement traditional owner/group/other bits with per-principal permissions; the technique works for situations involving give one additional service identity file access without broad group membership, rather than this need to find executables that might run with a file owner's elevated effective identity.

B:

sshd membership checks provide an additional admission layer beyond file permissions or network connectivity; its mechanism supports limit which existing Linux accounts may initiate remote shell access, while the requested control must be able to find executables that might run with a file owner's elevated effective identity.

D:

POSIX permission bits determine access for the file owner, group and others independently of a firewall; although relevant to remove group and world write privileges from a sensitive configuration file, it does not by itself achieve the required task to find executables that might run with a file owner's elevated effective identity.

E:

Disabling direct root SSH entry improves attribution and reduces direct attack opportunities against a shared identity; it could help someone trying to force administrators to enter through named accounts before elevation, but the problem is instead to find executables that might run with a file owner's elevated effective identity.

F:

Linux capabilities divide traditional root authority so processes can receive narrower privilege sets; that is useful when the task is to give a Linux daemon one privileged operation without full root identity, not the stated requirement to find executables that might run with a file owner's elevated effective identity.

Question 286

To give a Linux daemon one privileged operation without full root identity, what is the most direct option?

  1. Setuid audit
  2. Capability minimization
  3. File permission chmod
  4. Account expiration

Explanation

Correct Answer

B:

Linux capabilities divide traditional root authority so processes can receive narrower privilege sets; the requested outcome is precisely to give a Linux daemon one privileged operation without full root identity.

Incorrect Answers

A:

Setuid permissions can confer privileged execution and warrant tight ownership, necessity and patch review; it addresses the different need to find executables that might run with a file owner's elevated effective identity, leaving the requested ability to give a Linux daemon one privileged operation without full root identity unresolved.

C:

POSIX permission bits determine access for the file owner, group and others independently of a firewall; its mechanism supports remove group and world write privileges from a sensitive configuration file, while the requested control must be able to give a Linux daemon one privileged operation without full root identity.

D:

Account aging disables credentials at a configured date, avoiding forgotten long-lived access; the outcome it supports is to remove login capability from temporary contractor accounts after project closure, whereas this scenario asks defenders to give a Linux daemon one privileged operation without full root identity.

Question 287

To block a compromised service from reading files outside its permitted security domain, what should defenders select?

  1. AppArmor confinement
  2. Linux namespaces
  3. SELinux enforcing mode
  4. cgroups resource limits

Explanation

Correct Answer

C:

Type enforcement evaluates labeled subject and object policy even when ordinary UNIX permissions allow access; this choice fits the scenario because the team must block a compromised service from reading files outside its permitted security domain.

Incorrect Answers

A:

Path-oriented mandatory policy limits application behavior beyond the account's discretionary permissions; applying it would serve restrict a service's filesystem and operation access with a named profile without directly satisfying the goal to block a compromised service from reading files outside its permitted security domain.

B:

Namespace boundaries partition kernel resource views but do not by themselves create a full VM boundary; it addresses the different need to isolate a process view of PIDs, mounts or network interfaces, leaving the requested ability to block a compromised service from reading files outside its permitted security domain unresolved.

D:

Control groups account for and constrain process resource consumption, supporting denial-of-service containment; its mechanism supports stop an untrusted service exhausting host CPU or memory, while the requested control must be able to block a compromised service from reading files outside its permitted security domain.

Question 288

To restrict a service's filesystem and operation access with a named profile, which mechanism best fits?

  1. seccomp syscall filter
  2. AppArmor confinement
  3. SELinux enforcing mode
  4. Linux namespaces

Explanation

Correct Answer

B:

Path-oriented mandatory policy limits application behavior beyond the account's discretionary permissions; this mechanism directly supports the requirement to restrict a service's filesystem and operation access with a named profile.

Incorrect Answers

A:

System-call allow or deny rules reduce kernel attack surface independently of file-level access controls; its operational purpose is to prevent a containerized worker from invoking unneeded kernel system calls, not to achieve the specific requirement to restrict a service's filesystem and operation access with a named profile.

C:

Type enforcement evaluates labeled subject and object policy even when ordinary UNIX permissions allow access; it addresses the different need to block a compromised service from reading files outside its permitted security domain, leaving the requested ability to restrict a service's filesystem and operation access with a named profile unresolved.

D:

Namespace boundaries partition kernel resource views but do not by themselves create a full VM boundary; the technique works for situations involving isolate a process view of PIDs, mounts or network interfaces, rather than this need to restrict a service's filesystem and operation access with a named profile.

Question 289

An unprivileged Linux worker must voluntarily restrict its own read and write access to selected directories at runtime. The team does not want to install a system-wide security profile. On a kernel with this facility enabled, what fits best?

  1. AppArmor confinement profiles
  2. Landlock filesystem ruleset
  3. seccomp system-call filter
  4. A chroot directory change

Explanation

Correct Answer

B:

Landlock lets a process, including an unprivileged one under supported conditions, restrict its own filesystem access with an additive ruleset. It does not grant new rights beyond existing permissions.

Incorrect Answers

A:

AppArmor can restrict file access using administrator-defined profiles, but the requirement is an unprivileged process applying additional restrictions to itself without a system-level profile.

C:

seccomp restricts available system calls or arguments under the filter design. It is not a directory-by-directory filesystem access policy for this unprivileged worker.

D:

chroot changes the apparent filesystem root, but alone is not a robust security boundary. It does not provide the requested self-imposed, path-based access-control ruleset.

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.

Certified Network Defender (312-38) Practice Tests