Question 80A database PVC is created using ReadWriteOnce and two Pods on different nodes both expect simultaneous independent writes. Following the proposed change—Choose an access mode and storage backend compatible with the intended attach and sharing semantics—which observation best demonstrates that the particular fault is resolved? Pods on different workers simultaneously read and write a shared test file where supported. The selected topology and access mode permit the intended writer pattern under a controlled test. The approved Pod writes a test file and unauthorized consumers remain restricted. After PVC deletion, the retained PV and backend volume still exist for approved recovery. ExplanationCorrect Answer B:The selected topology and access mode permit the intended writer pattern under a controlled test. This validates the stated intervention—choose an access mode and storage backend compatible with the intended attach and sharing semantics.—rather than an unrelated cluster change. The relevant mechanism is: ReadWriteOnce restricts volume mounting to one node, not globally one Pod; multi-node sharing needs backend support.Incorrect Answers A:Kubernetes access modes express requested attachment semantics but cannot add capability to a backend. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The selected topology and access mode permit the intended writer pattern under a controlled test. C:Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The selected topology and access mode permit the intended writer pattern under a controlled test. D:Reclaim policy determines what happens to backend storage after a bound claim is released. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The selected topology and access mode permit the intended writer pattern under a controlled test.
Question 81A team adds an HPA to a Deployment whose Pods lack CPU requests, producing unknown CPU utilization. Following the proposed change—Set defensible CPU requests and confirm metrics-server data before relying on percentage-based HPA—which observation best demonstrates that the particular fault is resolved? The HPA reports observed utilization and increases replicas during a controlled load. Controlled queue growth drives replica changes even when CPU remains low. Replicas decrease after the approved stabilization interval without oscillating under test load. The HPA stops reporting unknown metrics and scales within configured bounds. ExplanationCorrect Answer D:The HPA stops reporting unknown metrics and scales within configured bounds. This validates the stated intervention—set defensible CPU requests and confirm metrics-server data before relying on percentage-based HPA.—rather than an unrelated cluster change. The relevant mechanism is: CPU percentage targets use utilization relative to requested CPU, not just absolute node usage.Incorrect Answers A: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: The HPA stops reporting unknown metrics and scales within configured bounds. B:Different workload bottlenecks require appropriately supported HPA metrics. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The HPA stops reporting unknown metrics and scales within configured bounds. C:HPA may delay downscaling to avoid flapping even after metrics fall. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The HPA stops reporting unknown metrics and scales within configured bounds.
Question 82A security review finds a wildcard RBAC rule allowing all verbs on all API groups for a log collector. An engineer recommends: Replace wildcard rules with explicit get list watch permissions on the exact resources the collector reads. Which Kubernetes behavior best explains why this correction fits? Authentication establishes identity while authorization separately decides permitted API verbs and resources. Kubernetes service accounts do not automatically inherit administrator permissions from the Pod owner. RBAC treats interactive Pod subresources separately from operations on the parent Pod resource. Least-privilege RBAC narrows blast radius by limiting the allowed verbs, resources, and API groups. ExplanationCorrect Answer D:Least-privilege RBAC narrows blast radius by limiting the allowed verbs, resources, and API groups. This explains why the proposed action—replace wildcard rules with explicit get list watch permissions on the exact resources the collector reads.—is appropriate. Direct confirmation is: kubectl auth can-i checks show read-only access on log inputs and denial of workload modification.Incorrect Answers A:Authentication establishes identity while authorization separately decides permitted API verbs and resources. This does not establish the proposed intervention. The governing principle here is: Least-privilege RBAC narrows blast radius by limiting the allowed verbs, resources, and API groups. Apply it by: Replace wildcard rules with explicit get list watch permissions on the exact resources the collector reads. B:Kubernetes service accounts do not automatically inherit administrator permissions from the Pod owner. This does not establish the proposed intervention. The governing principle here is: Least-privilege RBAC narrows blast radius by limiting the allowed verbs, resources, and API groups. Apply it by: Replace wildcard rules with explicit get list watch permissions on the exact resources the collector reads. C:RBAC treats interactive Pod subresources separately from operations on the parent Pod resource. This does not establish the proposed intervention. The governing principle here is: Least-privilege RBAC narrows blast radius by limiting the allowed verbs, resources, and API groups. Apply it by: Replace wildcard rules with explicit get list watch permissions on the exact resources the collector reads.
Question 83A node reports DiskPressure and new Pods cannot be admitted although CPU and memory are available. Following the proposed change—Identify and clean safe image or container filesystem usage and expand capacity if needed—which observation best demonstrates that the particular fault is resolved? Node DiskPressure clears and new Pods are admitted without deleting active volume data. Process counts fall and the node condition clears while essential services remain alive. The workload completes under tested memory bounds and node pressure clears. A permitted workload schedules after the taint policy is corrected without relaxing other nodes. ExplanationCorrect Answer A:Node DiskPressure clears and new Pods are admitted without deleting active volume data. This validates the stated intervention—identify and clean safe image or container filesystem usage and expand capacity if needed.—rather than an unrelated cluster change. The relevant mechanism is: Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization.Incorrect Answers B:Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Node DiskPressure clears and new Pods are admitted without deleting active volume data. C:The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Node DiskPressure clears and new Pods are admitted without deleting active volume data. D:Scheduler taints are placement constraints distinct from raw allocatable capacity. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Node DiskPressure clears and new Pods are admitted without deleting active volume data.
Question 84A stateful Pod requests a PVC from a StorageClass using a CSI driver that is healthy on control-plane nodes but not on workers. Which Kubernetes administration action most directly addresses the observed failure? Select a StorageClass with an installed valid provisioner or install the required CSI driver. Define the correct CSI StorageClass parameters and verify the provisioned volume security properties. Use WaitForFirstConsumer binding for topology-constrained storage where supported. Install and verify the CSI node plugin on every eligible attachment node. ExplanationCorrect Answer D:Install and verify the CSI node plugin on every eligible attachment node. This corrects the specific failure because a controller may provision a volume while the node-side CSI plugin is still required to mount it. Verify it by checking: The PVC is Bound and a consumer on each eligible worker mounts and reads the volume.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: Install and verify the CSI node plugin on every eligible attachment node. The governing reason is: A controller may provision a volume while the node-side CSI plugin is still required to mount it. B:StorageClass parameters are driver-specific and determine backend provisioning behavior. That is relevant to a different intervention. For the stated situation, the required action is: Install and verify the CSI node plugin on every eligible attachment node. The governing reason is: A controller may provision a volume while the node-side CSI plugin is still required to mount it. 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: Install and verify the CSI node plugin on every eligible attachment node. The governing reason is: A controller may provision a volume while the node-side CSI plugin is still required to mount it.
Question 85A team creates a NetworkPolicy resource but its chosen CNI has no policy enforcement feature enabled. An engineer recommends: Deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement. Which Kubernetes behavior best explains why this correction fits? Ingress and egress restrictions are evaluated independently and policy effects compose additively. Kubernetes accepts policy objects even when a CNI does not implement enforcement. NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. DNS name resolution is a separate network flow from the application connection. ExplanationCorrect Answer B:Kubernetes accepts policy objects even when a CNI does not implement enforcement. This explains why the proposed action—deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement.—is appropriate. Direct confirmation is: A disallowed Pod connection is denied on the network, not merely recorded as a policy object.Incorrect Answers A:Ingress and egress restrictions are evaluated independently and policy effects compose additively. This does not establish the proposed intervention. The governing principle here is: Kubernetes accepts policy objects even when a CNI does not implement enforcement. Apply it by: Deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement. C:NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. This does not establish the proposed intervention. The governing principle here is: Kubernetes accepts policy objects even when a CNI does not implement enforcement. Apply it by: Deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement. 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: Kubernetes accepts policy objects even when a CNI does not implement enforcement. Apply it by: Deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement.
Question 86A namespace applies a default-deny ingress NetworkPolicy and legitimate frontend-to-backend requests begin timing out. An engineer recommends: Add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port. Which Kubernetes behavior best explains why this correction fits? NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. An egress-isolated Pod needs an explicit permitted path to each required destination. Ingress and egress restrictions are evaluated independently and policy effects compose additively. ExplanationCorrect Answer A:NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. This explains why the proposed action—add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port.—is appropriate. Direct confirmation is: Approved frontend traffic succeeds while an unrelated test Pod remains denied.Incorrect Answers B:A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. This does not establish the proposed intervention. The governing principle here is: NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. Apply it by: Add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port. C:An egress-isolated Pod needs an explicit permitted path to each required destination. This does not establish the proposed intervention. The governing principle here is: NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. Apply it by: Add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port. D:Ingress and egress restrictions are evaluated independently and policy effects compose additively. This does not establish the proposed intervention. The governing principle here is: NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. Apply it by: Add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port.
Question 87Pods show scheduling failures after a node label was removed during inventory synchronization. What is the most direct consequence if the underlying problem is left unresolved? A reachable API server cannot schedule useful workloads to a runtime-broken node. An administrative labeling error can strand healthy workloads. Capacity may sit unused while Pods remain Pending. Pod evictions and admission failures may continue despite idle CPU. ExplanationCorrect Answer B:An administrative labeling error can strand healthy workloads. This directly follows from the failed condition. The preventive correction is: Restore the intended stable node label or update hard node affinity after verifying policy. The governing Kubernetes behavior is: Hard placement rules require actual matching node labels at scheduling time.Incorrect Answers A:The kubelet must connect to the correct container runtime interface to manage Pod sandboxes. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An administrative labeling error can strand healthy workloads. C:Scheduler taints are placement constraints distinct from raw allocatable capacity. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An administrative labeling error can strand healthy workloads. 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: An administrative labeling error can strand healthy workloads.
Question 88Pods show scheduling failures after a node label was removed during inventory synchronization. Which Kubernetes administration action most directly addresses the observed failure? Update the kubelet CRI endpoint configuration to the installed runtime's actual socket. Restore the intended stable node label or update hard node affinity after verifying policy. 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 B:Restore the intended stable node label or update hard node affinity after verifying policy. This corrects the specific failure because hard placement rules require actual matching node labels at scheduling time. Verify it by checking: The relevant Pods schedule onto approved labeled nodes and node inventory matches policy.Incorrect Answers A:The kubelet must connect to the correct container runtime interface to manage Pod sandboxes. That is relevant to a different intervention. For the stated situation, the required action is: Restore the intended stable node label or update hard node affinity after verifying policy. The governing reason is: Hard placement rules require actual matching node labels at scheduling time. 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: Restore the intended stable node label or update hard node affinity after verifying policy. The governing reason is: Hard placement rules require actual matching node labels at scheduling time. 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: Restore the intended stable node label or update hard node affinity after verifying policy. The governing reason is: Hard placement rules require actual matching node labels at scheduling time.
Question 89An on-premises cluster is planned with overlapping Pod and service address blocks in the organization's existing routed networks. Which Kubernetes administration action most directly addresses the observed failure? Open only documented kubeadm control-plane, etcd, and kubelet communication paths for the intended topology. Choose nonoverlapping Pod and Service CIDRs and validate them against physical and VPN routes before initialization. Validate the stable controlPlaneEndpoint name and its reachable load balancer before kubeadm initialization. Configure a compatible CRI runtime and its cgroup driver consistently with the kubelet. ExplanationCorrect Answer B:Choose nonoverlapping Pod and Service CIDRs and validate them against physical and VPN routes before initialization. This corrects the specific failure because conflicting cluster and external address spaces can misroute traffic even when the API server is healthy. Verify it by checking: A route review and trial Pod-to-Service connection show unique destination networks.Incorrect Answers A:Bootstrap and reconciliation require distinct network flows among the API server, etcd, and nodes. That is relevant to a different intervention. For the stated situation, the required action is: Choose nonoverlapping Pod and Service CIDRs and validate them against physical and VPN routes before initialization. The governing reason is: Conflicting cluster and external address spaces can misroute traffic even when the API server is healthy. C:Clients and join operations need a durable API endpoint independent of one control-plane host. That is relevant to a different intervention. For the stated situation, the required action is: Choose nonoverlapping Pod and Service CIDRs and validate them against physical and VPN routes before initialization. The governing reason is: Conflicting cluster and external address spaces can misroute traffic even when the API server is healthy. D:The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings. That is relevant to a different intervention. For the stated situation, the required action is: Choose nonoverlapping Pod and Service CIDRs and validate them against physical and VPN routes before initialization. The governing reason is: Conflicting cluster and external address spaces can misroute traffic even when the API server is healthy.
Question 90A Pod requests 8 GiB of memory but each suitable node has only 4 GiB allocatable. Following the proposed change—Resize requests or provide sufficient eligible nodes based on actual allocatable capacity—which observation best demonstrates that the particular fault is resolved? Events no longer report Insufficient memory and the Pod schedules after capacity is corrected. The Pod schedules onto a matching GPU node and a nonmatching node is excluded. A matching eligible Pod exists in the specified topology and the new Pod schedules. Only intended workloads land on dedicated nodes while unapproved Pods remain excluded. ExplanationCorrect Answer A:Events no longer report Insufficient memory and the Pod schedules after capacity is corrected. This validates the stated intervention—resize requests or provide sufficient eligible nodes based on actual allocatable capacity.—rather than an unrelated cluster change. The relevant mechanism is: The scheduler evaluates Pod requests against node allocatable resources, not observed averages alone.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: Events no longer report Insufficient memory and the Pod schedules after capacity is corrected. C: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: Events no longer report Insufficient memory and the Pod schedules after capacity is corrected. D:Tolerations permit scheduling onto tainted nodes but do not by themselves select those nodes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Events no longer report Insufficient memory and the Pod schedules after capacity is corrected.