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

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.

Question 581

To avoid placing database passwords in image layers or environment dumps, what control should be selected?

  1. Container user namespace remapping
  2. Runtime container detection
  3. Read-only container root filesystem
  4. Container secrets mounting

Explanation

Correct Answer

D:

Runtime secret delivery isolates credential lifecycle from immutable application artifacts; this choice fits the scenario because the team must avoid placing database passwords in image layers or environment dumps.

Incorrect Answers

A:

User mappings reduce the impact of privilege confusion across the container boundary; it could help someone trying to prevent container UID 0 mapping directly to host UID 0, but the problem is instead to avoid placing database passwords in image layers or environment dumps.

B:

Behavioral monitoring detects execution changes that build-time image inspection cannot predict; that is useful when the task is to alert when a deployed service unexpectedly launches a shell, not the stated requirement to avoid placing database passwords in image layers or environment dumps.

C:

Immutable roots constrain writes while designated runtime data directories can remain mounted separately; a team would select it to prevent a compromised application from changing its packaged code, which does not provide the particular result to avoid placing database passwords in image layers or environment dumps.

Question 582

To stop a processing container calling unauthorized external endpoints and to alert when a deployed service unexpectedly launches a shell, which TWO measures should the defender select? Choose TWO.

  1. Container seccomp profile
  2. Read-only container root filesystem
  3. Runtime container detection
  4. Container user namespace remapping
  5. Container egress policy

Explanation

Correct Answers

C:

Behavioral monitoring detects execution changes that build-time image inspection cannot predict; this is the measure that can alert when a deployed service unexpectedly launches a shell as one of the separately stated outcomes.

E:

Network policy limits potential exfiltration and command channels beyond image-content scanning; this is the measure that can stop a processing container calling unauthorized external endpoints as one of the separately stated outcomes.

Incorrect Answers

A:

System-call policies reduce attack surface shared with the host kernel; although relevant to deny unsafe or unused kernel syscalls from a workload, it does not by itself achieve the required task to stop a processing container calling unauthorized external endpoints and to alert when a deployed service unexpectedly launches a shell.

B:

Immutable roots constrain writes while designated runtime data directories can remain mounted separately; it could help someone trying to prevent a compromised application from changing its packaged code, but the problem is instead to stop a processing container calling unauthorized external endpoints and to alert when a deployed service unexpectedly launches a shell.

D:

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 stop a processing container calling unauthorized external endpoints and to alert when a deployed service unexpectedly launches a shell.

Question 583

To alert when a deployed service unexpectedly launches a shell, which security control is most appropriate?

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

Explanation

Correct Answer

A:

Behavioral monitoring detects execution changes that build-time image inspection cannot predict; it supplies the specific control needed to alert when a deployed service unexpectedly launches a shell.

Incorrect Answers

B:

System-call policies reduce attack surface shared with the host kernel; although relevant to deny unsafe or unused kernel syscalls from a workload, it does not by itself achieve the required task to alert when a deployed service unexpectedly launches a shell.

C:

User mappings reduce the impact of privilege confusion across the container boundary; it could help someone trying to prevent container UID 0 mapping directly to host UID 0, but the problem is instead to alert when a deployed service unexpectedly launches a shell.

D:

Network policy limits potential exfiltration and command channels beyond image-content scanning; that is useful when the task is to stop a processing container calling unauthorized external endpoints, not the stated requirement to alert when a deployed service unexpectedly launches a shell.

Question 584

To stop a namespace developer reading secrets from other workloads, what would a virtualization security engineer implement or use?

  1. Kubernetes RBAC least privilege
  2. Kubernetes audit logging
  3. Kubernetes secrets encryption at rest
  4. Kubernetes NetworkPolicy

Explanation

Correct Answer

A:

API authorization uses roles and bindings to limit resources, verbs and scoped identities; that is why it addresses the operational task to stop a namespace developer reading secrets from other workloads.

Incorrect Answers

B:

Audit records connect requested actions and user identities to control-plane changes; the outcome it supports is to trace API calls that created a privileged role binding, whereas this scenario asks defenders to stop a namespace developer reading secrets from other workloads.

C:

API-server encryption configuration protects secret objects in etcd storage, with careful key governance; although relevant to reduce disclosure of stored cluster secrets from the backing datastore, it does not by itself achieve the required task to stop a namespace developer reading secrets from other workloads.

D:

CNI-enforced policies restrict ingress and egress where the network plugin supports them; it could help someone trying to deny unapproved pod-to-pod connections within a cluster, but the problem is instead to stop a namespace developer reading secrets from other workloads.

Question 585

To deny unapproved pod-to-pod connections within a cluster, which practice addresses that objective?

  1. Kubernetes secrets encryption at rest
  2. Kubernetes NetworkPolicy
  3. Kubernetes audit logging
  4. Pod Security Admission
  5. Kubernetes RBAC least privilege

Explanation

Correct Answer

B:

CNI-enforced policies restrict ingress and egress where the network plugin supports them; its relevant protective or investigative effect is to deny unapproved pod-to-pod connections within a cluster.

Incorrect Answers

A:

API-server encryption configuration protects secret objects in etcd storage, with careful key governance; the technique works for situations involving reduce disclosure of stored cluster secrets from the backing datastore, rather than this need to deny unapproved pod-to-pod connections within a cluster.

C:

Audit records connect requested actions and user identities to control-plane changes; the outcome it supports is to trace API calls that created a privileged role binding, whereas this scenario asks defenders to deny unapproved pod-to-pod connections within a cluster.

D:

Namespace security levels constrain unsafe pod specifications before scheduling; although relevant to reject pods requesting privileged host namespaces under restricted policy, it does not by itself achieve the required task to deny unapproved pod-to-pod connections within a cluster.

E:

API authorization uses roles and bindings to limit resources, verbs and scoped identities; it could help someone trying to stop a namespace developer reading secrets from other workloads, but the problem is instead to deny unapproved pod-to-pod connections within a cluster.

Question 586

To reject pods requesting privileged host namespaces under restricted policy, which tool, policy, or technique is appropriate?

  1. Pod Security Admission
  2. Kubernetes RBAC least privilege
  3. Image admission allowlist
  4. Service account token scope

Explanation

Correct Answer

A:

Namespace security levels constrain unsafe pod specifications before scheduling; the requested outcome is precisely to reject pods requesting privileged host namespaces under restricted policy.

Incorrect Answers

B:

API authorization uses roles and bindings to limit resources, verbs and scoped identities; the technique works for situations involving stop a namespace developer reading secrets from other workloads, rather than this need to reject pods requesting privileged host namespaces under restricted policy.

C:

Admission policy checks image origin and compliance before workload creation; its mechanism supports permit only signed approved registries in production namespaces, while the requested control must be able to reject pods requesting privileged host namespaces under restricted policy.

D:

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 reject pods requesting privileged host namespaces under restricted policy.

Question 587

To reduce disclosure of stored cluster secrets from the backing datastore, what safeguard would be most applicable?

  1. Kubernetes RBAC least privilege
  2. Kubernetes NetworkPolicy
  3. Etcd access isolation
  4. Kubernetes secrets encryption at rest

Explanation

Correct Answer

D:

API-server encryption configuration protects secret objects in etcd storage, with careful key governance; this choice fits the scenario because the team must reduce disclosure of stored cluster secrets from the backing datastore.

Incorrect Answers

A:

API authorization uses roles and bindings to limit resources, verbs and scoped identities; applying it would serve stop a namespace developer reading secrets from other workloads without directly satisfying the goal to reduce disclosure of stored cluster secrets from the backing datastore.

B:

CNI-enforced policies restrict ingress and egress where the network plugin supports them; it addresses the different need to deny unapproved pod-to-pod connections within a cluster, leaving the requested ability to reduce disclosure of stored cluster secrets from the backing datastore unresolved.

C:

Network and credential controls protect Kubernetes state that contains critical configuration and secrets; the technique works for situations involving prevent ordinary workload networks from querying the cluster datastore, rather than this need to reduce disclosure of stored cluster secrets from the backing datastore.

Question 588

To prevent ordinary workload networks from querying the cluster datastore, what is the relevant defensive action?

  1. Kubernetes RBAC least privilege
  2. Kubernetes NetworkPolicy
  3. Etcd access isolation
  4. Kubernetes audit logging

Explanation

Correct Answer

C:

Network and credential controls protect Kubernetes state that contains critical configuration and secrets; this mechanism directly supports the requirement to prevent ordinary workload networks from querying the cluster datastore.

Incorrect Answers

A:

API authorization uses roles and bindings to limit resources, verbs and scoped identities; its operational purpose is to stop a namespace developer reading secrets from other workloads, not to achieve the specific requirement to prevent ordinary workload networks from querying the cluster datastore.

B:

CNI-enforced policies restrict ingress and egress where the network plugin supports them; applying it would serve deny unapproved pod-to-pod connections within a cluster without directly satisfying the goal to prevent ordinary workload networks from querying the cluster datastore.

D:

Audit records connect requested actions and user identities to control-plane changes; the technique works for situations involving trace API calls that created a privileged role binding, rather than this need to prevent ordinary workload networks from querying the cluster datastore.

Question 589

To trace API calls that created a privileged role binding, which option most directly provides the capability?

  1. Pod Security Admission
  2. Image admission allowlist
  3. Cluster certificate rotation
  4. Kubernetes audit logging
  5. Kubernetes NetworkPolicy
  6. Kubernetes namespace quotas

Explanation

Correct Answer

D:

Audit records connect requested actions and user identities to control-plane changes; it supplies the specific control needed to trace API calls that created a privileged role binding.

Incorrect Answers

A:

Namespace security levels constrain unsafe pod specifications before scheduling; a team would select it to reject pods requesting privileged host namespaces under restricted policy, which does not provide the particular result to trace API calls that created a privileged role binding.

B:

Admission policy checks image origin and compliance before workload creation; its operational purpose is to permit only signed approved registries in production namespaces, not to achieve the specific requirement to trace API calls that created a privileged role binding.

C:

Managed certificate lifecycle maintains authentication between control-plane and worker components; applying it would serve replace expiring component certificates without interrupting API trust without directly satisfying the goal to trace API calls that created a privileged role binding.

E:

CNI-enforced policies restrict ingress and egress where the network plugin supports them; the technique works for situations involving deny unapproved pod-to-pod connections within a cluster, rather than this need to trace API calls that created a privileged role binding.

F:

ResourceQuotas and limits constrain aggregate consumption inside an administrative namespace; its mechanism supports keep one team from exhausting shared cluster compute resources, while the requested control must be able to trace API calls that created a privileged role binding.

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.

Certified Network Defender (312-38) Practice Tests