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.
Question 131An operator's certificate identity authenticates successfully but kubectl reports forbidden when listing ConfigMaps in the billing namespace. What is the most direct consequence if the underlying problem is left unresolved? A compromised collector may manipulate arbitrary cluster resources. Legitimate maintenance remains blocked or privileges are broadened unnecessarily. Excess authority can let one team disrupt unrelated workloads. Emergency diagnostics are blocked or an overly broad role exposes workloads. ExplanationCorrect Answer B:Legitimate maintenance remains blocked or privileges are broadened unnecessarily. This directly follows from the failed condition. The preventive correction is: Bind an appropriate namespace-scoped Role to that authenticated user or group after checking the effective identity. The governing Kubernetes behavior is: Authentication establishes identity while authorization separately decides permitted API verbs and resources.Incorrect Answers A:Least-privilege RBAC narrows blast radius by limiting the allowed verbs, resources, and API groups. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Legitimate maintenance remains blocked or privileges are broadened unnecessarily. C:A RoleBinding restricts a Role or referenced ClusterRole to its own namespace; a ClusterRoleBinding grants across namespaces. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Legitimate maintenance remains blocked or privileges are broadened unnecessarily. D:RBAC treats interactive Pod subresources separately from operations on the parent Pod resource. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Legitimate maintenance remains blocked or privileges are broadened unnecessarily.
Question 132A node reports DiskPressure and new Pods cannot be admitted although CPU and memory are available. Which Kubernetes administration action most directly addresses the observed failure? Inspect process counts and runaway process creation, then cap or repair the offending workload. Inspect memory metrics and OOMKilled events, then right-size the Pod and add safe limits or capacity. Inspect taints and remove the unintended taint or use narrowly authorized tolerations. Identify and clean safe image or container filesystem usage and expand capacity if needed. ExplanationCorrect Answer D:Identify and clean safe image or container filesystem usage and expand capacity if needed. This corrects the specific failure because kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. Verify it by checking: Node DiskPressure clears and new Pods are admitted without deleting active volume data.Incorrect Answers A:Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. That is relevant to a different intervention. For the stated situation, the required action is: Identify and clean safe image or container filesystem usage and expand capacity if needed. The governing reason is: Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. B:The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests. That is relevant to a different intervention. For the stated situation, the required action is: Identify and clean safe image or container filesystem usage and expand capacity if needed. The governing reason is: Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. C:Scheduler taints are placement constraints distinct from raw allocatable capacity. That is relevant to a different intervention. For the stated situation, the required action is: Identify and clean safe image or container filesystem usage and expand capacity if needed. The governing reason is: Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization.
Question 133A worker remains marked SchedulingDisabled after maintenance has completed and passed health checks. An engineer recommends: Run the supported uncordon action after validating the kubelet and desired workloads. Which Kubernetes behavior best explains why this correction fits? A drain evicts eligible Pods through the API and respects disruption policies unlike abrupt host shutdown. Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. Cordon status prevents new scheduling even when the node is otherwise Ready. kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command. ExplanationCorrect Answer C:Cordon status prevents new scheduling even when the node is otherwise Ready. This explains why the proposed action—run the supported uncordon action after validating the kubelet and desired workloads.—is appropriate. Direct confirmation is: kubectl get nodes shows Ready without SchedulingDisabled and a test Pod can land there.Incorrect Answers A:A drain evicts eligible Pods through the API and respects disruption policies unlike abrupt host shutdown. This does not establish the proposed intervention. The governing principle here is: Cordon status prevents new scheduling even when the node is otherwise Ready. Apply it by: Run the supported uncordon action after validating the kubelet and desired workloads. B:Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. This does not establish the proposed intervention. The governing principle here is: Cordon status prevents new scheduling even when the node is otherwise Ready. Apply it by: Run the supported uncordon action after validating the kubelet and desired workloads. D:kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command. This does not establish the proposed intervention. The governing principle here is: Cordon status prevents new scheduling even when the node is otherwise Ready. Apply it by: Run the supported uncordon action after validating the kubelet and desired workloads.
Question 134An administrator drains a node but DaemonSet Pods prevent a naive drain command from completing. Which Kubernetes administration action most directly addresses the observed failure? Drain and decommission the old identity cleanly before joining the replacement with a unique node identity. Restore the intended stable node label or update hard node affinity after verifying policy. Use drain with the documented DaemonSet handling and respect eviction and disruption constraints. Identify and clean safe image or container filesystem usage and expand capacity if needed. ExplanationCorrect Answer C:Use drain with the documented DaemonSet handling and respect eviction and disruption constraints. This corrects the specific failure because daemonSet Pods are managed for node coverage and are not treated like ordinary replicated workloads during drain. Verify it by checking: Evictable Pods relocate while the DaemonSet is handled according to the maintenance plan.Incorrect Answers A:Node names are identity keys in the API and stale entries can confuse lifecycle operations. That is relevant to a different intervention. For the stated situation, the required action is: Use drain with the documented DaemonSet handling and respect eviction and disruption constraints. The governing reason is: DaemonSet Pods are managed for node coverage and are not treated like ordinary replicated workloads during drain. B:Hard placement rules require actual matching node labels at scheduling time. That is relevant to a different intervention. For the stated situation, the required action is: Use drain with the documented DaemonSet handling and respect eviction and disruption constraints. The governing reason is: DaemonSet Pods are managed for node coverage and are not treated like ordinary replicated workloads during drain. D:Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. That is relevant to a different intervention. For the stated situation, the required action is: Use drain with the documented DaemonSet handling and respect eviction and disruption constraints. The governing reason is: DaemonSet Pods are managed for node coverage and are not treated like ordinary replicated workloads during drain.
Question 135A release of a payment API introduces an invalid image tag and the Deployment cannot complete its rolling update. Following the proposed change—Use rollout history to identify the last healthy revision and roll back the Deployment to it—which observation best demonstrates that the particular fault is resolved? During a controlled rollout, the configured availability floor is maintained while new Pods become Ready. kubectl rollout status shows the prior revision fully available and application probes succeed. The desired replica count is ready under the new image and old ReplicaSet replicas are reduced. The workload reaches Complete after the expected successful tasks and does not restart indefinitely. ExplanationCorrect Answer B:kubectl rollout status shows the prior revision fully available and application probes succeed. This validates the stated intervention—use rollout history to identify the last healthy revision and roll back the Deployment to it.—rather than an unrelated cluster change. The relevant mechanism 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. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl rollout status shows the prior revision fully available and application probes succeed. C:Desired-state changes are asynchronous and a successful API update is not proof of healthy Pods. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl rollout status shows the prior revision fully available and application probes succeed. D:Jobs manage successful completion of finite work; Deployments maintain continuous desired replicas. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl rollout status shows the prior revision fully available and application probes succeed.
Question 136A cluster dedicates worker nodes to compliance workloads using NoSchedule taints, yet authorized Pods cannot use them. Following the proposed change—Add narrowly scoped matching tolerations and appropriate node placement constraints to the authorized Pods—which observation best demonstrates that the particular fault is resolved? Only intended workloads land on dedicated nodes while unapproved Pods remain excluded. The Pod schedules onto a matching GPU node and a nonmatching node is excluded. Scheduling tests reject nodes that lack the required sovereignty label. The replicas appear across the required topology domains after a controlled reschedule. ExplanationCorrect Answer A:Only intended workloads land on dedicated nodes while unapproved Pods remain excluded. This validates the stated intervention—add narrowly scoped matching tolerations and appropriate node placement constraints to the authorized Pods.—rather than an unrelated cluster change. The relevant mechanism is: Tolerations permit scheduling onto tainted nodes but do not by themselves select those nodes.Incorrect Answers B:The scheduler matches Pod node constraints to node labels and available resources. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Only intended workloads land on dedicated nodes while unapproved Pods remain excluded. C:Preferred affinity influences scoring but is not a hard scheduling constraint. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Only intended workloads land on dedicated nodes while unapproved Pods remain excluded. D:Affinity and spread rules influence placement of replicas across nodes or zones. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Only intended workloads land on dedicated nodes while unapproved Pods remain excluded.
Question 137A replacement worker joins with the same hostname as an existing stale Node object and reconciliation becomes confusing. What is the most direct consequence if the underlying problem is left unresolved? Maintenance can stall or forceful deletion may interrupt required node agents. The control plane can lose visibility of an otherwise running host. Stale identities can mislead operators about capacity and failure locations. Pod evictions and admission failures may continue despite idle CPU. ExplanationCorrect Answer C:Stale identities can mislead operators about capacity and failure locations. This directly follows from the failed condition. The preventive correction is: Drain and decommission the old identity cleanly before joining the replacement with a unique node identity. The governing Kubernetes behavior is: Node names are identity keys in the API and stale entries can confuse lifecycle operations.Incorrect Answers A:DaemonSet Pods are managed for node coverage and are not treated like ordinary replicated workloads during drain. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Stale identities can mislead operators about capacity and failure locations. B: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: Stale identities can mislead operators about capacity and failure locations. D: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: Stale identities can mislead operators about capacity and failure locations.
Question 138A database must be exposed only to workloads inside the cluster but its Service type was changed to LoadBalancer. Following the proposed change—Return to ClusterIP and remove the unnecessary external frontend—which observation best demonstrates that the particular fault is resolved? The Service receives the expected load balancer ingress and end-to-end external probes succeed. DNS lookups return the intended Pod endpoint addresses and stateful clients connect to them. No external load-balancer address exists and internal client traffic succeeds. EndpointSlices list the correct ready Pod addresses and Service calls succeed. ExplanationCorrect Answer C:No external load-balancer address exists and internal client traffic succeeds. This validates the stated intervention—return to ClusterIP and remove the unnecessary external frontend.—rather than an unrelated cluster change. The relevant mechanism is: ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported.Incorrect Answers A:NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: No external load-balancer address exists and internal client traffic succeeds. B: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: No external load-balancer address exists and internal client traffic succeeds. D: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: No external load-balancer address exists and internal client traffic succeeds.
Question 139A service needs a long database migration at startup and aggressive liveness checks repeatedly kill it before initialization completes. What is the most direct consequence if the underlying problem is left unresolved? Pods can remain alive but permanently unable to serve work. Traffic may reach an uninitialized instance and fail transiently. A single Pod may destabilize other workloads sharing the node. Repeated premature restarts can prevent the service from ever becoming ready. ExplanationCorrect Answer D:Repeated premature restarts can prevent the service from ever becoming ready. This directly follows from the failed condition. The preventive correction is: Add a startup probe with an adequate startup budget while retaining later liveness and readiness checks. The governing Kubernetes behavior is: Startup probes suppress other probe evaluation until the startup check succeeds.Incorrect Answers A:Liveness failures restart a container; readiness failures alone only affect traffic eligibility. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Repeated premature restarts can prevent the service from ever becoming ready. B:A failed readiness probe removes Pod endpoints from Services without necessarily restarting the container. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Repeated premature restarts can prevent the service from ever becoming ready. C:Requests guide scheduling while limits constrain runtime resource consumption. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Repeated premature restarts can prevent the service from ever becoming ready.
Question 140A control-plane host's clock drifts and kubelet and API authentication fail with certificate not yet valid errors. Following the proposed change—Restore accurate time synchronization before investigating certificate renewal—which observation best demonstrates that the particular fault is resolved? kubectl establishes a verified TLS session to the intended endpoint without insecure skipping. Worker kubelet connections and administrator requests succeed using current endpoints. Host clocks align and API clients authenticate with existing valid certificates. The controller-manager stays Running and a Deployment reconciles desired replicas. ExplanationCorrect Answer C:Host clocks align and API clients authenticate with existing valid certificates. This validates the stated intervention—restore accurate time synchronization before investigating certificate renewal.—rather than an unrelated cluster change. The relevant mechanism is: TLS certificate validity periods depend on reasonable clock agreement between peers.Incorrect Answers A:Clients validate control-plane TLS certificate identity before trusting API responses. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Host clocks align and API clients authenticate with existing valid certificates. B:Control-plane advertised addresses must be reachable through the cluster's intended topology. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Host clocks align and API clients authenticate with existing valid certificates. D: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: Host clocks align and API clients authenticate with existing valid certificates.