Question 370
Teams pull base images from a registry without knowing whether packaged libraries contain publicly disclosed vulnerabilities. Which container security control best addresses the weakness?
- Read-only root filesystem
- Run containers as non-root
- Drop unnecessary Linux capabilities
- Container image vulnerability scanning
- Container seccomp profile
Explanation
Correct Answer
D:Image scanning compares OS and software components with vulnerability data. Rebuilds and runtime verification ensure fixes reach workloads.
Incorrect Answers
A:A read-only root filesystem limits writable areas in a container when analysts encounter unauthorized modification of container image contents; this question instead describes vulnerabilities in packaged container layers.
B:Non-root execution limits process authority inside a container and reduces certain escape consequences in a setting defined by excessive root identity inside container; the observed issue is vulnerabilities in packaged container layers.
C:Capability reduction removes selected privileged operations from container processes in a setting defined by excessive kernel privileges in application containers; the observed issue is vulnerabilities in packaged container layers.
E:Seccomp filters constrain Linux system calls available to a container process for situations characterized by syscall attack surface exposed to container; the case points instead to vulnerabilities in packaged container layers.
Question 371
A Docker job runs with broad host-device access even though it only needs to process files within its own workspace. Which Docker runtime or build safeguard should be applied?
- Avoid privileged containers
- Docker daemon TLS protection
- Multi-stage Docker build
- Restrict Docker socket mounts
Explanation
Correct Answer
A:Privileged mode relaxes key container isolation limits and can expose host resources. Narrow explicit permissions are safer.
Incorrect Answers
B:Authenticated TLS and tight network access protect daemon APIs from unauthorized privileged requests; this characterizes unprotected remote container-engine API, whereas the reported condition is unrestricted host capabilities for Docker job.
C:Multi-stage builds copy only necessary artifacts into a smaller runtime image, reducing excess software and secret exposure in a setting defined by unnecessary build material in runtime image; the observed issue is unrestricted host capabilities for Docker job.
D:Docker daemon access is highly privileged and can enable host compromise for the specific concern of in-container control of Docker daemon, not the requirement involving unrestricted host capabilities for Docker job.
Question 372
An application container can use the host's Docker control socket, allowing it to create new powerful containers. Which Docker runtime or build safeguard should be applied?
- Pin Docker base-image digest
- Avoid privileged containers
- Restrict Docker socket mounts
- Docker daemon TLS protection
Explanation
Correct Answer
C:Docker daemon access is highly privileged and can enable host compromise. Avoid exposing the socket to untrusted workloads.
Incorrect Answers
A:Digest pinning selects exact image content; this characterizes mutable upstream image tag drift, whereas the reported condition is in-container control of Docker daemon.
B:Privileged mode relaxes key container isolation limits and can expose host resources; this characterizes unrestricted host capabilities for Docker job, whereas the reported condition is in-container control of Docker daemon.
D:Authenticated TLS and tight network access protect daemon APIs from unauthorized privileged requests for the specific concern of unprotected remote container-engine API, not the requirement involving in-container control of Docker daemon.
Question 373
A final application image accidentally includes build toolchains, source files and temporary credentials from the compilation stage. Which Docker runtime or build safeguard should be applied?
- Restrict Docker socket mounts
- Multi-stage Docker build
- Avoid privileged containers
- Docker daemon TLS protection
Explanation
Correct Answer
B:Multi-stage builds copy only necessary artifacts into a smaller runtime image, reducing excess software and secret exposure.
Incorrect Answers
A:Docker daemon access is highly privileged and can enable host compromise; the operational difference is in-container control of Docker daemon versus the scenario's unnecessary build material in runtime image.
C:Privileged mode relaxes key container isolation limits and can expose host resources; the operational difference is unrestricted host capabilities for Docker job versus the scenario's unnecessary build material in runtime image.
D:Authenticated TLS and tight network access protect daemon APIs from unauthorized privileged requests; that is relevant to unprotected remote container-engine API but does not directly account for unnecessary build material in runtime image.
Question 374
Builds unpredictably change after a mutable image tag points to a different upstream release. Two additional independently scoped requirements involve unrestricted host capabilities for Docker job and unnecessary build material in runtime image. Which THREE of the listed approaches correspond to all three needs? Choose THREE.
- Avoid privileged containers
- Pin Docker base-image digest
- Multi-stage Docker build
- Restrict Docker socket mounts
- Docker daemon TLS protection
Explanation
Correct Answers
A:Privileged mode relaxes key container isolation limits and can expose host resources; this specifically explains unrestricted host capabilities for Docker job among the independent requirements in the combined case.
B:Digest pinning selects exact image content; for this multi-part scenario, the pertinent observation is mutable upstream image tag drift.
C:Multi-stage builds copy only necessary artifacts into a smaller runtime image, reducing excess software and secret exposure; this specifically explains unnecessary build material in runtime image among the independent requirements in the combined case.
Incorrect Answers
D:Docker daemon access is highly privileged and can enable host compromise; it handles in-container control of Docker daemon, while the decisive evidence in the question is mutable upstream image tag drift and unrestricted host capabilities for Docker job and unnecessary build material in runtime image.
E:Authenticated TLS and tight network access protect daemon APIs from unauthorized privileged requests; it handles unprotected remote container-engine API, while the decisive evidence in the question is mutable upstream image tag drift and unrestricted host capabilities for Docker job and unnecessary build material in runtime image.
Question 375
Remote Docker administration currently uses an unsecured TCP endpoint that could grant control of the container host. Which Docker runtime or build safeguard should be applied?
- Avoid privileged containers
- Docker daemon TLS protection
- Pin Docker base-image digest
- Restrict Docker socket mounts
- Multi-stage Docker build
Explanation
Correct Answer
B:Authenticated TLS and tight network access protect daemon APIs from unauthorized privileged requests. Local socket permissions also matter.
Incorrect Answers
A:Privileged mode relaxes key container isolation limits and can expose host resources; the operational difference is unrestricted host capabilities for Docker job versus the scenario's unprotected remote container-engine API.
C:Digest pinning selects exact image content when analysts encounter mutable upstream image tag drift; this question instead describes unprotected remote container-engine API.
D:Docker daemon access is highly privileged and can enable host compromise in a setting defined by in-container control of Docker daemon; the observed issue is unprotected remote container-engine API.
E:Multi-stage builds copy only necessary artifacts into a smaller runtime image, reducing excess software and secret exposure for the specific concern of unnecessary build material in runtime image, not the requirement involving unprotected remote container-engine API.
Question 376
Pods in different namespaces communicate freely, but only a documented set of application-to-database flows should be allowed. Which Kubernetes security measure is most appropriate?
- Admission policy enforcement
- Kubernetes NetworkPolicy
- Kubernetes RBAC
- Kubernetes audit logging
Explanation
Correct Answer
B:NetworkPolicy defines allowed pod ingress and egress where supported by the network plugin. A capable enforcement implementation is required.
Incorrect Answers
A:Admission controllers evaluate API requests against policies, preventing disallowed workloads from entering the cluster; that is relevant to blocking unsafe resource definitions at admission but does not directly account for east-west pod communication rules.
C:Kubernetes RBAC binds roles to subjects at appropriate scopes, reducing excessive API authorization for the specific concern of excessive Kubernetes API privileges, not the requirement involving east-west pod communication rules.
D:Kubernetes audit policy records configured API actions and actors, supporting investigation of control-plane changes for the specific concern of API server control-plane activity evidence, not the requirement involving east-west pod communication rules.
Question 377
Developers can delete secrets and deployments clusterwide despite requiring changes only in their assigned namespace. Which Kubernetes security measure is most appropriate?
- Kubernetes Secrets encryption at rest
- Kubernetes NetworkPolicy
- Kubernetes audit logging
- Kubernetes RBAC
Explanation
Correct Answer
D:Kubernetes RBAC binds roles to subjects at appropriate scopes, reducing excessive API authorization. Audit effective permissions.
Incorrect Answers
A:Kubernetes can encrypt sensitive resource data at rest through configured encryption providers; that is relevant to confidentiality of secrets stored in etcd but does not directly account for excessive Kubernetes API privileges.
B:NetworkPolicy defines allowed pod ingress and egress where supported by the network plugin; the operational difference is east-west pod communication rules versus the scenario's excessive Kubernetes API privileges.
C:Kubernetes audit policy records configured API actions and actors, supporting investigation of control-plane changes for the specific concern of API server control-plane activity evidence, not the requirement involving excessive Kubernetes API privileges.
Question 378
Engineers repeatedly submit privileged pod specifications, and security must reject noncompliant resources before creation. Which Kubernetes security measure is most appropriate?
- Kubernetes audit logging
- Admission policy enforcement
- Kubernetes NetworkPolicy
- Kubernetes RBAC
Explanation
Correct Answer
B:Admission controllers evaluate API requests against policies, preventing disallowed workloads from entering the cluster.
Incorrect Answers
A:Kubernetes audit policy records configured API actions and actors, supporting investigation of control-plane changes; the operational difference is API server control-plane activity evidence versus the scenario's blocking unsafe resource definitions at admission.
C:NetworkPolicy defines allowed pod ingress and egress where supported by the network plugin; that is relevant to east-west pod communication rules but does not directly account for blocking unsafe resource definitions at admission.
D:Kubernetes RBAC binds roles to subjects at appropriate scopes, reducing excessive API authorization; it handles excessive Kubernetes API privileges, while the decisive evidence in the question is blocking unsafe resource definitions at admission.
Question 379
Cluster administrators worry that copied etcd storage might expose stored secret values without additional storage-layer safeguards. Which Kubernetes security measure is most appropriate?
- Kubernetes audit logging
- Kubernetes RBAC
- Admission policy enforcement
- Kubernetes Secrets encryption at rest
Explanation
Correct Answer
D:Kubernetes can encrypt sensitive resource data at rest through configured encryption providers. API permissions and key handling still matter.
Incorrect Answers
A:Kubernetes audit policy records configured API actions and actors, supporting investigation of control-plane changes for the specific concern of API server control-plane activity evidence, not the requirement involving confidentiality of secrets stored in etcd.
B:Kubernetes RBAC binds roles to subjects at appropriate scopes, reducing excessive API authorization when analysts encounter excessive Kubernetes API privileges; this question instead describes confidentiality of secrets stored in etcd.
C:Admission controllers evaluate API requests against policies, preventing disallowed workloads from entering the cluster for situations characterized by blocking unsafe resource definitions at admission; the case points instead to confidentiality of secrets stored in etcd.
Question 380
An unknown identity changed a cluster role and the SOC needs request-level evidence from the API server. Which Kubernetes security measure is most appropriate?
- Kubernetes RBAC
- Kubernetes audit logging
- Admission policy enforcement
- Kubernetes Secrets encryption at rest
- Kubernetes NetworkPolicy
Explanation
Correct Answer
B:Kubernetes audit policy records configured API actions and actors, supporting investigation of control-plane changes. Log delivery should resist tampering.
Incorrect Answers
A:Kubernetes RBAC binds roles to subjects at appropriate scopes, reducing excessive API authorization when analysts encounter excessive Kubernetes API privileges; this question instead describes API server control-plane activity evidence.
C:Admission controllers evaluate API requests against policies, preventing disallowed workloads from entering the cluster; this characterizes blocking unsafe resource definitions at admission, whereas the reported condition is API server control-plane activity evidence.
D:Kubernetes can encrypt sensitive resource data at rest through configured encryption providers; this characterizes confidentiality of secrets stored in etcd, whereas the reported condition is API server control-plane activity evidence.
E:NetworkPolicy defines allowed pod ingress and egress where supported by the network plugin; its distinguishing scope is east-west pod communication rules, not the reported API server control-plane activity evidence.