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

Question 590

To permit only signed approved registries in production namespaces, which control achieves the target outcome?

  1. Image admission allowlist
  2. Kubernetes audit logging
  3. Pod Security Admission
  4. Etcd access isolation
  5. Kubelet endpoint hardening

Explanation

Correct Answer

A:

Admission policy checks image origin and compliance before workload creation; that is why it addresses the operational task to permit only signed approved registries in production namespaces.

Incorrect Answers

B:

Audit records connect requested actions and user identities to control-plane changes; a team would select it to trace API calls that created a privileged role binding, which does not provide the particular result to permit only signed approved registries in production namespaces.

C:

Namespace security levels constrain unsafe pod specifications before scheduling; its operational purpose is to reject pods requesting privileged host namespaces under restricted policy, not to achieve the specific requirement to permit only signed approved registries in production namespaces.

D:

Network and credential controls protect Kubernetes state that contains critical configuration and secrets; applying it would serve prevent ordinary workload networks from querying the cluster datastore without directly satisfying the goal to permit only signed approved registries in production namespaces.

E:

Authenticated and restricted kubelet APIs protect pod execution and node state; it addresses the different need to stop remote unauthenticated access to node-management functions, leaving the requested ability to permit only signed approved registries in production namespaces unresolved.

Question 591

To prevent every pod inheriting unnecessary Kubernetes API credentials, which solution should be adopted?

  1. Cluster certificate rotation
  2. Image admission allowlist
  3. Etcd access isolation
  4. Service account token scope

Explanation

Correct Answer

D:

Disabling unneeded token mounts narrows identity material available to a compromised container; its relevant protective or investigative effect is to prevent every pod inheriting unnecessary Kubernetes API credentials.

Incorrect Answers

A:

Managed certificate lifecycle maintains authentication between control-plane and worker components; it could help someone trying to replace expiring component certificates without interrupting API trust, but the problem is instead to prevent every pod inheriting unnecessary Kubernetes API credentials.

B:

Admission policy checks image origin and compliance before workload creation; that is useful when the task is to permit only signed approved registries in production namespaces, not the stated requirement to prevent every pod inheriting unnecessary Kubernetes API credentials.

C:

Network and credential controls protect Kubernetes state that contains critical configuration and secrets; a team would select it to prevent ordinary workload networks from querying the cluster datastore, which does not provide the particular result to prevent every pod inheriting unnecessary Kubernetes API credentials.

Question 592

To stop remote unauthenticated access to node-management functions, which of the available controls is suitable?

  1. Kubelet endpoint hardening
  2. Etcd access isolation
  3. Service account token scope
  4. Cluster certificate rotation

Explanation

Correct Answer

A:

Authenticated and restricted kubelet APIs protect pod execution and node state; the requested outcome is precisely to stop remote unauthenticated access to node-management functions.

Incorrect Answers

B:

Network and credential controls protect Kubernetes state that contains critical configuration and secrets; it could help someone trying to prevent ordinary workload networks from querying the cluster datastore, but the problem is instead to stop remote unauthenticated access to node-management functions.

C:

Disabling unneeded token mounts narrows identity material available to a compromised container; that is useful when the task is to prevent every pod inheriting unnecessary Kubernetes API credentials, not the stated requirement to stop remote unauthenticated access to node-management functions.

D:

Managed certificate lifecycle maintains authentication between control-plane and worker components; a team would select it to replace expiring component certificates without interrupting API trust, which does not provide the particular result to stop remote unauthenticated access to node-management functions.

Question 593

To keep one team from exhausting shared cluster compute resources, which option is the direct technical match?

  1. Service account token scope
  2. Kubelet endpoint hardening
  3. Etcd access isolation
  4. Kubernetes namespace quotas

Explanation

Correct Answer

D:

ResourceQuotas and limits constrain aggregate consumption inside an administrative namespace; this choice fits the scenario because the team must keep one team from exhausting shared cluster compute resources.

Incorrect Answers

A:

Disabling unneeded token mounts narrows identity material available to a compromised container; the outcome it supports is to prevent every pod inheriting unnecessary Kubernetes API credentials, whereas this scenario asks defenders to keep one team from exhausting shared cluster compute resources.

B:

Authenticated and restricted kubelet APIs protect pod execution and node state; although relevant to stop remote unauthenticated access to node-management functions, it does not by itself achieve the required task to keep one team from exhausting shared cluster compute resources.

C:

Network and credential controls protect Kubernetes state that contains critical configuration and secrets; it could help someone trying to prevent ordinary workload networks from querying the cluster datastore, but the problem is instead to keep one team from exhausting shared cluster compute resources.

Question 594

To stop remote unauthenticated access to node-management functions, to keep one team from exhausting shared cluster compute resources, and to replace expiring component certificates without interrupting API trust, which THREE measures should the team select? Choose THREE.

  1. Cluster certificate rotation
  2. Kubernetes namespace quotas
  3. Kubernetes audit logging
  4. Kubelet endpoint hardening
  5. Image admission allowlist
  6. Service account token scope

Explanation

Correct Answers

A:

Managed certificate lifecycle maintains authentication between control-plane and worker components; this is the measure that can replace expiring component certificates without interrupting API trust as one of the separately stated outcomes.

B:

ResourceQuotas and limits constrain aggregate consumption inside an administrative namespace; this is the measure that can keep one team from exhausting shared cluster compute resources as one of the separately stated outcomes.

D:

Authenticated and restricted kubelet APIs protect pod execution and node state; this is the measure that can stop remote unauthenticated access to node-management functions as one of the separately stated outcomes.

Incorrect Answers

C:

Audit records connect requested actions and user identities to control-plane changes; although relevant to trace API calls that created a privileged role binding, it does not by itself achieve the required task to stop remote unauthenticated access to node-management functions, to keep one team from exhausting shared cluster compute resources, and to replace expiring component certificates without interrupting API trust.

E:

Admission policy checks image origin and compliance before workload creation; that is useful when the task is to permit only signed approved registries in production namespaces, not the stated requirement to stop remote unauthenticated access to node-management functions, to keep one team from exhausting shared cluster compute resources, and to replace expiring component certificates without interrupting API trust.

F:

Disabling unneeded token mounts narrows identity material available to a compromised container; a team would select it to prevent every pod inheriting unnecessary Kubernetes API credentials, which does not provide the particular result to stop remote unauthenticated access to node-management functions, to keep one team from exhausting shared cluster compute resources, and to replace expiring component certificates without interrupting API trust.

Question 595

To ensure traffic traverses the approved virtual security-function sequence, which approach should a virtualization security engineer choose?

  1. Virtual switch promiscuous mode audit
  2. NFV service-chain integrity
  3. NFV orchestrator privileges
  4. Virtual appliance license validation
  5. Virtual network function patching

Explanation

Correct Answer

B:

Orchestration and path verification prevent bypass of virtual firewall or inspection stages; it supplies the specific control needed to ensure traffic traverses the approved virtual security-function sequence.

Incorrect Answers

A:

Restrictive virtual NIC policies limit unintended packet observation and spoofing behavior; the technique works for situations involving stop an unauthorized guest from receiving other port-group traffic, rather than this need to ensure traffic traverses the approved virtual security-function sequence.

C:

Orchestrator authorization governs creation and topology changes across service resources; the outcome it supports is to limit who can instantiate or remove virtual routing functions, whereas this scenario asks defenders to ensure traffic traverses the approved virtual security-function sequence.

D:

Entitlement monitoring anticipates disabled capabilities that remain otherwise technically configured; although relevant to avoid losing a security feature when a virtual appliance entitlement expires, it does not by itself achieve the required task to ensure traffic traverses the approved virtual security-function sequence.

E:

VNF lifecycle updates protect the software function even when underlying hosts are patched; it could help someone trying to remediate a vulnerable virtual firewall appliance image, but the problem is instead to ensure traffic traverses the approved virtual security-function sequence.

Question 596

To remediate a vulnerable virtual firewall appliance image, which method is designed for the task?

  1. NFV service-chain integrity
  2. NFV orchestrator privileges
  3. Virtual network function patching
  4. Virtual switch promiscuous mode audit

Explanation

Correct Answer

C:

VNF lifecycle updates protect the software function even when underlying hosts are patched; that is why it addresses the operational task to remediate a vulnerable virtual firewall appliance image.

Incorrect Answers

A:

Orchestration and path verification prevent bypass of virtual firewall or inspection stages; it addresses the different need to ensure traffic traverses the approved virtual security-function sequence, leaving the requested ability to remediate a vulnerable virtual firewall appliance image unresolved.

B:

Orchestrator authorization governs creation and topology changes across service resources; the technique works for situations involving limit who can instantiate or remove virtual routing functions, rather than this need to remediate a vulnerable virtual firewall appliance image.

D:

Restrictive virtual NIC policies limit unintended packet observation and spoofing behavior; the outcome it supports is to stop an unauthorized guest from receiving other port-group traffic, whereas this scenario asks defenders to remediate a vulnerable virtual firewall appliance image.

Question 597

To limit who can instantiate or remove virtual routing functions, what technique should the team use?

  1. Virtual appliance license validation
  2. Virtual network function patching
  3. MAC address change controls
  4. NFV orchestrator privileges

Explanation

Correct Answer

D:

Orchestrator authorization governs creation and topology changes across service resources; its relevant protective or investigative effect is to limit who can instantiate or remove virtual routing functions.

Incorrect Answers

A:

Entitlement monitoring anticipates disabled capabilities that remain otherwise technically configured; applying it would serve avoid losing a security feature when a virtual appliance entitlement expires without directly satisfying the goal to limit who can instantiate or remove virtual routing functions.

B:

VNF lifecycle updates protect the software function even when underlying hosts are patched; it addresses the different need to remediate a vulnerable virtual firewall appliance image, leaving the requested ability to limit who can instantiate or remove virtual routing functions unresolved.

C:

Restrictive virtual port-group policy blocks unapproved effective MAC changes, complementing a separate egress forged-transmit check; the technique works for situations involving deny a guest's attempt to change its virtual NIC's effective receive MAC mapping, rather than this need to limit who can instantiate or remove virtual routing functions.

Question 598

To avoid losing a security feature when a virtual appliance entitlement expires, which protective or investigative measure applies?

  1. Virtual appliance license validation
  2. Forged transmit filtering
  3. Virtual network function patching
  4. MAC address change controls

Explanation

Correct Answer

A:

Entitlement monitoring anticipates disabled capabilities that remain otherwise technically configured; the requested outcome is precisely to avoid losing a security feature when a virtual appliance entitlement expires.

Incorrect Answers

B:

Egress source validation limits guest-controlled Layer-2 impersonation; applying it would serve drop VM frames whose source MAC is not authorized on that port without directly satisfying the goal to avoid losing a security feature when a virtual appliance entitlement expires.

C:

VNF lifecycle updates protect the software function even when underlying hosts are patched; it addresses the different need to remediate a vulnerable virtual firewall appliance image, leaving the requested ability to avoid losing a security feature when a virtual appliance entitlement expires unresolved.

D:

Restrictive virtual port-group policy blocks unapproved effective MAC changes, complementing a separate egress forged-transmit check; the technique works for situations involving deny a guest's attempt to change its virtual NIC's effective receive MAC mapping, rather than this need to avoid losing a security feature when a virtual appliance entitlement expires.

Question 599

To stop an unauthorized guest from receiving other port-group traffic, what is the most direct option?

  1. Virtual appliance license validation
  2. Virtual switch promiscuous mode audit
  3. Virtual network function patching
  4. NFV orchestrator privileges

Explanation

Correct Answer

B:

Restrictive virtual NIC policies limit unintended packet observation and spoofing behavior; this choice fits the scenario because the team must stop an unauthorized guest from receiving other port-group traffic.

Incorrect Answers

A:

Entitlement monitoring anticipates disabled capabilities that remain otherwise technically configured; a team would select it to avoid losing a security feature when a virtual appliance entitlement expires, which does not provide the particular result to stop an unauthorized guest from receiving other port-group traffic.

C:

VNF lifecycle updates protect the software function even when underlying hosts are patched; applying it would serve remediate a vulnerable virtual firewall appliance image without directly satisfying the goal to stop an unauthorized guest from receiving other port-group traffic.

D:

Orchestrator authorization governs creation and topology changes across service resources; it addresses the different need to limit who can instantiate or remove virtual routing functions, leaving the requested ability to stop an unauthorized guest from receiving other port-group traffic unresolved.

Question 600

To deny a guest's attempt to change its virtual NIC's effective receive MAC mapping, what should defenders select?

  1. Virtual appliance license validation
  2. Virtual switch promiscuous mode audit
  3. Forged transmit filtering
  4. MAC address change controls
  5. Live-migration channel encryption

Explanation

Correct Answer

D:

Restrictive virtual port-group policy blocks unapproved effective MAC changes, complementing a separate egress forged-transmit check; this mechanism directly supports the requirement to deny a guest's attempt to change its virtual NIC's effective receive MAC mapping.

Incorrect Answers

A:

Entitlement monitoring anticipates disabled capabilities that remain otherwise technically configured; that is useful when the task is to avoid losing a security feature when a virtual appliance entitlement expires, not the stated requirement to deny a guest's attempt to change its virtual NIC's effective receive MAC mapping.

B:

Restrictive virtual NIC policies limit unintended packet observation and spoofing behavior; a team would select it to stop an unauthorized guest from receiving other port-group traffic, which does not provide the particular result to deny a guest's attempt to change its virtual NIC's effective receive MAC mapping.

C:

Egress source validation limits guest-controlled Layer-2 impersonation; its operational purpose is to drop VM frames whose source MAC is not authorized on that port, not to achieve the specific requirement to deny a guest's attempt to change its virtual NIC's effective receive MAC mapping.

E:

Encrypted migration transport reduces exposure of memory pages and credentials in flight; it addresses the different need to protect guest state moving between virtualization hosts, leaving the requested ability to deny a guest's attempt to change its virtual NIC's effective receive MAC mapping unresolved.

Certified Network Defender (312-38) Practice Tests