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.
Question 401A critical workload must never run on nodes missing a data-sovereignty label, yet a preferred affinity rule was used. Which Kubernetes administration action most directly addresses the observed failure? Correct the label selector or intentionally seed the matching workload after validating the placement requirement. Set a nodeSelector or required node affinity matching the available accelerator nodes. Resize requests or provide sufficient eligible nodes based on actual allocatable capacity. Replace preferred affinity with a required node affinity or other enforceable placement policy. ExplanationCorrect Answer D:Replace preferred affinity with a required node affinity or other enforceable placement policy. This corrects the specific failure because preferred affinity influences scoring but is not a hard scheduling constraint. Verify it by checking: Scheduling tests reject nodes that lack the required sovereignty label.Incorrect Answers A:Required pod affinity is a hard predicate and cannot match nonexistent target Pods. That is relevant to a different intervention. For the stated situation, the required action is: Replace preferred affinity with a required node affinity or other enforceable placement policy. The governing reason is: Preferred affinity influences scoring but is not a hard scheduling constraint. B:The scheduler matches Pod node constraints to node labels and available resources. That is relevant to a different intervention. For the stated situation, the required action is: Replace preferred affinity with a required node affinity or other enforceable placement policy. The governing reason is: Preferred affinity influences scoring but is not a hard scheduling constraint. C:The scheduler evaluates Pod requests against node allocatable resources, not observed averages alone. That is relevant to a different intervention. For the stated situation, the required action is: Replace preferred affinity with a required node affinity or other enforceable placement policy. The governing reason is: Preferred affinity influences scoring but is not a hard scheduling constraint.
Question 402A control-plane operator assumes a stale mirror Pod status means the kubelet is not running its static Pod. Which Kubernetes administration action most directly addresses the observed failure? Inspect the kubelet-managed static Pod manifest and its container logs, then repair invalid API server flags. Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs. Inspect actual local runtime containers and static manifest files as well as API mirror objects. Repair the scheduler manifest or configuration after inspecting static Pod logs. ExplanationCorrect Answer C:Inspect actual local runtime containers and static manifest files as well as API mirror objects. This corrects the specific failure because mirror Pods represent static Pods in the API but are not their source of truth on the node. Verify it by checking: Local runtime state, kubelet logs and mirror Pod status reconcile after repair.Incorrect Answers A:kubeadm control-plane components often run as static Pods from local manifests. That is relevant to a different intervention. For the stated situation, the required action is: Inspect actual local runtime containers and static manifest files as well as API mirror objects. The governing reason is: Mirror Pods represent static Pods in the API but are not their source of truth on the node. B:The kubelet restarts static control-plane Pods when their manifest changes. That is relevant to a different intervention. For the stated situation, the required action is: Inspect actual local runtime containers and static manifest files as well as API mirror objects. The governing reason is: Mirror Pods represent static Pods in the API but are not their source of truth on the node. D:The scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it. That is relevant to a different intervention. For the stated situation, the required action is: Inspect actual local runtime containers and static manifest files as well as API mirror objects. The governing reason is: Mirror Pods represent static Pods in the API but are not their source of truth on the node.
Question 403An application has no resource limits and one request can exhaust memory on the node. An engineer recommends: Assign realistic resource requests and memory limits, then load-test under expected peaks. Which Kubernetes behavior best explains why this correction fits? A failed readiness probe removes Pod endpoints from Services without necessarily restarting the container. DaemonSets ensure eligible nodes run a copy of the node-level workload. Startup probes suppress other probe evaluation until the startup check succeeds. Requests guide scheduling while limits constrain runtime resource consumption. ExplanationCorrect Answer D:Requests guide scheduling while limits constrain runtime resource consumption. This explains why the proposed action—assign realistic resource requests and memory limits, then load-test under expected peaks.—is appropriate. Direct confirmation is: The Pod is scheduled with sufficient requested memory and a stress test respects its configured ceiling.Incorrect Answers A:A failed readiness probe removes Pod endpoints from Services without necessarily restarting the container. This does not establish the proposed intervention. The governing principle here is: Requests guide scheduling while limits constrain runtime resource consumption. Apply it by: Assign realistic resource requests and memory limits, then load-test under expected peaks. B:DaemonSets ensure eligible nodes run a copy of the node-level workload. This does not establish the proposed intervention. The governing principle here is: Requests guide scheduling while limits constrain runtime resource consumption. Apply it by: Assign realistic resource requests and memory limits, then load-test under expected peaks. C:Startup probes suppress other probe evaluation until the startup check succeeds. This does not establish the proposed intervention. The governing principle here is: Requests guide scheduling while limits constrain runtime resource consumption. Apply it by: Assign realistic resource requests and memory limits, then load-test under expected peaks.
Question 404A batch service account cannot read a Secret in its own namespace although its Pods use the intended serviceAccountName. What is the most direct consequence if the underlying problem is left unresolved? Emergency diagnostics are blocked or an overly broad role exposes workloads. A partial role leaves administrators without required visibility or tempts broad grants. Excess authority can let one team disrupt unrelated workloads. Broad fallback permissions can expose credentials beyond the job's purpose. ExplanationCorrect Answer D:Broad fallback permissions can expose credentials beyond the job's purpose. This directly follows from the failed condition. The preventive correction is: Bind Secret get permissions only to that service account for the required namespace and named resources when feasible. The governing Kubernetes behavior is: Kubernetes service accounts do not automatically inherit administrator permissions from the Pod owner.Incorrect Answers A: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: Broad fallback permissions can expose credentials beyond the job's purpose. B:Aggregated ClusterRoles rely on matching labels on source ClusterRoles; ordinary ClusterRoles do not aggregate automatically. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Broad fallback permissions can expose credentials beyond the job's purpose. 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: Broad fallback permissions can expose credentials beyond the job's purpose.
Question 405A development team asks for expanding a live filesystem PVC but its StorageClass disables allowVolumeExpansion. Which Kubernetes administration action most directly addresses the observed failure? Select a StorageClass with an installed valid provisioner or install the required CSI driver. Install and verify the CSI node plugin on every eligible attachment node. Use WaitForFirstConsumer binding for topology-constrained storage where supported. Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow. ExplanationCorrect Answer D:Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow. This corrects the specific failure because pVC size expansion depends on both StorageClass permission and storage-driver capabilities. Verify it by checking: 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. That is relevant to a different intervention. For the stated situation, the required action is: Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow. The governing reason is: PVC size expansion depends on both StorageClass permission and storage-driver capabilities. B:A controller may provision a volume while the node-side CSI plugin is still required to mount it. That is relevant to a different intervention. For the stated situation, the required action is: Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow. The governing reason is: PVC size expansion depends on both StorageClass permission and storage-driver capabilities. C:Delayed volume binding allows scheduling constraints and storage topology to be considered together. That is relevant to a different intervention. For the stated situation, the required action is: Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow. The governing reason is: PVC size expansion depends on both StorageClass permission and storage-driver capabilities.
Question 406A newly added control-plane node runs etcd but has not joined the expected quorum member set. An engineer recommends: Use supported etcd member verification and safely add or reconcile the intended member. Which Kubernetes behavior best explains why this correction fits? Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. Control-plane advertised addresses must be reachable through the cluster's intended topology. ExplanationCorrect Answer C:A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. This explains why the proposed action—use supported etcd member verification and safely add or reconcile the intended member.—is appropriate. Direct confirmation is: The membership list includes the new peer and quorum health remains good after failure testing.Incorrect Answers A:Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. This does not establish the proposed intervention. The governing principle here is: A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. Apply it by: Use supported etcd member verification and safely add or reconcile the intended member. B:Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. This does not establish the proposed intervention. The governing principle here is: A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. Apply it by: Use supported etcd member verification and safely add or reconcile the intended member. D:Control-plane advertised addresses must be reachable through the cluster's intended topology. This does not establish the proposed intervention. The governing principle here is: A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. Apply it by: Use supported etcd member verification and safely add or reconcile the intended member.
Question 407A controller-manager static Pod crashes after an administrator edits its command flags in place. Which Kubernetes administration action most directly addresses the observed failure? Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs. Inspect the kubelet-managed static Pod manifest and its container logs, then repair invalid API server flags. Restore the intended component identity and required API authorization rather than granting cluster-admin broadly. Inspect actual local runtime containers and static manifest files as well as API mirror objects. ExplanationCorrect Answer A:Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs. This corrects the specific failure because the kubelet restarts static control-plane Pods when their manifest changes. Verify it by checking: The controller-manager stays Running and a Deployment reconciles desired replicas.Incorrect Answers B:kubeadm control-plane components often run as static Pods from local manifests. That is relevant to a different intervention. For the stated situation, the required action is: Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs. The governing reason is: The kubelet restarts static control-plane Pods when their manifest changes. C:Control-plane components need functional credentials and narrowly appropriate permissions to reconcile state. That is relevant to a different intervention. For the stated situation, the required action is: Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs. The governing reason is: The kubelet restarts static control-plane Pods when their manifest changes. D:Mirror Pods represent static Pods in the API but are not their source of truth on the node. That is relevant to a different intervention. For the stated situation, the required action is: Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs. The governing reason is: The kubelet restarts static control-plane Pods when their manifest changes.
Question 408A worker pool must scale on queue depth but an engineer configures only a CPU utilization HPA. Following the proposed change—Use a suitable custom or external metrics source and scale target based on backlog with validated adapters—which observation best demonstrates that the particular fault is resolved? Controlled queue growth drives replica changes even when CPU remains low. The HPA reports observed utilization and increases replicas during a controlled load. The HPA stops reporting unknown metrics and scales within configured bounds. The workload reaches Complete after the expected successful tasks and does not restart indefinitely. ExplanationCorrect Answer A:Controlled queue growth drives replica changes even when CPU remains low. This validates the stated intervention—use a suitable custom or external metrics source and scale target based on backlog with validated adapters.—rather than an unrelated cluster change. The relevant mechanism is: Different workload bottlenecks require appropriately supported HPA metrics.Incorrect Answers B:HPA CPU utilization calculations depend on resource requests and relevant metrics API data. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Controlled queue growth drives replica changes even when CPU remains low. C:CPU percentage targets use utilization relative to requested CPU, not just absolute node usage. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Controlled queue growth drives replica changes even when CPU remains low. 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: Controlled queue growth drives replica changes even when CPU remains low.
Question 409A site-specific overlay uses Kustomize but the generator emits different ConfigMap names across releases. What is the most direct consequence if the underlying problem is left unresolved? Stale references can strand Pods on nonexistent configuration objects. Production receives unsafe or incomplete development configuration. Unexamined template changes may break unrelated cluster services. Out-of-band edits can be overwritten or create unexplained release drift. ExplanationCorrect Answer A:Stale references can strand Pods on nonexistent configuration objects. This directly follows from the failed condition. The preventive correction is: Use a stable, reviewed generator strategy and update references through supported Kustomize transformations. The governing Kubernetes behavior is: Kustomize may hash generated ConfigMap names to make content changes trigger referential updates.Incorrect Answers B:Bases compose reusable manifests while overlays encode environment-specific differences. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Stale references can strand Pods on nonexistent configuration objects. C:Template rendering plus a values diff exposes chart-side effects before they affect cluster resources. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Stale references can strand Pods on nonexistent configuration objects. D:Helm's release history and desired manifests should remain the authoritative source for chart-managed resources. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Stale references can strand Pods on nonexistent configuration objects.
Question 410A Gateway resource reports Programmed=False even though all HTTPRoute YAML validates. An engineer recommends: Inspect the GatewayClass controller and Gateway listener conditions before debugging application Pods. Which Kubernetes behavior best explains why this correction fits? Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references. Gateway API resources require an implementing controller to provision and program data-plane listeners. Gateway API constrains route attachment and cross-namespace references through explicit policies. Exact and prefix path matches are different routing rules in Gateway API. ExplanationCorrect Answer B:Gateway API resources require an implementing controller to provision and program data-plane listeners. This explains why the proposed action—inspect the GatewayClass controller and Gateway listener conditions before debugging application Pods.—is appropriate. Direct confirmation is: Gateway conditions become Programmed/Accepted and the assigned address receives requests.Incorrect Answers A:Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references. This does not establish the proposed intervention. The governing principle here is: Gateway API resources require an implementing controller to provision and program data-plane listeners. Apply it by: Inspect the GatewayClass controller and Gateway listener conditions before debugging application Pods. C:Gateway API constrains route attachment and cross-namespace references through explicit policies. This does not establish the proposed intervention. The governing principle here is: Gateway API resources require an implementing controller to provision and program data-plane listeners. Apply it by: Inspect the GatewayClass controller and Gateway listener conditions before debugging application Pods. D:Exact and prefix path matches are different routing rules in Gateway API. This does not establish the proposed intervention. The governing principle here is: Gateway API resources require an implementing controller to provision and program data-plane listeners. Apply it by: Inspect the GatewayClass controller and Gateway listener conditions before debugging application Pods.