Question 420A Pod can contact other Pods by IP but DNS queries time out after CoreDNS replicas were moved. An engineer recommends: Inspect CoreDNS readiness, Service endpoints and the calling Pod's resolv.conf. Which Kubernetes behavior best explains why this correction fits? Services generally route only to endpoints considered ready, so Pod IP probes do not establish Service capacity. Pod networking can work while the separate cluster DNS service path is unavailable. Per-node DNS cache configuration can produce node-specific resolution failures. StatefulSet per-Pod DNS identity depends on its governing headless Service and stable ordinal names. ExplanationCorrect Answer B:Pod networking can work while the separate cluster DNS service path is unavailable. This explains why the proposed action—inspect CoreDNS readiness, Service endpoints and the calling Pod's resolv.conf.—is appropriate. Direct confirmation is: Known Service names resolve and CoreDNS Pods have ready endpoints with successful queries.Incorrect Answers A:Services generally route only to endpoints considered ready, so Pod IP probes do not establish Service capacity. This does not establish the proposed intervention. The governing principle here is: Pod networking can work while the separate cluster DNS service path is unavailable. Apply it by: Inspect CoreDNS readiness, Service endpoints and the calling Pod's resolv.conf. C:Per-node DNS cache configuration can produce node-specific resolution failures. This does not establish the proposed intervention. The governing principle here is: Pod networking can work while the separate cluster DNS service path is unavailable. Apply it by: Inspect CoreDNS readiness, Service endpoints and the calling Pod's resolv.conf. D:StatefulSet per-Pod DNS identity depends on its governing headless Service and stable ordinal names. This does not establish the proposed intervention. The governing principle here is: Pod networking can work while the separate cluster DNS service path is unavailable. Apply it by: Inspect CoreDNS readiness, Service endpoints and the calling Pod's resolv.conf.
Question 421A Service selector was changed during a deployment rename and kubectl get endpointslice shows no ready endpoints. An engineer recommends: Correct the Service selector to match the intended ready Pod labels. Which Kubernetes behavior best explains why this correction fits? Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. Selector-backed Services route through EndpointSlices populated from matching eligible Pods. Readiness controls endpoint eligibility; Pod phase Running alone does not guarantee serving capacity. ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported. ExplanationCorrect Answer B:Selector-backed Services route through EndpointSlices populated from matching eligible Pods. This explains why the proposed action—correct the Service selector to match the intended ready Pod labels.—is appropriate. Direct confirmation is: EndpointSlices list the correct ready Pod addresses and Service calls succeed.Incorrect Answers A:Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. This does not establish the proposed intervention. The governing principle here is: Selector-backed Services route through EndpointSlices populated from matching eligible Pods. Apply it by: Correct the Service selector to match the intended ready Pod labels. C:Readiness controls endpoint eligibility; Pod phase Running alone does not guarantee serving capacity. This does not establish the proposed intervention. The governing principle here is: Selector-backed Services route through EndpointSlices populated from matching eligible Pods. Apply it by: Correct the Service selector to match the intended ready Pod labels. D:ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported. This does not establish the proposed intervention. The governing principle here is: Selector-backed Services route through EndpointSlices populated from matching eligible Pods. Apply it by: Correct the Service selector to match the intended ready Pod labels.
Question 422A Service sends requests to a Pod that reports Running but fails readiness checks. Following the proposed change—Make the Pod's readiness probe meaningful and confirm only ready endpoints receive traffic—which observation best demonstrates that the particular fault is resolved? EndpointSlices list the correct ready Pod addresses and Service calls succeed. No external load-balancer address exists and internal client traffic succeeds. DNS lookups return the intended Pod endpoint addresses and stateful clients connect to them. EndpointSlices exclude the unready Pod and traffic flows only to healthy replicas. ExplanationCorrect Answer D:EndpointSlices exclude the unready Pod and traffic flows only to healthy replicas. This validates the stated intervention—make the Pod's readiness probe meaningful and confirm only ready endpoints receive traffic.—rather than an unrelated cluster change. The relevant mechanism is: Readiness controls endpoint eligibility; Pod phase Running alone does not guarantee serving capacity.Incorrect Answers A:Selector-backed Services route through EndpointSlices populated from matching eligible Pods. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: EndpointSlices exclude the unready Pod and traffic flows only to healthy replicas. B:ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: EndpointSlices exclude the unready Pod and traffic flows only to healthy replicas. C:A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: EndpointSlices exclude the unready Pod and traffic flows only to healthy replicas.
Question 423A Gateway route splits traffic between two backend Services but weight settings send most requests to an untested canary. Following the proposed change—Adjust backendRefs weights and validate rollout percentages before production promotion—which observation best demonstrates that the particular fault is resolved? HTTPRoute status reports Accepted and traffic matches its intended listener. Observed test traffic approximates approved weights and both backends report ready. The intended route becomes Accepted only from an approved namespace. Requests to /api and a child path reach the intended backend while unrelated paths do not. ExplanationCorrect Answer B:Observed test traffic approximates approved weights and both backends report ready. This validates the stated intervention—adjust backendRefs weights and validate rollout percentages before production promotion.—rather than an unrelated cluster change. The relevant mechanism is: Gateway API backend weights influence proportional HTTPRoute forwarding among valid backends.Incorrect Answers A:Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Observed test traffic approximates approved weights and both backends report ready. C:Gateway API constrains route attachment and cross-namespace references through explicit policies. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Observed test traffic approximates approved weights and both backends report ready. D:Exact and prefix path matches are different routing rules in Gateway API. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Observed test traffic approximates approved weights and both backends report ready.
Question 424A tenant can edit operator configuration custom resources outside its namespace due to a broad custom API RoleBinding. What is the most direct consequence if the underlying problem is left unresolved? Resource deployment fails with no matches for kind even though YAML syntax is valid. Custom resources persist but never result in actual managed workloads. A tenant may reconfigure shared controllers and affect other applications. Custom resources can become stuck Terminating after their controller disappears. ExplanationCorrect Answer C:A tenant may reconfigure shared controllers and affect other applications. This directly follows from the failed condition. The preventive correction is: Restrict custom resource group, kind and namespace verbs using scoped RBAC policies. The governing Kubernetes behavior is: New custom resource types participate in authorization using their API group and scope.Incorrect Answers A:The API server must register an extension type before it can accept objects of that kind. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A tenant may reconfigure shared controllers and affect other applications. B:A CRD defines the API schema while a running controller implements the desired behavior. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A tenant may reconfigure shared controllers and affect other applications. D:Custom resources can become stuck Terminating after their controller disappears. That outcome is tied more directly to this separate failure: An operator installation is removed but its CRDs and custom instances remain with active finalizers. The stated gap instead most directly risks that a tenant may reconfigure shared controllers and affect other applications.
Question 425A Service calls Pods whose readiness probes fail but the team tests only direct Pod IPs and sees partial success. Following the proposed change—Inspect EndpointSlice ready conditions and repair readiness before declaring the Service operational—which observation best demonstrates that the particular fault is resolved? Known Service names resolve and CoreDNS Pods have ready endpoints with successful queries. The route becomes Accepted and requests to the matching host/path receive a valid backend response. The expected number of ready endpoints is present and Service load tests distribute successfully. EndpointSlices list ready Pods and a port-specific request succeeds after selector repair. ExplanationCorrect Answer C:The expected number of ready endpoints is present and Service load tests distribute successfully. This validates the stated intervention—inspect EndpointSlice ready conditions and repair readiness before declaring the Service operational.—rather than an unrelated cluster change. The relevant mechanism is: Services generally route only to endpoints considered ready, so Pod IP probes do not establish Service capacity.Incorrect Answers A:Pod networking can work while the separate cluster DNS service path is unavailable. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The expected number of ready endpoints is present and Service load tests distribute successfully. B:Gateway API status conditions identify attachment or match failures separate from backend Pod readiness. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The expected number of ready endpoints is present and Service load tests distribute successfully. D:DNS resolution and a Service object do not guarantee a valid ready backend endpoint. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The expected number of ready endpoints is present and Service load tests distribute successfully.
Question 426A team installed metrics-server but kubectl top nodes returns an unavailable metrics API error. An engineer recommends: Verify the aggregated metrics APIService and metrics-server connectivity to kubelets. Which Kubernetes behavior best explains why this correction fits? Node-wide utilization can hide a throttled or memory-constrained application container. Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. Image storage pressure and image garbage collection are distinct from application CPU demand. ExplanationCorrect Answer C:kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. This explains why the proposed action—verify the aggregated metrics APIService and metrics-server connectivity to kubelets.—is appropriate. Direct confirmation is: 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. This does not establish the proposed intervention. The governing principle here is: kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. Apply it by: Verify the aggregated metrics APIService and metrics-server connectivity to kubelets. B:Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. This does not establish the proposed intervention. The governing principle here is: kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. Apply it by: Verify the aggregated metrics APIService and metrics-server connectivity to kubelets. D:Image storage pressure and image garbage collection are distinct from application CPU demand. This does not establish the proposed intervention. The governing principle here is: kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. Apply it by: Verify the aggregated metrics APIService and metrics-server connectivity to kubelets.
Question 427CoreDNS Pods restart after a ConfigMap edit introducing an invalid Corefile directive. An engineer recommends: Restore a valid Corefile and validate the CoreDNS configuration before rollout. Which Kubernetes behavior best explains why this correction fits? Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. Pod DNS settings may be generated from kubelet node configuration and dnsPolicy. Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement. CoreDNS must parse its plugin chain before it can serve cluster DNS queries. ExplanationCorrect Answer D:CoreDNS must parse its plugin chain before it can serve cluster DNS queries. This explains why the proposed action—restore a valid Corefile and validate the CoreDNS configuration before rollout.—is appropriate. Direct confirmation is: CoreDNS is Ready with clean logs and a test Pod resolves internal and external names.Incorrect Answers A:Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. This does not establish the proposed intervention. The governing principle here is: CoreDNS must parse its plugin chain before it can serve cluster DNS queries. Apply it by: Restore a valid Corefile and validate the CoreDNS configuration before rollout. B:Pod DNS settings may be generated from kubelet node configuration and dnsPolicy. This does not establish the proposed intervention. The governing principle here is: CoreDNS must parse its plugin chain before it can serve cluster DNS queries. Apply it by: Restore a valid Corefile and validate the CoreDNS configuration before rollout. C:Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement. This does not establish the proposed intervention. The governing principle here is: CoreDNS must parse its plugin chain before it can serve cluster DNS queries. Apply it by: Restore a valid Corefile and validate the CoreDNS configuration before rollout.
Question 428A worker shows MemoryPressure while one batch Pod repeatedly exceeds its memory limit. What is the most direct consequence if the underlying problem is left unresolved? The kubelet may evict Pods when process capacity is exhausted. Pod evictions and admission failures may continue despite idle CPU. Repeated OOM kills can degrade both batch work and neighboring services. The control plane can lose visibility of an otherwise running host. ExplanationCorrect Answer C:Repeated OOM kills can degrade both batch work and neighboring services. This directly follows from the failed condition. The preventive correction is: Inspect memory metrics and OOMKilled events, then right-size the Pod and add safe limits or capacity. The governing Kubernetes behavior is: The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests.Incorrect Answers A: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: Repeated OOM kills can degrade both batch work and neighboring services. B:Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Repeated OOM kills can degrade both batch work and neighboring services. D:Node status updates require authenticated kubelet API requests using valid credentials. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Repeated OOM kills can degrade both batch work and neighboring services.
Question 429A load balancer health check probes only TCP 6443 and continues routing clients to an API server that is not ready. An engineer recommends: Configure a readiness-aware control-plane health check compatible with the API service. Which Kubernetes behavior best explains why this correction fits? Highly available control planes depend on load-balanced API access and durable quorum-backed state. A successful TCP handshake does not prove a particular API server is ready to serve requests. TLS clients verify the endpoint hostname against the presented certificate SANs. Etcd commits require a majority of voting members; removal and replacement must preserve quorum. ExplanationCorrect Answer B:A successful TCP handshake does not prove a particular API server is ready to serve requests. This explains why the proposed action—configure a readiness-aware control-plane health check compatible with the API service.—is appropriate. Direct confirmation is: 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. This does not establish the proposed intervention. The governing principle here is: A successful TCP handshake does not prove a particular API server is ready to serve requests. Apply it by: Configure a readiness-aware control-plane health check compatible with the API service. C:TLS clients verify the endpoint hostname against the presented certificate SANs. This does not establish the proposed intervention. The governing principle here is: A successful TCP handshake does not prove a particular API server is ready to serve requests. Apply it by: Configure a readiness-aware control-plane health check compatible with the API service. D:Etcd commits require a majority of voting members; removal and replacement must preserve quorum. This does not establish the proposed intervention. The governing principle here is: A successful TCP handshake does not prove a particular API server is ready to serve requests. Apply it by: Configure a readiness-aware control-plane health check compatible with the API service.
Question 430A development team asks for expanding a live filesystem PVC but its StorageClass disables allowVolumeExpansion. An engineer recommends: Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow. Which Kubernetes behavior best explains why this correction fits? Dynamic provisioning depends on a controller that recognizes the StorageClass provisioner identifier. A controller may provision a volume while the node-side CSI plugin is still required to mount it. StorageClass parameters are driver-specific and determine backend provisioning behavior. PVC size expansion depends on both StorageClass permission and storage-driver capabilities. ExplanationCorrect Answer D:PVC size expansion depends on both StorageClass permission and storage-driver capabilities. This explains why the proposed action—use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow.—is appropriate. Direct confirmation is: PVC capacity grows to the requested value and the filesystem reports additional usable space.Incorrect Answers A:Dynamic provisioning depends on a controller that recognizes the StorageClass provisioner identifier. This does not establish the proposed intervention. The governing principle here is: PVC size expansion depends on both StorageClass permission and storage-driver capabilities. Apply it by: Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow. B:A controller may provision a volume while the node-side CSI plugin is still required to mount it. This does not establish the proposed intervention. The governing principle here is: PVC size expansion depends on both StorageClass permission and storage-driver capabilities. Apply it by: Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow. C:StorageClass parameters are driver-specific and determine backend provisioning behavior. This does not establish the proposed intervention. The governing principle here is: PVC size expansion depends on both StorageClass permission and storage-driver capabilities. Apply it by: Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow.