Question 380New Pods remain Pending across the cluster because the kube-scheduler static Pod is in CrashLoopBackOff. What is the most direct consequence if the underlying problem is left unresolved? Cluster control functions remain unavailable while the API server fails. An administrator may delete the wrong object while the underlying static Pod stays broken. Ready nodes may sit idle while unscheduled workloads accumulate. Resources may stop reconciling even when direct API reads still work. ExplanationCorrect Answer C:Ready nodes may sit idle while unscheduled workloads accumulate. This directly follows from the failed condition. The preventive correction is: Repair the scheduler manifest or configuration after inspecting static Pod logs. The governing Kubernetes behavior is: The scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it.Incorrect Answers A: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: Ready nodes may sit idle while unscheduled workloads accumulate. B:Mirror Pods represent static Pods in the API but are not their source of truth on the node. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Ready nodes may sit idle while unscheduled workloads accumulate. D:The kubelet restarts static control-plane Pods when their manifest changes. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Ready nodes may sit idle while unscheduled workloads accumulate.
Question 381A log-gathering command returns nothing because the responder queried an old namespace after a team migration. An engineer recommends: Resolve the actual namespace and label selector before requesting the current workload's logs. Which Kubernetes behavior best explains why this correction fits? kubectl log filters help isolate relevant events and reduce diagnostic noise. Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis. kubectl resource lookups are namespace-scoped unless explicitly configured otherwise. Restarted containers can have a previous log stream that is distinct from the current one. ExplanationCorrect Answer C:kubectl resource lookups are namespace-scoped unless explicitly configured otherwise. This explains why the proposed action—resolve the actual namespace and label selector before requesting the current workload's logs.—is appropriate. Direct confirmation is: The queried Pods and log lines match the current deployment namespace and time window.Incorrect Answers A:kubectl log filters help isolate relevant events and reduce diagnostic noise. This does not establish the proposed intervention. The governing principle here is: kubectl resource lookups are namespace-scoped unless explicitly configured otherwise. Apply it by: Resolve the actual namespace and label selector before requesting the current workload's logs. B:Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis. This does not establish the proposed intervention. The governing principle here is: kubectl resource lookups are namespace-scoped unless explicitly configured otherwise. Apply it by: Resolve the actual namespace and label selector before requesting the current workload's logs. D:Restarted containers can have a previous log stream that is distinct from the current one. This does not establish the proposed intervention. The governing principle here is: kubectl resource lookups are namespace-scoped unless explicitly configured otherwise. Apply it by: Resolve the actual namespace and label selector before requesting the current workload's logs.
Question 382An application needs a ConfigMap-mounted file to refresh when its ConfigMap changes, but it is mounted using subPath. An engineer recommends: Mount the ConfigMap as a normal projected volume and verify the application's file reload behavior. Which Kubernetes behavior best explains why this correction fits? ConfigMap volumes can update eventually, whereas a subPath-mounted key does not receive automatic updates. ConfigMaps separate nonsecret configuration from the application container image. Secrets are intended for sensitive values but still require RBAC and protection at rest and in use. Secret key references are exact and missing mandatory keys prevent valid container configuration. ExplanationCorrect Answer A:ConfigMap volumes can update eventually, whereas a subPath-mounted key does not receive automatic updates. This explains why the proposed action—mount the ConfigMap as a normal projected volume and verify the application's file reload behavior.—is appropriate. Direct confirmation is: A ConfigMap change appears in the projected file and the application reloads it as intended.Incorrect Answers B:ConfigMaps separate nonsecret configuration from the application container image. This does not establish the proposed intervention. The governing principle here is: ConfigMap volumes can update eventually, whereas a subPath-mounted key does not receive automatic updates. Apply it by: Mount the ConfigMap as a normal projected volume and verify the application's file reload behavior. C:Secrets are intended for sensitive values but still require RBAC and protection at rest and in use. This does not establish the proposed intervention. The governing principle here is: ConfigMap volumes can update eventually, whereas a subPath-mounted key does not receive automatic updates. Apply it by: Mount the ConfigMap as a normal projected volume and verify the application's file reload behavior. D:Secret key references are exact and missing mandatory keys prevent valid container configuration. This does not establish the proposed intervention. The governing principle here is: ConfigMap volumes can update eventually, whereas a subPath-mounted key does not receive automatic updates. Apply it by: Mount the ConfigMap as a normal projected volume and verify the application's file reload behavior.
Question 383An operator reconciles a custom resource but never creates the expected Deployment after its controller Pod crashes. Following the proposed change—Restore the controller/operator and check reconciliation logs and permissions before changing the custom object—which observation best demonstrates that the particular fault is resolved? Controller events show successful status reconciliation without allowing unwanted spec modification. The operator returns healthy and the managed Deployment appears with the expected owner references. Custom instances delete cleanly after their finalizers are processed and dependent resources are reviewed. Impersonated edits fail outside the permitted namespace while intended local access remains. ExplanationCorrect Answer B:The operator returns healthy and the managed Deployment appears with the expected owner references. This validates the stated intervention—restore the controller/operator and check reconciliation logs and permissions before changing the custom object.—rather than an unrelated cluster change. The relevant mechanism is: A CRD defines the API schema while a running controller implements the desired behavior.Incorrect Answers A:Custom resource status updates are separately authorized from spec updates when status is enabled. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The operator returns healthy and the managed Deployment appears with the expected owner references. C:Finalizers block object deletion until the associated controller completes the required cleanup. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The operator returns healthy and the managed Deployment appears with the expected owner references. D:New custom resource types participate in authorization using their API group and scope. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The operator returns healthy and the managed Deployment appears with the expected owner references.
Question 384kubectl cannot reach a recently upgraded control plane and the kube-apiserver static Pod is not running. What is the most direct consequence if the underlying problem is left unresolved? An administrator may delete the wrong object while the underlying static Pod stays broken. Cluster control functions remain unavailable while the API server fails. Ready nodes may sit idle while unscheduled workloads accumulate. Nodes may become isolated from an otherwise running API process. ExplanationCorrect Answer B:Cluster control functions remain unavailable while the API server fails. This directly follows from the failed condition. The preventive correction is: Inspect the kubelet-managed static Pod manifest and its container logs, then repair invalid API server flags. The governing Kubernetes behavior is: kubeadm control-plane components often run as static Pods from local manifests.Incorrect Answers A:Mirror Pods represent static Pods in the API but are not their source of truth on the node. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Cluster control functions remain unavailable while the API server fails. C:The scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Cluster control functions remain unavailable while the API server fails. D:Control-plane advertised addresses must be reachable through the cluster's intended topology. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Cluster control functions remain unavailable while the API server fails.
Question 385An etcd member is removed after a disk failure, but nobody checks whether the remaining members have quorum. Which Kubernetes administration action most directly addresses the observed failure? Distribute control-plane and etcd members across independent failure domains. Design and test multiple control-plane nodes behind a durable API endpoint with compatible etcd quorum. 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 D:Inspect etcd endpoint status and membership before modifying the cluster's voter set. This corrects the specific failure because etcd commits require a majority of voting members; removal and replacement must preserve quorum. Verify it by checking: The member list and endpoint health show an operational majority before and after the change.Incorrect Answers A:Quorum and replication do not protect against a common power or hypervisor failure domain. That is relevant to a different intervention. For the stated situation, the required action is: Inspect etcd endpoint status and membership before modifying the cluster's voter set. The governing reason is: Etcd commits require a majority of voting members; removal and replacement must preserve quorum. B: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: Inspect etcd endpoint status and membership before modifying the cluster's voter set. The governing reason is: Etcd commits require a majority of voting members; removal and replacement must preserve quorum. C:A successful TCP handshake does not prove a particular API server is ready to serve requests. That is relevant to a different intervention. For the stated situation, the required action is: Inspect etcd endpoint status and membership before modifying the cluster's voter set. The governing reason is: Etcd commits require a majority of voting members; removal and replacement must preserve quorum.
Question 386A Pod is repeatedly evicted from a worker reporting PIDPressure but memory and disk look healthy. An engineer recommends: Inspect process counts and runaway process creation, then cap or repair the offending workload. Which Kubernetes behavior best explains why this correction fits? The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests. Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. A node's Ready condition depends on kubelet heartbeats and necessary local runtime services. ExplanationCorrect Answer B:Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. This explains why the proposed action—inspect process counts and runaway process creation, then cap or repair the offending workload.—is appropriate. Direct confirmation is: Process counts fall and the node condition clears while essential services remain alive.Incorrect Answers A:The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests. This does not establish the proposed intervention. The governing principle here is: Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. Apply it by: Inspect process counts and runaway process creation, then cap or repair the offending workload. C:Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. This does not establish the proposed intervention. The governing principle here is: Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. Apply it by: Inspect process counts and runaway process creation, then cap or repair the offending workload. D:A node's Ready condition depends on kubelet heartbeats and necessary local runtime services. This does not establish the proposed intervention. The governing principle here is: Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. Apply it by: Inspect process counts and runaway process creation, then cap or repair the offending workload.
Question 387A control-plane operator assumes a stale mirror Pod status means the kubelet is not running its static Pod. Following the proposed change—Inspect actual local runtime containers and static manifest files as well as API mirror objects—which observation best demonstrates that the particular fault is resolved? The API server static Pod starts and authenticated kubectl requests succeed. The controller-manager stays Running and a Deployment reconciles desired replicas. The scheduler becomes healthy and newly created Pods receive node assignments. Local runtime state, kubelet logs and mirror Pod status reconcile after repair. ExplanationCorrect Answer D:Local runtime state, kubelet logs and mirror Pod status reconcile after repair. This validates the stated intervention—inspect actual local runtime containers and static manifest files as well as API mirror objects.—rather than an unrelated cluster change. The relevant mechanism is: Mirror Pods represent static Pods in the API but are not their source of truth on the node.Incorrect Answers A:kubeadm control-plane components often run as static Pods from local manifests. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Local runtime state, kubelet logs and mirror Pod status reconcile after repair. B:The kubelet restarts static control-plane Pods when their manifest changes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Local runtime state, kubelet logs and mirror Pod status reconcile after repair. C:The scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Local runtime state, kubelet logs and mirror Pod status reconcile after repair.
Question 388Pods can resolve external domains but fail to resolve the names of ClusterIP Services in their namespace. An engineer recommends: Inspect CoreDNS Kubernetes plugin configuration and its access to the cluster API and service domain. Which Kubernetes behavior best explains why this correction fits? Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. CoreDNS must parse its plugin chain before it can serve cluster DNS queries. Pod DNS settings may be generated from kubelet node configuration and dnsPolicy. DNS name resolution is a separate network flow from the application connection. ExplanationCorrect Answer A:Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. This explains why the proposed action—inspect CoreDNS Kubernetes plugin configuration and its access to the cluster API and service domain.—is appropriate. Direct confirmation is: A test Pod resolves the target Service FQDN to its intended ClusterIP.Incorrect Answers B:CoreDNS must parse its plugin chain before it can serve cluster DNS queries. This does not establish the proposed intervention. The governing principle here is: Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. Apply it by: Inspect CoreDNS Kubernetes plugin configuration and its access to the cluster API and service domain. C:Pod DNS settings may be generated from kubelet node configuration and dnsPolicy. This does not establish the proposed intervention. The governing principle here is: Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. Apply it by: Inspect CoreDNS Kubernetes plugin configuration and its access to the cluster API and service domain. D:DNS name resolution is a separate network flow from the application connection. This does not establish the proposed intervention. The governing principle here is: Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. Apply it by: Inspect CoreDNS Kubernetes plugin configuration and its access to the cluster API and service domain.
Question 389An HTTPRoute path match is exact but a team expects it to match nested paths under /api. Which Kubernetes administration action most directly addresses the observed failure? Change parentRefs sectionName or create the intended listener and confirm route attachment status. Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions. Use the intended PathPrefix match semantics and verify path rewriting separately if required. Adjust backendRefs weights and validate rollout percentages before production promotion. ExplanationCorrect Answer C:Use the intended PathPrefix match semantics and verify path rewriting separately if required. This corrects the specific failure because exact and prefix path matches are different routing rules in Gateway API. Verify it by checking: Requests to /api and a child path reach the intended backend while unrelated paths do not.Incorrect Answers A:Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references. That is relevant to a different intervention. For the stated situation, the required action is: Use the intended PathPrefix match semantics and verify path rewriting separately if required. The governing reason is: Exact and prefix path matches are different routing rules in Gateway API. B:Gateway API constrains route attachment and cross-namespace references through explicit policies. That is relevant to a different intervention. For the stated situation, the required action is: Use the intended PathPrefix match semantics and verify path rewriting separately if required. The governing reason is: Exact and prefix path matches are different routing rules in Gateway API. D:Gateway API backend weights influence proportional HTTPRoute forwarding among valid backends. That is relevant to a different intervention. For the stated situation, the required action is: Use the intended PathPrefix match semantics and verify path rewriting separately if required. The governing reason is: Exact and prefix path matches are different routing rules in Gateway API.
Question 390A controller installed by an operator enters a reconciliation loop because its ServiceAccount cannot update the custom resource status subresource. What is the most direct consequence if the underlying problem is left unresolved? The custom object can remain perpetually degraded despite healthy dependencies. Custom resources persist but never result in actual managed workloads. A tenant may reconfigure shared controllers and affect other applications. Resource deployment fails with no matches for kind even though YAML syntax is valid. ExplanationCorrect Answer A:The custom object can remain perpetually degraded despite healthy dependencies. This directly follows from the failed condition. The preventive correction is: Grant the controller the minimum required update or patch permission for the status subresource. The governing Kubernetes behavior is: Custom resource status updates are separately authorized from spec updates when status is enabled.Incorrect Answers 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: The custom object can remain perpetually degraded despite healthy dependencies. C:New custom resource types participate in authorization using their API group and scope. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: The custom object can remain perpetually degraded despite healthy dependencies. D: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: The custom object can remain perpetually degraded despite healthy dependencies.