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

Question 570

To avoid overlay outages caused by unreachable tunnel endpoints and to capture same-host VM east-west flows for security analysis, which TWO measures should the defender select? Choose TWO.

  1. Underlay routing validation
  2. Distributed policy drift checks
  3. SDN flow-table auditing
  4. SDN northbound API authentication
  5. Virtual network traffic mirroring

Explanation

Correct Answers

A:

Underlay IP reachability and MTU support are prerequisites for stable encapsulated tenant networking; this is the measure that can avoid overlay outages caused by unreachable tunnel endpoints as one of the separately stated outcomes.

E:

Mirroring from virtual switches exposes packets that may not traverse physical taps; this is the measure that can capture same-host VM east-west flows for security analysis as one of the separately stated outcomes.

Incorrect Answers

B:

Centralized intent reconciliation prevents host-specific gaps during placement changes; a team would select it to confirm security rules stay consistent when workloads migrate among hosts, which does not provide the particular result to avoid overlay outages caused by unreachable tunnel endpoints and to capture same-host VM east-west flows for security analysis.

C:

Flow policy review finds controller-introduced forwarding changes independent of conventional firewall ACLs; its operational purpose is to detect an unexpected high-priority rule redirecting sensitive traffic, not to achieve the specific requirement to avoid overlay outages caused by unreachable tunnel endpoints and to capture same-host VM east-west flows for security analysis.

D:

API identity, scopes and auditing protect controller automation interfaces; applying it would serve prevent unauthorized applications from changing logical network intent without directly satisfying the goal to avoid overlay outages caused by unreachable tunnel endpoints and to capture same-host VM east-west flows for security analysis.

Question 571

To capture same-host VM east-west flows for security analysis, which option is the direct technical match?

  1. Virtual network traffic mirroring
  2. Distributed policy drift checks
  3. SDN northbound API authentication
  4. Underlay routing validation

Explanation

Correct Answer

A:

Mirroring from virtual switches exposes packets that may not traverse physical taps; it supplies the specific control needed to capture same-host VM east-west flows for security analysis.

Incorrect Answers

B:

Centralized intent reconciliation prevents host-specific gaps during placement changes; that is useful when the task is to confirm security rules stay consistent when workloads migrate among hosts, not the stated requirement to capture same-host VM east-west flows for security analysis.

C:

API identity, scopes and auditing protect controller automation interfaces; a team would select it to prevent unauthorized applications from changing logical network intent, which does not provide the particular result to capture same-host VM east-west flows for security analysis.

D:

Underlay IP reachability and MTU support are prerequisites for stable encapsulated tenant networking; its operational purpose is to avoid overlay outages caused by unreachable tunnel endpoints, not to achieve the specific requirement to capture same-host VM east-west flows for security analysis.

Question 572

To confirm security rules stay consistent when workloads migrate among hosts, which option is the direct technical match?

  1. SDN flow-table auditing
  2. Distributed policy drift checks
  3. Virtual network traffic mirroring
  4. Underlay routing validation

Explanation

Correct Answer

B:

Centralized intent reconciliation prevents host-specific gaps during placement changes; that is why it addresses the operational task to confirm security rules stay consistent when workloads migrate among hosts.

Incorrect Answers

A:

Flow policy review finds controller-introduced forwarding changes independent of conventional firewall ACLs; although relevant to detect an unexpected high-priority rule redirecting sensitive traffic, it does not by itself achieve the required task to confirm security rules stay consistent when workloads migrate among hosts.

C:

Mirroring from virtual switches exposes packets that may not traverse physical taps; that is useful when the task is to capture same-host VM east-west flows for security analysis, not the stated requirement to confirm security rules stay consistent when workloads migrate among hosts.

D:

Underlay IP reachability and MTU support are prerequisites for stable encapsulated tenant networking; a team would select it to avoid overlay outages caused by unreachable tunnel endpoints, which does not provide the particular result to confirm security rules stay consistent when workloads migrate among hosts.

Question 573

To reduce host-root exposure from routine container runtime processes, which approach should a virtualization security engineer choose?

  1. Container image signing
  2. Minimal base images
  3. Container vulnerability scanning
  4. Rootless container execution

Explanation

Correct Answer

D:

User namespaces and rootless daemons constrain privilege compared with a traditional root-owned runtime; its relevant protective or investigative effect is to reduce host-root exposure from routine container runtime processes.

Incorrect Answers

A:

Signature policy verifies artifact provenance before workloads receive deployment authority; the outcome it supports is to reject images whose producer identity or digest cannot be validated, whereas this scenario asks defenders to reduce host-root exposure from routine container runtime processes.

B:

Smaller image contents reduce available binaries and patch burden for an attacker; although relevant to remove unused shells and network clients from container deployments, it does not by itself achieve the required task to reduce host-root exposure from routine container runtime processes.

C:

Image analysis maps packages to advisories before the artifact reaches the runtime; it could help someone trying to find outdated libraries baked into a proposed production image, but the problem is instead to reduce host-root exposure from routine container runtime processes.

Question 574

To reject images whose producer identity or digest cannot be validated, which method is designed for the task?

  1. Container image signing
  2. Minimal base images
  3. Read-only container root filesystem
  4. Container vulnerability scanning

Explanation

Correct Answer

A:

Signature policy verifies artifact provenance before workloads receive deployment authority; the requested outcome is precisely to reject images whose producer identity or digest cannot be validated.

Incorrect Answers

B:

Smaller image contents reduce available binaries and patch burden for an attacker; the outcome it supports is to remove unused shells and network clients from container deployments, whereas this scenario asks defenders to reject images whose producer identity or digest cannot be validated.

C:

Immutable roots constrain writes while designated runtime data directories can remain mounted separately; although relevant to prevent a compromised application from changing its packaged code, it does not by itself achieve the required task to reject images whose producer identity or digest cannot be validated.

D:

Image analysis maps packages to advisories before the artifact reaches the runtime; it could help someone trying to find outdated libraries baked into a proposed production image, but the problem is instead to reject images whose producer identity or digest cannot be validated.

Question 575

To find outdated libraries baked into a proposed production image, what technique should the team use?

  1. Container image signing
  2. Read-only container root filesystem
  3. Container vulnerability scanning
  4. Container user namespace remapping
  5. Minimal base images

Explanation

Correct Answer

C:

Image analysis maps packages to advisories before the artifact reaches the runtime; this choice fits the scenario because the team must find outdated libraries baked into a proposed production image.

Incorrect Answers

A:

Signature policy verifies artifact provenance before workloads receive deployment authority; the technique works for situations involving reject images whose producer identity or digest cannot be validated, rather than this need to find outdated libraries baked into a proposed production image.

B:

Immutable roots constrain writes while designated runtime data directories can remain mounted separately; its mechanism supports prevent a compromised application from changing its packaged code, while the requested control must be able to find outdated libraries baked into a proposed production image.

D:

User mappings reduce the impact of privilege confusion across the container boundary; although relevant to prevent container UID 0 mapping directly to host UID 0, it does not by itself achieve the required task to find outdated libraries baked into a proposed production image.

E:

Smaller image contents reduce available binaries and patch burden for an attacker; it could help someone trying to remove unused shells and network clients from container deployments, but the problem is instead to find outdated libraries baked into a proposed production image.

Question 576

To remove unused shells and network clients from container deployments, which protective or investigative measure applies?

  1. Container user namespace remapping
  2. Container image signing
  3. Minimal base images
  4. Rootless container execution

Explanation

Correct Answer

C:

Smaller image contents reduce available binaries and patch burden for an attacker; this mechanism directly supports the requirement to remove unused shells and network clients from container deployments.

Incorrect Answers

A:

User mappings reduce the impact of privilege confusion across the container boundary; it addresses the different need to prevent container UID 0 mapping directly to host UID 0, leaving the requested ability to remove unused shells and network clients from container deployments unresolved.

B:

Signature policy verifies artifact provenance before workloads receive deployment authority; the technique works for situations involving reject images whose producer identity or digest cannot be validated, rather than this need to remove unused shells and network clients from container deployments.

D:

User namespaces and rootless daemons constrain privilege compared with a traditional root-owned runtime; the outcome it supports is to reduce host-root exposure from routine container runtime processes, whereas this scenario asks defenders to remove unused shells and network clients from container deployments.

Question 577

An approved Kubernetes deployment refers to a mutable container-image tag. A registry administrator could later move that tag to different code without updating the deployment manifest. How should the team ensure the deployment requests the exact reviewed image artifact?

  1. Container image signing without a digest reference
  2. Scheduled vulnerability scanning of image tags
  3. Minimal container base-image selection
  4. Pin the image reference to an immutable content digest

Explanation

Correct Answer

D:

An immutable image digest identifies the exact artifact content referenced by the deployment manifest. Pinning the digest prevents a later registry tag change from silently selecting different code.

Incorrect Answers

A:

Image signing can establish image origin and artifact integrity when signatures are actually verified. Merely signing an image while deploying a mutable tag does not guarantee that the manifest selects the previously reviewed artifact.

B:

Vulnerability scanning identifies packages and exposures in container images. It does not lock a mutable registry tag to one exact artifact during deployment, even when the tag was scanned earlier.

C:

A minimal base image reduces unnecessary software and attack surface. It does not prevent a tag from being reassigned to a different set of image layers after approval.

Question 578

To remove powerful Linux operations not required by a web API, what should defenders select?

  1. Read-only container root filesystem
  2. Container image signing
  3. Container user namespace remapping
  4. Container capability drop

Explanation

Correct Answer

D:

Dropping capabilities limits privilege beyond the container's user identity; that is why it addresses the operational task to remove powerful Linux operations not required by a web API.

Incorrect Answers

A:

Immutable roots constrain writes while designated runtime data directories can remain mounted separately; its operational purpose is to prevent a compromised application from changing its packaged code, not to achieve the specific requirement to remove powerful Linux operations not required by a web API.

B:

Signature policy verifies artifact provenance before workloads receive deployment authority; applying it would serve reject images whose producer identity or digest cannot be validated without directly satisfying the goal to remove powerful Linux operations not required by a web API.

C:

User mappings reduce the impact of privilege confusion across the container boundary; it addresses the different need to prevent container UID 0 mapping directly to host UID 0, leaving the requested ability to remove powerful Linux operations not required by a web API unresolved.

Question 579

To deny unsafe or unused kernel syscalls from a workload, which mechanism best fits?

  1. Container user namespace remapping
  2. Container seccomp profile
  3. Read-only container root filesystem
  4. Container capability drop

Explanation

Correct Answer

B:

System-call policies reduce attack surface shared with the host kernel; its relevant protective or investigative effect is to deny unsafe or unused kernel syscalls from a workload.

Incorrect Answers

A:

User mappings reduce the impact of privilege confusion across the container boundary; a team would select it to prevent container UID 0 mapping directly to host UID 0, which does not provide the particular result to deny unsafe or unused kernel syscalls from a workload.

C:

Immutable roots constrain writes while designated runtime data directories can remain mounted separately; applying it would serve prevent a compromised application from changing its packaged code without directly satisfying the goal to deny unsafe or unused kernel syscalls from a workload.

D:

Dropping capabilities limits privilege beyond the container's user identity; it addresses the different need to remove powerful Linux operations not required by a web API, leaving the requested ability to deny unsafe or unused kernel syscalls from a workload unresolved.

Question 580

To prevent container UID 0 mapping directly to host UID 0, which measure best meets the requirement?

  1. Container capability drop
  2. Container egress policy
  3. Runtime container detection
  4. Container seccomp profile
  5. Container user namespace remapping

Explanation

Correct Answer

E:

User mappings reduce the impact of privilege confusion across the container boundary; the requested outcome is precisely to prevent container UID 0 mapping directly to host UID 0.

Incorrect Answers

A:

Dropping capabilities limits privilege beyond the container's user identity; that is useful when the task is to remove powerful Linux operations not required by a web API, not the stated requirement to prevent container UID 0 mapping directly to host UID 0.

B:

Network policy limits potential exfiltration and command channels beyond image-content scanning; a team would select it to stop a processing container calling unauthorized external endpoints, which does not provide the particular result to prevent container UID 0 mapping directly to host UID 0.

C:

Behavioral monitoring detects execution changes that build-time image inspection cannot predict; its operational purpose is to alert when a deployed service unexpectedly launches a shell, not to achieve the specific requirement to prevent container UID 0 mapping directly to host UID 0.

D:

System-call policies reduce attack surface shared with the host kernel; applying it would serve deny unsafe or unused kernel syscalls from a workload without directly satisfying the goal to prevent container UID 0 mapping directly to host UID 0.

Certified Network Defender (312-38) Practice Tests