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.
Question 391A worker's kubeadm join attempt reports an expired bootstrap token obtained from an old onboarding note. Which Kubernetes administration action most directly addresses the observed failure? Generate an appropriate short-lived join token and refreshed discovery command from the current control plane. Regenerate the token-based join command with the expected cluster CA public-key hash. Use the supported kubeadm control-plane join procedure with securely distributed certificate material. Install a compatible CNI after successful kubeadm initialization and validate its daemon components. ExplanationCorrect Answer A:Generate an appropriate short-lived join token and refreshed discovery command from the current control plane. This corrects the specific failure because bootstrap tokens have limited lifetimes and support authenticated discovery during node enrollment. Verify it by checking: The worker joins using a current token and is visible with the intended node identity.Incorrect Answers B:kubeadm discovery pins the trust anchor so a worker does not enroll with the wrong control plane. That is relevant to a different intervention. For the stated situation, the required action is: Generate an appropriate short-lived join token and refreshed discovery command from the current control plane. The governing reason is: Bootstrap tokens have limited lifetimes and support authenticated discovery during node enrollment. C:Additional control-plane nodes require appropriate cluster certificates and an established shared control-plane endpoint. That is relevant to a different intervention. For the stated situation, the required action is: Generate an appropriate short-lived join token and refreshed discovery command from the current control plane. The governing reason is: Bootstrap tokens have limited lifetimes and support authenticated discovery during node enrollment. D:kubeadm bootstraps the control plane but does not provision a complete Pod network plugin by default. That is relevant to a different intervention. For the stated situation, the required action is: Generate an appropriate short-lived join token and refreshed discovery command from the current control plane. The governing reason is: Bootstrap tokens have limited lifetimes and support authenticated discovery during node enrollment.
Question 392An operator applies the development Kustomize base directly into production, bypassing a production-only resource patch. Which Kubernetes administration action most directly addresses the observed failure? Apply the intended production overlay and validate the build output before kubectl apply. Use a stable, reviewed generator strategy and update references through supported Kustomize transformations. Change the values or chart sources and run an approved Helm upgrade to preserve release state. Use release-aware uninstall and explicit resource ownership checks before deleting the namespace. ExplanationCorrect Answer A:Apply the intended production overlay and validate the build output before kubectl apply. This corrects the specific failure because bases compose reusable manifests while overlays encode environment-specific differences. Verify it by checking: The generated manifest includes production image, replicas, namespace and labels without development-only settings.Incorrect Answers B:Kustomize may hash generated ConfigMap names to make content changes trigger referential updates. That is relevant to a different intervention. For the stated situation, the required action is: Apply the intended production overlay and validate the build output before kubectl apply. The governing reason is: Bases compose reusable manifests while overlays encode environment-specific differences. C:Helm's release history and desired manifests should remain the authoritative source for chart-managed resources. That is relevant to a different intervention. For the stated situation, the required action is: Apply the intended production overlay and validate the build output before kubectl apply. The governing reason is: Bases compose reusable manifests while overlays encode environment-specific differences. D:Helm tracks release objects, while some custom resources and cluster-scoped artifacts can outlive a namespace. That is relevant to a different intervention. For the stated situation, the required action is: Apply the intended production overlay and validate the build output before kubectl apply. The governing reason is: Bases compose reusable manifests while overlays encode environment-specific differences.
Question 393A controller-manager static Pod crashes after an administrator edits its command flags in place. An engineer recommends: Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs. Which Kubernetes behavior best explains why this correction fits? kubeadm control-plane components often run as static Pods from local manifests. Control-plane components need functional credentials and narrowly appropriate permissions to reconcile state. The kubelet restarts static control-plane Pods when their manifest changes. Mirror Pods represent static Pods in the API but are not their source of truth on the node. ExplanationCorrect Answer C:The kubelet restarts static control-plane Pods when their manifest changes. This explains why the proposed action—restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs.—is appropriate. Direct confirmation is: The controller-manager stays Running and a Deployment reconciles desired replicas.Incorrect Answers A:kubeadm control-plane components often run as static Pods from local manifests. This does not establish the proposed intervention. The governing principle here is: The kubelet restarts static control-plane Pods when their manifest changes. Apply it by: Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs. B:Control-plane components need functional credentials and narrowly appropriate permissions to reconcile state. This does not establish the proposed intervention. The governing principle here is: The kubelet restarts static control-plane Pods when their manifest changes. Apply it by: Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs. D:Mirror Pods represent static Pods in the API but are not their source of truth on the node. This does not establish the proposed intervention. The governing principle here is: The kubelet restarts static control-plane Pods when their manifest changes. Apply it by: Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs.
Question 394A headless Service was created for a StatefulSet but clients still expect one virtual ClusterIP. What is the most direct consequence if the underlying problem is left unresolved? Clients relying on VIP semantics can fail or choose the wrong replica. An unnecessary public endpoint can expose a sensitive internal database. External clients may remain without a stable supported entry point. A valid Service IP can return no backends indefinitely. ExplanationCorrect Answer A:Clients relying on VIP semantics can fail or choose the wrong replica. This directly follows from the failed condition. The preventive correction is: Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing. The governing Kubernetes behavior is: A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target.Incorrect Answers B:ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Clients relying on VIP semantics can fail or choose the wrong replica. C:NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Clients relying on VIP semantics can fail or choose the wrong replica. D:Selector-backed Services route through EndpointSlices populated from matching eligible Pods. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Clients relying on VIP semantics can fail or choose the wrong replica.
Question 395An HTTPRoute remains Accepted=False and clients get 404 while the Gateway address is reachable. Which Kubernetes administration action most directly addresses the observed failure? Verify ingressClassName, host/path matches and controller reconciliation for the intended Ingress. Inspect EndpointSlice ready conditions and repair readiness before declaring the Service operational. Compare Service selectors, ready EndpointSlices and actual container listener ports. Inspect route parentRefs, listener compatibility and allowedRoutes conditions before changing the backend. ExplanationCorrect Answer D:Inspect route parentRefs, listener compatibility and allowedRoutes conditions before changing the backend. This corrects the specific failure because gateway API status conditions identify attachment or match failures separate from backend Pod readiness. Verify it by checking: The route becomes Accepted and requests to the matching host/path receive a valid backend response.Incorrect Answers A:Ingress routing adds a separate HTTP match layer beyond normal Service reachability. That is relevant to a different intervention. For the stated situation, the required action is: Inspect route parentRefs, listener compatibility and allowedRoutes conditions before changing the backend. The governing reason is: Gateway API status conditions identify attachment or match failures separate from backend Pod readiness. B:Services generally route only to endpoints considered ready, so Pod IP probes do not establish Service capacity. That is relevant to a different intervention. For the stated situation, the required action is: Inspect route parentRefs, listener compatibility and allowedRoutes conditions before changing the backend. The governing reason is: Gateway API status conditions identify attachment or match failures separate from backend Pod readiness. C:DNS resolution and a Service object do not guarantee a valid ready backend endpoint. That is relevant to a different intervention. For the stated situation, the required action is: Inspect route parentRefs, listener compatibility and allowedRoutes conditions before changing the backend. The governing reason is: Gateway API status conditions identify attachment or match failures separate from backend Pod readiness.
Question 396A Pod fails to mount an otherwise Bound PVC because its volumeMode is Block while the application expects a filesystem path. Following the proposed change—Use a filesystem-mode volume or configure the consumer for a raw block device consistently—which observation best demonstrates that the particular fault is resolved? The storage driver reports successful attachment to the replacement node and the Pod mounts correctly. The Pod sees the expected filesystem path or explicitly mapped blockDevice as designed. The PVC binds the expected PV and a consumer Pod mounts it successfully. The Pod's namespace contains the referenced claim and volume mounts successfully. ExplanationCorrect Answer B:The Pod sees the expected filesystem path or explicitly mapped blockDevice as designed. This validates the stated intervention—use a filesystem-mode volume or configure the consumer for a raw block device consistently.—rather than an unrelated cluster change. The relevant mechanism is: volumeMode distinguishes raw Block devices from mounted Filesystem volumes.Incorrect Answers A:A Bound PVC proves allocation but not that attach, stage and publish operations have succeeded. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Pod sees the expected filesystem path or explicitly mapped blockDevice as designed. C:A PVC must satisfy PV binding predicates, not merely request a compatible size. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Pod sees the expected filesystem path or explicitly mapped blockDevice as designed. D:PVCs are namespace-scoped and Pods cannot mount another namespace's claim by name. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Pod sees the expected filesystem path or explicitly mapped blockDevice as designed.
Question 397A critical workload must never run on nodes missing a data-sovereignty label, yet a preferred affinity rule was used. Following the proposed change—Replace preferred affinity with a required node affinity or other enforceable placement policy—which observation best demonstrates that the particular fault is resolved? A matching eligible Pod exists in the specified topology and the new Pod schedules. Scheduling tests reject nodes that lack the required sovereignty label. The Pod schedules onto a matching GPU node and a nonmatching node is excluded. Events no longer report Insufficient memory and the Pod schedules after capacity is corrected. ExplanationCorrect Answer B:Scheduling tests reject nodes that lack the required sovereignty label. This validates the stated intervention—replace preferred affinity with a required node affinity or other enforceable placement policy.—rather than an unrelated cluster change. The relevant mechanism is: Preferred affinity influences scoring but is not a hard scheduling constraint.Incorrect Answers A:Required pod affinity is a hard predicate and cannot match nonexistent target Pods. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Scheduling tests reject nodes that lack the required sovereignty label. C: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: Scheduling tests reject nodes that lack the required sovereignty label. D:The scheduler evaluates Pod requests against node allocatable resources, not observed averages alone. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Scheduling tests reject nodes that lack the required sovereignty label.
Question 398A headless Service was created for a StatefulSet but clients still expect one virtual ClusterIP. An engineer recommends: Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing. Which Kubernetes behavior best explains why this correction fits? ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported. NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. Service port and targetPort describe different ends of the virtual forwarding path. A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. ExplanationCorrect Answer D:A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. This explains why the proposed action—document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing.—is appropriate. Direct confirmation is: DNS lookups return the intended Pod endpoint addresses and stateful clients connect to them.Incorrect Answers A: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: A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. Apply it by: Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing. B: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: A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. Apply it by: Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing. C:Service port and targetPort describe different ends of the virtual forwarding path. This does not establish the proposed intervention. The governing principle here is: A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. Apply it by: Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing.
Question 399A Pod is rejected by a ResourceQuota admission check after a team asks for more replicas. Following the proposed change—Review namespace quota usage and grant resources or adjust workload requests within approved limits—which observation best demonstrates that the particular fault is resolved? The Deployment replicas become admitted after quota headroom is available and usage remains within policy. The Pod schedules onto a matching GPU node and a nonmatching node is excluded. The replicas appear across the required topology domains after a controlled reschedule. Events no longer report Insufficient memory and the Pod schedules after capacity is corrected. ExplanationCorrect Answer A:The Deployment replicas become admitted after quota headroom is available and usage remains within policy. This validates the stated intervention—review namespace quota usage and grant resources or adjust workload requests within approved limits.—rather than an unrelated cluster change. The relevant mechanism is: ResourceQuota admission enforces aggregate namespace constraints when objects are created.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: The Deployment replicas become admitted after quota headroom is available and usage remains within policy. C: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: The Deployment replicas become admitted after quota headroom is available and usage remains within policy. D:The scheduler evaluates Pod requests against node allocatable resources, not observed averages alone. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Deployment replicas become admitted after quota headroom is available and usage remains within policy.
Question 400A Secret update is expected to replace a running process's environment value immediately without restarting the container. Following the proposed change—Roll out the workload or make the application reread supported projected files as required—which observation best demonstrates that the particular fault is resolved? The Pod starts and its injected environment contains the intended credential key value. A new environment receives the intended host configuration without rebuilding the image. Only approved service accounts can read the Secret and the Pod consumes the intended key. New Pods use the updated Secret value and old processes terminate in a controlled rollout. ExplanationCorrect Answer D:New Pods use the updated Secret value and old processes terminate in a controlled rollout. This validates the stated intervention—roll out the workload or make the application reread supported projected files as required.—rather than an unrelated cluster change. The relevant mechanism is: Environment variables sourced from Secrets are fixed for the lifetime of a container process.Incorrect Answers A:Secret key references are exact and missing mandatory keys prevent valid container configuration. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: New Pods use the updated Secret value and old processes terminate in a controlled rollout. B:ConfigMaps separate nonsecret configuration from the application container image. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: New Pods use the updated Secret value and old processes terminate in a controlled rollout. C:Secrets are intended for sensitive values but still require RBAC and protection at rest and in use. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: New Pods use the updated Secret value and old processes terminate in a controlled rollout.