Question 230An operations team begins worker maintenance by shutting down a node without cordoning or draining workloads. Following the proposed change—Cordon and drain the node using disruption-safe options before maintenance, then uncordon after validation—which observation best demonstrates that the particular fault is resolved? PDB allowedDisruptions increases and a retried drain succeeds without reducing healthy replicas below policy. kubectl get nodes shows Ready without SchedulingDisabled and a test Pod can land there. kubectl version and node reports confirm supported version relationships after the planned sequence. Non-DaemonSet workloads relocate and the maintained node accepts Pods only after uncordon. ExplanationCorrect Answer D:Non-DaemonSet workloads relocate and the maintained node accepts Pods only after uncordon. This validates the stated intervention—cordon and drain the node using disruption-safe options before maintenance, then uncordon after validation.—rather than an unrelated cluster change. The relevant mechanism is: A drain evicts eligible Pods through the API and respects disruption policies unlike abrupt host shutdown.Incorrect Answers A:The eviction API respects PodDisruptionBudget limits for voluntary disruption. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Non-DaemonSet workloads relocate and the maintained node accepts Pods only after uncordon. B:Cordon status prevents new scheduling even when the node is otherwise Ready. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Non-DaemonSet workloads relocate and the maintained node accepts Pods only after uncordon. C: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: Non-DaemonSet workloads relocate and the maintained node accepts Pods only after uncordon.
Question 231A team deletes a PVC expecting to preserve its disk, but the dynamically created PV uses a Delete reclaim policy. Which Kubernetes administration action most directly addresses the observed failure? Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access. Move durable state to a PVC and reserve emptyDir for the lifetime of a Pod. Set the appropriate Retain policy before deleting the claim and plan explicit data recovery or disposal. Use networked persistent storage or node-aware scheduling instead of assuming hostPath is portable. ExplanationCorrect Answer C:Set the appropriate Retain policy before deleting the claim and plan explicit data recovery or disposal. This corrects the specific failure because reclaim policy determines what happens to backend storage after a bound claim is released. Verify it by checking: After PVC deletion, the retained PV and backend volume still exist for approved recovery.Incorrect Answers A:Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. That is relevant to a different intervention. For the stated situation, the required action is: Set the appropriate Retain policy before deleting the claim and plan explicit data recovery or disposal. The governing reason is: Reclaim policy determines what happens to backend storage after a bound claim is released. B:emptyDir follows the Pod lifetime and is removed when that Pod ceases to exist. That is relevant to a different intervention. For the stated situation, the required action is: Set the appropriate Retain policy before deleting the claim and plan explicit data recovery or disposal. The governing reason is: Reclaim policy determines what happens to backend storage after a bound claim is released. D:hostPath refers to a specific node filesystem and does not provide cluster-wide data mobility. That is relevant to a different intervention. For the stated situation, the required action is: Set the appropriate Retain policy before deleting the claim and plan explicit data recovery or disposal. The governing reason is: Reclaim policy determines what happens to backend storage after a bound claim is released.
Question 232A namespace applies a default-deny ingress NetworkPolicy and legitimate frontend-to-backend requests begin timing out. What is the most direct consequence if the underlying problem is left unresolved? Selector confusion can either block legitimate clients or allow unwanted access. Critical integrations can fail even though ingress policies are correct. A blanket allow would erase the intended namespace segmentation. One direction may remain blocked or unintentionally open without end-to-end testing. ExplanationCorrect Answer C:A blanket allow would erase the intended namespace segmentation. This directly follows from the failed condition. The preventive correction is: Add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port. The governing Kubernetes behavior is: NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation.Incorrect Answers A:A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A blanket allow would erase the intended namespace segmentation. B:An egress-isolated Pod needs an explicit permitted path to each required destination. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A blanket allow would erase the intended namespace segmentation. D: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: A blanket allow would erase the intended namespace segmentation.
Question 233The API server advertises an obsolete host IP after an infrastructure migration and workers fail to reconnect. What is the most direct consequence if the underlying problem is left unresolved? Nodes may become isolated from an otherwise running API process. Cluster control functions remain unavailable while the API server fails. A supposedly redundant control plane can provide less resilience than planned. Control loops can stall while the process itself remains Running. ExplanationCorrect Answer A:Nodes may become isolated from an otherwise running API process. This directly follows from the failed condition. The preventive correction is: Correct the supported advertise-address and stable endpoint configuration with matching certificates. The governing Kubernetes behavior is: Control-plane advertised addresses must be reachable through the cluster's intended topology.Incorrect Answers B:kubeadm control-plane components often run as static Pods from local manifests. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Nodes may become isolated from an otherwise running API process. C:A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Nodes may become isolated from an otherwise running API process. D:Control-plane components need functional credentials and narrowly appropriate permissions to reconcile state. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Nodes may become isolated from an otherwise running API process.
Question 234A team installed metrics-server but kubectl top nodes returns an unavailable metrics API error. Which Kubernetes administration action most directly addresses the observed failure? Inspect Pod-level CPU and memory use and component metrics with kubectl top and relevant monitoring. Correlate node memory metrics with Pod usage, cache and eviction conditions before resizing the app. Verify the aggregated metrics APIService and metrics-server connectivity to kubelets. Inspect image filesystem consumption and kubelet garbage collection thresholds before changing policies. ExplanationCorrect Answer C:Verify the aggregated metrics APIService and metrics-server connectivity to kubelets. This corrects the specific failure because kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. Verify it by checking: The APIService is Available and kubectl top displays current node and Pod usage.Incorrect Answers A:Node-wide utilization can hide a throttled or memory-constrained application container. That is relevant to a different intervention. For the stated situation, the required action is: Verify the aggregated metrics APIService and metrics-server connectivity to kubelets. The governing reason is: kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. B:Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. That is relevant to a different intervention. For the stated situation, the required action is: Verify the aggregated metrics APIService and metrics-server connectivity to kubelets. The governing reason is: kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. D:Image storage pressure and image garbage collection are distinct from application CPU demand. That is relevant to a different intervention. For the stated situation, the required action is: Verify the aggregated metrics APIService and metrics-server connectivity to kubelets. The governing reason is: kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics.
Question 235A dynamic PVC stays Pending because its StorageClass provisioner name does not match any installed CSI driver. Following the proposed change—Select a StorageClass with an installed valid provisioner or install the required CSI driver—which observation best demonstrates that the particular fault is resolved? A test PVC becomes Bound and the expected CSI volume is created. The PVC is Bound and a consumer on each eligible worker mounts and reads the volume. A test PV is created with the required encryption setting reported by the storage provider. A test unqualified PVC picks the expected class and critical manifests remain explicit. ExplanationCorrect Answer A:A test PVC becomes Bound and the expected CSI volume is created. This validates the stated intervention—select a StorageClass with an installed valid provisioner or install the required CSI driver.—rather than an unrelated cluster change. The relevant mechanism is: Dynamic provisioning depends on a controller that recognizes the StorageClass provisioner identifier.Incorrect Answers B: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 PVC becomes Bound and the expected CSI volume is created. C:StorageClass parameters are driver-specific and determine backend provisioning behavior. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test PVC becomes Bound and the expected CSI volume is created. D:PVCs without a specified class can inherit the cluster's default storage class. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test PVC becomes Bound and the expected CSI volume is created.
Question 236An Ingress hostname returns the default backend page though the application's ClusterIP Service responds correctly. What is the most direct consequence if the underlying problem is left unresolved? A programmed Gateway can expose no usable route for an application. Traffic can become node-dependent and intermittent. Clients can see connection errors despite successful DNS lookup. Valid backend Pods may be hidden behind incorrect ingress rules. ExplanationCorrect Answer D:Valid backend Pods may be hidden behind incorrect ingress rules. This directly follows from the failed condition. The preventive correction is: Verify ingressClassName, host/path matches and controller reconciliation for the intended Ingress. The governing Kubernetes behavior is: Ingress routing adds a separate HTTP match layer beyond normal Service reachability.Incorrect Answers A:Gateway API status conditions identify attachment or match failures separate from backend Pod readiness. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Valid backend Pods may be hidden behind incorrect ingress rules. B:Service reachability depends on node packet-forwarding rules and network acceptance at entry nodes. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Valid backend Pods may be hidden behind incorrect ingress rules. C:DNS resolution and a Service object do not guarantee a valid ready backend endpoint. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Valid backend Pods may be hidden behind incorrect ingress rules.
Question 237A Helm-managed monitoring release is modified by editing its generated Deployment directly in the cluster. Following the proposed change—Change the values or chart sources and run an approved Helm upgrade to preserve release state—which observation best demonstrates that the particular fault is resolved? The reviewed rendered difference contains only intended resource changes before promotion. The Helm release is absent and remaining CRDs or cluster-scoped resources are explicitly reviewed. The generated manifest includes production image, replicas, namespace and labels without development-only settings. helm get values and rendered manifests show the change, which survives the next upgrade. ExplanationCorrect Answer D:helm get values and rendered manifests show the change, which survives the next upgrade. This validates the stated intervention—change the values or chart sources and run an approved Helm upgrade to preserve release state.—rather than an unrelated cluster change. The relevant mechanism is: Helm's release history and desired manifests should remain the authoritative source for chart-managed resources.Incorrect Answers A:Template rendering plus a values diff exposes chart-side effects before they affect cluster resources. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: helm get values and rendered manifests show the change, which survives the next upgrade. B:Helm tracks release objects, while some custom resources and cluster-scoped artifacts can outlive a namespace. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: helm get values and rendered manifests show the change, which survives the next upgrade. C:Bases compose reusable manifests while overlays encode environment-specific differences. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: helm get values and rendered manifests show the change, which survives the next upgrade.
Question 238A service needs a long database migration at startup and aggressive liveness checks repeatedly kill it before initialization completes. Which Kubernetes administration action most directly addresses the observed failure? Configure a liveness probe that detects a real nonrecovering state with appropriate thresholds. Add a readiness probe that becomes successful only when the application can serve requests. Add a startup probe with an adequate startup budget while retaining later liveness and readiness checks. Assign realistic resource requests and memory limits, then load-test under expected peaks. ExplanationCorrect Answer C:Add a startup probe with an adequate startup budget while retaining later liveness and readiness checks. This corrects the specific failure because startup probes suppress other probe evaluation until the startup check succeeds. Verify it by checking: The application survives its expected initialization duration and later liveness recovery still works.Incorrect Answers A:Liveness failures restart a container; readiness failures alone only affect traffic eligibility. That is relevant to a different intervention. For the stated situation, the required action is: Add a startup probe with an adequate startup budget while retaining later liveness and readiness checks. The governing reason is: Startup probes suppress other probe evaluation until the startup check succeeds. B:A failed readiness probe removes Pod endpoints from Services without necessarily restarting the container. That is relevant to a different intervention. For the stated situation, the required action is: Add a startup probe with an adequate startup budget while retaining later liveness and readiness checks. The governing reason is: Startup probes suppress other probe evaluation until the startup check succeeds. D:Requests guide scheduling while limits constrain runtime resource consumption. That is relevant to a different intervention. For the stated situation, the required action is: Add a startup probe with an adequate startup budget while retaining later liveness and readiness checks. The governing reason is: Startup probes suppress other probe evaluation until the startup check succeeds.
Question 239A control-plane host lacks swap configuration compatible with the kubelet and new Pods remain unscheduled after provisioning. Following the proposed change—Align swap settings and kubelet configuration with supported Kubernetes host prerequisites before join—which observation best demonstrates that the particular fault is resolved? The kubelet starts without swap-related errors and the node becomes Ready. crictl can query the runtime endpoint and a test Pod starts successfully. The endpoint resolves to an active listener and kubeadm discovery succeeds from a worker. kubectl version and node reports confirm supported version relationships after the planned sequence. ExplanationCorrect Answer A:The kubelet starts without swap-related errors and the node becomes Ready. This validates the stated intervention—align swap settings and kubelet configuration with supported Kubernetes host prerequisites before join.—rather than an unrelated cluster change. The relevant mechanism is: Node prerequisites must be consistent with kubelet behavior and runtime support.Incorrect Answers B:The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The kubelet starts without swap-related errors and the node becomes Ready. C:Clients and join operations need a durable API endpoint independent of one control-plane host. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The kubelet starts without swap-related errors and the node becomes Ready. D: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: The kubelet starts without swap-related errors and the node becomes Ready.
Question 240A forensic review needs the last 30 minutes of container output, but an analyst streams an unbounded historical log dump. What is the most direct consequence if the underlying problem is left unresolved? Failures can go undetected because the standard logging path is silent. Image or scheduling failures can be mistaken for silent application crashes. Large unscoped logs can bury the critical event and waste incident time. An incident may be misdiagnosed as application code when an injected sidecar fails. ExplanationCorrect Answer C:Large unscoped logs can bury the critical event and waste incident time. This directly follows from the failed condition. The preventive correction is: Use time-scoped and bounded log retrieval with recorded Pod, container and timestamp context. The governing Kubernetes behavior is: kubectl log filters help isolate relevant events and reduce diagnostic noise.Incorrect Answers A:kubectl logs primarily reads the container runtime's captured stdout and stderr streams. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Large unscoped logs can bury the critical event and waste incident time. B:Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Large unscoped logs can bury the critical event and waste incident time. D:Container logs belong to individual containers even within one Pod. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Large unscoped logs can bury the critical event and waste incident time.