Question 320A team installed metrics-server but kubectl top nodes returns an unavailable metrics API error. What is the most direct consequence if the underlying problem is left unresolved? Tuning the wrong node resource may leave the slow service unchanged. Operators remain blind to live resource pressure during incidents. Incorrect attribution may cause wasteful scaling and leave the true issue uncorrected. Performance can degrade even when the host has unused CPU. ExplanationCorrect Answer B:Operators remain blind to live resource pressure during incidents. This directly follows from the failed condition. The preventive correction is: Verify the aggregated metrics APIService and metrics-server connectivity to kubelets. The governing Kubernetes behavior is: kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics.Incorrect Answers A: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: Operators remain blind to live resource pressure during incidents. C:Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Operators remain blind to live resource pressure during incidents. D: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: Operators remain blind to live resource pressure during incidents.
Question 321A control-plane host's clock drifts and kubelet and API authentication fail with certificate not yet valid errors. Which Kubernetes administration action most directly addresses the observed failure? Regenerate the affected serving certificate with the actual API endpoint names and rotate it safely. Correct the supported advertise-address and stable endpoint configuration with matching certificates. Restore accurate time synchronization before investigating certificate renewal. Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs. ExplanationCorrect Answer C:Restore accurate time synchronization before investigating certificate renewal. This corrects the specific failure because tLS certificate validity periods depend on reasonable clock agreement between peers. Verify it by checking: Host clocks align and API clients authenticate with existing valid certificates.Incorrect Answers A:Clients validate control-plane TLS certificate identity before trusting API responses. That is relevant to a different intervention. For the stated situation, the required action is: Restore accurate time synchronization before investigating certificate renewal. The governing reason is: TLS certificate validity periods depend on reasonable clock agreement between peers. B:Control-plane advertised addresses must be reachable through the cluster's intended topology. That is relevant to a different intervention. For the stated situation, the required action is: Restore accurate time synchronization before investigating certificate renewal. The governing reason is: TLS certificate validity periods depend on reasonable clock agreement between peers. D:The kubelet restarts static control-plane Pods when their manifest changes. That is relevant to a different intervention. For the stated situation, the required action is: Restore accurate time synchronization before investigating certificate renewal. The governing reason is: TLS certificate validity periods depend on reasonable clock agreement between peers.
Question 322A filesystem volume is mounted read-only by a Pod even though the application needs to write state. What is the most direct consequence if the underlying problem is left unresolved? Replicas may remain Pending or see inconsistent shared content. Persistent application data can be unintentionally destroyed. Pod rescheduling can silently change the data path or expose an empty directory. Application startup can fail with permission-denied errors despite a bound PVC. ExplanationCorrect Answer D:Application startup can fail with permission-denied errors despite a bound PVC. This directly follows from the failed condition. The preventive correction is: Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access. The governing Kubernetes behavior is: Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities.Incorrect Answers A:Kubernetes access modes express requested attachment semantics but cannot add capability to a backend. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Application startup can fail with permission-denied errors despite a bound PVC. B:Reclaim policy determines what happens to backend storage after a bound claim is released. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Application startup can fail with permission-denied errors despite a bound PVC. C:hostPath refers to a specific node filesystem and does not provide cluster-wide data mobility. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Application startup can fail with permission-denied errors despite a bound PVC.
Question 323A cluster operator assumes a CSI plugin handles Pod networking because it is deployed in the kube-system namespace. Which Kubernetes administration action most directly addresses the observed failure? Install and register the proper CSI controller and node plugin for the StorageClass driver. Plan CNI migration with explicit policy and routing compatibility checks and disruption controls. Verify the installed CNI and CSI components separately and test each extension boundary. Validate the CNI dataplane and Pod CIDR routing requirements against the infrastructure before promoting the plugin. ExplanationCorrect Answer C:Verify the installed CNI and CSI components separately and test each extension boundary. This corrects the specific failure because cNI handles networking while CSI handles storage; shared namespaces do not imply interchangeable capabilities. Verify it by checking: Network connectivity and volume mount fixtures independently pass for their respective plugins.Incorrect Answers A:CSI driver registration and controller/node capabilities are required for external volume provisioning and mounting. That is relevant to a different intervention. For the stated situation, the required action is: Verify the installed CNI and CSI components separately and test each extension boundary. The governing reason is: CNI handles networking while CSI handles storage; shared namespaces do not imply interchangeable capabilities. B:Network policy implementations and CNI-specific resources can differ despite common Pod-network requirements. That is relevant to a different intervention. For the stated situation, the required action is: Verify the installed CNI and CSI components separately and test each extension boundary. The governing reason is: CNI handles networking while CSI handles storage; shared namespaces do not imply interchangeable capabilities. D:CNI controls Pod network setup but cross-node reachability also depends on encapsulation or underlay routes. That is relevant to a different intervention. For the stated situation, the required action is: Verify the installed CNI and CSI components separately and test each extension boundary. The governing reason is: CNI handles networking while CSI handles storage; shared namespaces do not imply interchangeable capabilities.
Question 324A volume attachment fails after a node replacement and the Pod remains ContainerCreating although the PVC is Bound. Which Kubernetes administration action most directly addresses the observed failure? Inspect VolumeAttachment objects, CSI controller and node logs, then clear a genuinely stale attachment using the documented driver process. Match the claim's accessModes, storage class and capacity to the intended static PV. Create or reference the PVC in the Pod's own namespace with the approved storage configuration. Use a filesystem-mode volume or configure the consumer for a raw block device consistently. ExplanationCorrect Answer A:Inspect VolumeAttachment objects, CSI controller and node logs, then clear a genuinely stale attachment using the documented driver process. This corrects the specific failure because a Bound PVC proves allocation but not that attach, stage and publish operations have succeeded. Verify it by checking: The storage driver reports successful attachment to the replacement node and the Pod mounts correctly.Incorrect Answers B:A PVC must satisfy PV binding predicates, not merely request a compatible size. That is relevant to a different intervention. For the stated situation, the required action is: Inspect VolumeAttachment objects, CSI controller and node logs, then clear a genuinely stale attachment using the documented driver process. The governing reason is: A Bound PVC proves allocation but not that attach, stage and publish operations have succeeded. C:PVCs are namespace-scoped and Pods cannot mount another namespace's claim by name. That is relevant to a different intervention. For the stated situation, the required action is: Inspect VolumeAttachment objects, CSI controller and node logs, then clear a genuinely stale attachment using the documented driver process. The governing reason is: A Bound PVC proves allocation but not that attach, stage and publish operations have succeeded. D:volumeMode distinguishes raw Block devices from mounted Filesystem volumes. That is relevant to a different intervention. For the stated situation, the required action is: Inspect VolumeAttachment objects, CSI controller and node logs, then clear a genuinely stale attachment using the documented driver process. The governing reason is: A Bound PVC proves allocation but not that attach, stage and publish operations have succeeded.
Question 325A manually managed Service without a selector has no EndpointSlice configured yet the Service IP is expected to proxy connections. An engineer recommends: Create and maintain appropriate EndpointSlice resources with correct labels and target addresses. Which Kubernetes behavior best explains why this correction fits? Selector-backed Services route through EndpointSlices populated from matching eligible Pods. Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. ExplanationCorrect Answer B:Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. This explains why the proposed action—create and maintain appropriate EndpointSlice resources with correct labels and target addresses.—is appropriate. Direct confirmation is: The Service resolves to valid managed endpoints and a test client reaches its backing process.Incorrect Answers A:Selector-backed Services route through EndpointSlices populated from matching eligible Pods. This does not establish the proposed intervention. The governing principle here is: Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. Apply it by: Create and maintain appropriate EndpointSlice resources with correct labels and target addresses. C:NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. This does not establish the proposed intervention. The governing principle here is: Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. Apply it by: Create and maintain appropriate EndpointSlice resources with correct labels and target addresses. D:A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. This does not establish the proposed intervention. The governing principle here is: Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. Apply it by: Create and maintain appropriate EndpointSlice resources with correct labels and target addresses.
Question 326A team creates a NetworkPolicy resource but its chosen CNI has no policy enforcement feature enabled. Which Kubernetes administration action most directly addresses the observed failure? Test both directions, protocols, and the actual CNI implementation after applying the NetworkPolicy. Deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement. Add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port. Permit DNS traffic to the intended cluster DNS endpoints under the egress policy. ExplanationCorrect Answer B:Deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement. This corrects the specific failure because kubernetes accepts policy objects even when a CNI does not implement enforcement. Verify it by checking: A disallowed Pod connection is denied on the network, not merely recorded as a policy object.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: Deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement. The governing reason is: Kubernetes accepts policy objects even when a CNI does not implement enforcement. 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: Deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement. The governing reason is: Kubernetes accepts policy objects even when a CNI does not implement enforcement. D: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: Deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement. The governing reason is: Kubernetes accepts policy objects even when a CNI does not implement enforcement.
Question 327A cluster changes network plugins while still running critical workloads with plugin-specific policy objects. Following the proposed change—Plan CNI migration with explicit policy and routing compatibility checks and disruption controls—which observation best demonstrates that the particular fault is resolved? Pods on different nodes exchange traffic and routes or tunnels reflect the planned topology. Network connectivity and volume mount fixtures independently pass for their respective plugins. Representative policy and cross-node traffic tests pass under the new plugin before retirement of the old one. crictl info succeeds against the configured socket and a test workload starts. ExplanationCorrect Answer C:Representative policy and cross-node traffic tests pass under the new plugin before retirement of the old one. This validates the stated intervention—plan CNI migration with explicit policy and routing compatibility checks and disruption controls.—rather than an unrelated cluster change. The relevant mechanism is: Network policy implementations and CNI-specific resources can differ despite common Pod-network requirements.Incorrect Answers A:CNI controls Pod network setup but cross-node reachability also depends on encapsulation or underlay routes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Representative policy and cross-node traffic tests pass under the new plugin before retirement of the old one. B:CNI handles networking while CSI handles storage; shared namespaces do not imply interchangeable capabilities. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Representative policy and cross-node traffic tests pass under the new plugin before retirement of the old one. D:The container runtime interface is the kubelet's integration boundary for Pod sandboxes and containers. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Representative policy and cross-node traffic tests pass under the new plugin before retirement of the old one.
Question 328A worker remains marked SchedulingDisabled after maintenance has completed and passed health checks. Following the proposed change—Run the supported uncordon action after validating the kubelet and desired workloads—which observation best demonstrates that the particular fault is resolved? Non-DaemonSet workloads relocate and the maintained node accepts Pods only after uncordon. kubectl version and node reports confirm supported version relationships after the planned sequence. kubectl get nodes shows Ready without SchedulingDisabled and a test Pod can land there. The upgrade plan lists the expected target and preflight checks pass before apply. ExplanationCorrect Answer C:kubectl get nodes shows Ready without SchedulingDisabled and a test Pod can land there. This validates the stated intervention—run the supported uncordon action after validating the kubelet and desired workloads.—rather than an unrelated cluster change. The relevant mechanism is: Cordon status prevents new scheduling even when the node is otherwise Ready.Incorrect Answers A:A drain evicts eligible Pods through the API and respects disruption policies unlike abrupt host shutdown. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl get nodes shows Ready without SchedulingDisabled and a test Pod can land there. B:Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl get nodes shows Ready without SchedulingDisabled and a test Pod can land there. D:kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl get nodes shows Ready without SchedulingDisabled and a test Pod can land there.
Question 329An old PV is marked Released after its claim was deleted but an operator assumes it will auto-bind to any new claim. What is the most direct consequence if the underlying problem is left unresolved? The application stays Pending despite available storage elsewhere. A matching-looking volume can remain unused while workloads wait. An invalid dataSource can leave test workloads without a clone or copy. Old claim metadata can block safe reuse or result in accidental data exposure. ExplanationCorrect Answer D:Old claim metadata can block safe reuse or result in accidental data exposure. This directly follows from the failed condition. The preventive correction is: Perform the approved reclaim and rebind procedure, including handling stale claimRef where safe. The governing Kubernetes behavior is: A Released PV may preserve its previous claim reference until an administrator makes it available.Incorrect Answers A:PVCs are namespace-scoped and Pods cannot mount another namespace's claim by name. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Old claim metadata can block safe reuse or result in accidental data exposure. B:A PVC must satisfy PV binding predicates, not merely request a compatible size. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Old claim metadata can block safe reuse or result in accidental data exposure. C:An invalid dataSource can leave test workloads without a clone or copy. That outcome is tied more directly to this separate failure: A team wants to clone a PVC into a test namespace but assumes a PVC dataSource can reference claims across namespaces automatically. The stated gap instead most directly risks that old claim metadata can block safe reuse or result in accidental data exposure.
Question 330A load balancer health check probes only TCP 6443 and continues routing clients to an API server that is not ready. Which Kubernetes administration action most directly addresses the observed failure? Design and test multiple control-plane nodes behind a durable API endpoint with compatible etcd quorum. Issue certificates that include the approved stable API endpoint and node identities. Configure a readiness-aware control-plane health check compatible with the API service. Inspect etcd endpoint status and membership before modifying the cluster's voter set. ExplanationCorrect Answer C:Configure a readiness-aware control-plane health check compatible with the API service. This corrects the specific failure because a successful TCP handshake does not prove a particular API server is ready to serve requests. Verify it by checking: Traffic drains away from an unready instance and remains on ready control-plane backends.Incorrect Answers A:Highly available control planes depend on load-balanced API access and durable quorum-backed state. That is relevant to a different intervention. For the stated situation, the required action is: Configure a readiness-aware control-plane health check compatible with the API service. The governing reason is: A successful TCP handshake does not prove a particular API server is ready to serve requests. B:TLS clients verify the endpoint hostname against the presented certificate SANs. That is relevant to a different intervention. For the stated situation, the required action is: Configure a readiness-aware control-plane health check compatible with the API service. The governing reason is: A successful TCP handshake does not prove a particular API server is ready to serve requests. D:Etcd commits require a majority of voting members; removal and replacement must preserve quorum. That is relevant to a different intervention. For the stated situation, the required action is: Configure a readiness-aware control-plane health check compatible with the API service. The governing reason is: A successful TCP handshake does not prove a particular API server is ready to serve requests.