Question 120A storage policy requires encrypted volumes but an engineer creates a StorageClass without the provider's encryption parameters. Following the proposed change—Define the correct CSI StorageClass parameters and verify the provisioned volume security properties—which observation best demonstrates that the particular fault is resolved? A test PVC becomes Bound and the expected CSI volume is created. A test PV is created with the required encryption setting reported by the storage provider. The PVC is Bound and a consumer on each eligible worker mounts and reads the volume. A new PVC binds in the same topology as its consuming Pod and the Pod starts. ExplanationCorrect Answer B:A test PV is created with the required encryption setting reported by the storage provider. This validates the stated intervention—define the correct CSI StorageClass parameters and verify the provisioned volume security properties.—rather than an unrelated cluster change. The relevant mechanism is: StorageClass parameters are driver-specific and determine backend provisioning behavior.Incorrect Answers A:Dynamic provisioning depends on a controller that recognizes the StorageClass provisioner identifier. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test PV is created with the required encryption setting reported by the storage provider. C:A controller may provision a volume while the node-side CSI plugin is still required to mount it. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test PV is created with the required encryption setting reported by the storage provider. D:Delayed volume binding allows scheduling constraints and storage topology to be considered together. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test PV is created with the required encryption setting reported by the storage provider.
Question 121A node remains NotReady after its certificate expired and the kubelet cannot authenticate to the API server. What is the most direct consequence if the underlying problem is left unresolved? The control plane can lose visibility of an otherwise running host. A reachable API server cannot schedule useful workloads to a runtime-broken node. Workloads may be evicted or remain unschedulable on the affected node. The kubelet may evict Pods when process capacity is exhausted. ExplanationCorrect Answer A:The control plane can lose visibility of an otherwise running host. This directly follows from the failed condition. The preventive correction is: Renew or rotate kubelet client credentials using the supported cluster certificate process. The governing Kubernetes behavior is: Node status updates require authenticated kubelet API requests using valid credentials.Incorrect Answers B:The kubelet must connect to the correct container runtime interface to manage Pod sandboxes. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: The control plane can lose visibility of an otherwise running host. C:A node's Ready condition depends on kubelet heartbeats and necessary local runtime services. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: The control plane can lose visibility of an otherwise running host. D:Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: The control plane can lose visibility of an otherwise running host.
Question 122An operator changes the default StorageClass during a migration and discovers new PVCs use the wrong backend. What is the most direct consequence if the underlying problem is left unresolved? A volume can be created in a zone unreachable by the scheduled Pod. New persistent data may be written to an unintended performance or retention tier. Sensitive application data may be stored on noncompliant volumes. Stateful Pods remain unschedulable without a provisioned volume. ExplanationCorrect Answer B:New persistent data may be written to an unintended performance or retention tier. This directly follows from the failed condition. The preventive correction is: Set exactly the intended default class annotation and specify storageClassName explicitly for critical claims. The governing Kubernetes behavior is: PVCs without a specified class can inherit the cluster's default storage class.Incorrect Answers A:Delayed volume binding allows scheduling constraints and storage topology to be considered together. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: New persistent data may be written to an unintended performance or retention tier. C:StorageClass parameters are driver-specific and determine backend provisioning behavior. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: New persistent data may be written to an unintended performance or retention tier. D:Dynamic provisioning depends on a controller that recognizes the StorageClass provisioner identifier. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: New persistent data may be written to an unintended performance or retention tier.
Question 123A payment Pod can reach internal Services but egress to an external approved API is denied after a policy update. What is the most direct consequence if the underlying problem is left unresolved? One direction may remain blocked or unintentionally open without end-to-end testing. Applications may appear network-isolated because they cannot resolve healthy destinations. Critical integrations can fail even though ingress policies are correct. A blanket allow would erase the intended namespace segmentation. ExplanationCorrect Answer C:Critical integrations can fail even though ingress policies are correct. This directly follows from the failed condition. The preventive correction is: Add an egress rule that permits the required destination range and port while preserving other restrictions. The governing Kubernetes behavior is: An egress-isolated Pod needs an explicit permitted path to each required destination.Incorrect Answers A:Ingress and egress restrictions are evaluated independently and policy effects compose additively. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Critical integrations can fail even though ingress policies are correct. B:DNS name resolution is a separate network flow from the application connection. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Critical integrations can fail even though ingress policies are correct. D:NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Critical integrations can fail even though ingress policies are correct.
Question 124A payment Pod can reach internal Services but egress to an external approved API is denied after a policy update. Which Kubernetes administration action most directly addresses the observed failure? Test both directions, protocols, and the actual CNI implementation after applying the NetworkPolicy. Permit DNS traffic to the intended cluster DNS endpoints under the egress policy. Add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port. Add an egress rule that permits the required destination range and port while preserving other restrictions. ExplanationCorrect Answer D:Add an egress rule that permits the required destination range and port while preserving other restrictions. This corrects the specific failure because an egress-isolated Pod needs an explicit permitted path to each required destination. Verify it by checking: The approved API endpoint is reachable and a disallowed destination remains blocked.Incorrect Answers A:Ingress and egress restrictions are evaluated independently and policy effects compose additively. That is relevant to a different intervention. For the stated situation, the required action is: Add an egress rule that permits the required destination range and port while preserving other restrictions. The governing reason is: An egress-isolated Pod needs an explicit permitted path to each required destination. B:DNS name resolution is a separate network flow from the application connection. That is relevant to a different intervention. For the stated situation, the required action is: Add an egress rule that permits the required destination range and port while preserving other restrictions. The governing reason is: An egress-isolated Pod needs an explicit permitted path to each required destination. C:NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. That is relevant to a different intervention. For the stated situation, the required action is: Add an egress rule that permits the required destination range and port while preserving other restrictions. The governing reason is: An egress-isolated Pod needs an explicit permitted path to each required destination.
Question 125An operator's certificate identity authenticates successfully but kubectl reports forbidden when listing ConfigMaps in the billing namespace. Which Kubernetes administration action most directly addresses the observed failure? Replace wildcard rules with explicit get list watch permissions on the exact resources the collector reads. Replace the cluster-wide binding with a namespaced RoleBinding granting only needed resource verbs. Grant the narrowly required pods/attach or pods/exec subresource verbs according to the approved response workflow. Bind an appropriate namespace-scoped Role to that authenticated user or group after checking the effective identity. ExplanationCorrect Answer D:Bind an appropriate namespace-scoped Role to that authenticated user or group after checking the effective identity. This corrects the specific failure because authentication establishes identity while authorization separately decides permitted API verbs and resources. Verify it by checking: kubectl auth can-i list configmaps -n billing --as=<identity> changes to yes without granting delete rights.Incorrect Answers A:Least-privilege RBAC narrows blast radius by limiting the allowed verbs, resources, and API groups. That is relevant to a different intervention. For the stated situation, the required action is: Bind an appropriate namespace-scoped Role to that authenticated user or group after checking the effective identity. The governing reason is: Authentication establishes identity while authorization separately decides permitted API verbs and resources. B:A RoleBinding restricts a Role or referenced ClusterRole to its own namespace; a ClusterRoleBinding grants across namespaces. That is relevant to a different intervention. For the stated situation, the required action is: Bind an appropriate namespace-scoped Role to that authenticated user or group after checking the effective identity. The governing reason is: Authentication establishes identity while authorization separately decides permitted API verbs and resources. C:RBAC treats interactive Pod subresources separately from operations on the parent Pod resource. That is relevant to a different intervention. For the stated situation, the required action is: Bind an appropriate namespace-scoped Role to that authenticated user or group after checking the effective identity. The governing reason is: Authentication establishes identity while authorization separately decides permitted API verbs and resources.
Question 126A controller installed by an operator enters a reconciliation loop because its ServiceAccount cannot update the custom resource status subresource. Which Kubernetes administration action most directly addresses the observed failure? Restore the controller/operator and check reconciliation logs and permissions before changing the custom object. Restrict custom resource group, kind and namespace verbs using scoped RBAC policies. Grant the controller the minimum required update or patch permission for the status subresource. Review finalizer ownership and perform a supported cleanup sequence before removing the responsible controller. ExplanationCorrect Answer C:Grant the controller the minimum required update or patch permission for the status subresource. This corrects the specific failure because custom resource status updates are separately authorized from spec updates when status is enabled. Verify it by checking: Controller events show successful status reconciliation without allowing unwanted spec modification.Incorrect Answers A:A CRD defines the API schema while a running controller implements the desired behavior. That is relevant to a different intervention. For the stated situation, the required action is: Grant the controller the minimum required update or patch permission for the status subresource. The governing reason is: Custom resource status updates are separately authorized from spec updates when status is enabled. B:New custom resource types participate in authorization using their API group and scope. That is relevant to a different intervention. For the stated situation, the required action is: Grant the controller the minimum required update or patch permission for the status subresource. The governing reason is: Custom resource status updates are separately authorized from spec updates when status is enabled. D:Finalizers block object deletion until the associated controller completes the required cleanup. That is relevant to a different intervention. For the stated situation, the required action is: Grant the controller the minimum required update or patch permission for the status subresource. The governing reason is: Custom resource status updates are separately authorized from spec updates when status is enabled.
Question 127A release of a payment API introduces an invalid image tag and the Deployment cannot complete its rolling update. What is the most direct consequence if the underlying problem is left unresolved? Aggressive replacement can remove serving capacity before new Pods are ready. An unhealthy release can continue serving errors while old replicas disappear. An unverified rollout may leave production partially updated. Finite tasks may execute repeatedly or never report terminal completion. ExplanationCorrect Answer B:An unhealthy release can continue serving errors while old replicas disappear. This directly follows from the failed condition. The preventive correction is: Use rollout history to identify the last healthy revision and roll back the Deployment to it. The governing Kubernetes behavior is: Deployment revisions track supported rollout history and a rollback restores a previous Pod template.Incorrect Answers A:The Deployment rollout strategy controls the allowed temporary excess and unavailable replicas. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An unhealthy release can continue serving errors while old replicas disappear. C:Desired-state changes are asynchronous and a successful API update is not proof of healthy Pods. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An unhealthy release can continue serving errors while old replicas disappear. D:Jobs manage successful completion of finite work; Deployments maintain continuous desired replicas. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An unhealthy release can continue serving errors while old replicas disappear.
Question 128The API server is running but writes fail after etcd loses quorum during maintenance. An engineer recommends: Inspect etcd membership and quorum health, then restore sufficient approved voting members. Which Kubernetes behavior best explains why this correction fits? A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. kubeadm control-plane components often run as static Pods from local manifests. Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. ExplanationCorrect Answer D:Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. This explains why the proposed action—inspect etcd membership and quorum health, then restore sufficient approved voting members.—is appropriate. Direct confirmation is: etcd endpoint health and a safe API create or update operation both succeed.Incorrect Answers A:A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. This does not establish the proposed intervention. The governing principle here is: Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. Apply it by: Inspect etcd membership and quorum health, then restore sufficient approved voting members. B:Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. This does not establish the proposed intervention. The governing principle here is: Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. Apply it by: Inspect etcd membership and quorum health, then restore sufficient approved voting members. C:kubeadm control-plane components often run as static Pods from local manifests. This does not establish the proposed intervention. The governing principle here is: Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. Apply it by: Inspect etcd membership and quorum health, then restore sufficient approved voting members.
Question 129A team wants its viewer ClusterRole to cover a new namespaced custom resource but the permissions do not propagate. Following the proposed change—Update the intended ClusterRole rules or its controlled aggregation labels and verify the bound roles—which observation best demonstrates that the particular fault is resolved? An impersonated authorization check denies deletion in another team's namespace but permits the required local update. The viewer can list only the approved custom resources in the bound namespace after reconciliation. An impersonated service-account access test reads the permitted Secret and rejects unrelated Secrets. Impersonated requests reach the approved subresource and reject unrelated secret reads. ExplanationCorrect Answer B:The viewer can list only the approved custom resources in the bound namespace after reconciliation. This validates the stated intervention—update the intended ClusterRole rules or its controlled aggregation labels and verify the bound roles.—rather than an unrelated cluster change. The relevant mechanism is: Aggregated ClusterRoles rely on matching labels on source ClusterRoles; ordinary ClusterRoles do not aggregate automatically.Incorrect Answers A:A RoleBinding restricts a Role or referenced ClusterRole to its own namespace; a ClusterRoleBinding grants across namespaces. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The viewer can list only the approved custom resources in the bound namespace after reconciliation. C:Kubernetes service accounts do not automatically inherit administrator permissions from the Pod owner. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The viewer can list only the approved custom resources in the bound namespace after reconciliation. D:RBAC treats interactive Pod subresources separately from operations on the parent Pod resource. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The viewer can list only the approved custom resources in the bound namespace after reconciliation.
Question 130A set of Pods is Pending despite low observed CPU because their requested resources exceed allocatable capacity. What is the most direct consequence if the underlying problem is left unresolved? Performance can degrade even when the host has unused CPU. Tuning the wrong node resource may leave the slow service unchanged. One tenant can remain blocked while the overall cluster appears healthy. Capacity decisions based on averages can hide real scheduler fit failures. ExplanationCorrect Answer D:Capacity decisions based on averages can hide real scheduler fit failures. This directly follows from the failed condition. The preventive correction is: Compare kubectl describe Pod scheduling events with node allocatable and total requested resources. The governing Kubernetes behavior is: Scheduling uses resource requests and constraints, not recent utilization percentages alone.Incorrect Answers A:CPU limits may cause throttling independent of overall node idle time. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Capacity decisions based on averages can hide real scheduler fit failures. B:Node-wide utilization can hide a throttled or memory-constrained application container. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Capacity decisions based on averages can hide real scheduler fit failures. C:Cluster-wide aggregates may hide localized resource exhaustion and namespace constraints. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Capacity decisions based on averages can hide real scheduler fit failures.