Question 30A Gateway is deployed but the namespace's HTTPRoute has no permission to attach across namespace boundaries. An engineer recommends: Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions. Which Kubernetes behavior best explains why this correction fits? Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references. Gateway API constrains route attachment and cross-namespace references through explicit policies. Gateway API resources require an implementing controller to provision and program data-plane listeners. Gateway API backend weights influence proportional HTTPRoute forwarding among valid backends. ExplanationCorrect Answer B:Gateway API constrains route attachment and cross-namespace references through explicit policies. This explains why the proposed action—configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions.—is appropriate. Direct confirmation is: The intended route becomes Accepted only from an approved namespace.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 constrains route attachment and cross-namespace references through explicit policies. Apply it by: Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions. C:Gateway API resources require an implementing controller to provision and program data-plane listeners. This does not establish the proposed intervention. The governing principle here is: Gateway API constrains route attachment and cross-namespace references through explicit policies. Apply it by: Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions. D:Gateway API backend weights influence proportional HTTPRoute forwarding among valid backends. This does not establish the proposed intervention. The governing principle here is: Gateway API constrains route attachment and cross-namespace references through explicit policies. Apply it by: Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions.
Question 31A cluster admin enables NodeLocal DNSCache but leaves pods pointing to an inaccessible DNS address. An engineer recommends: Align the node-local cache listen IP and Pod resolver configuration with the deployed cache topology. Which Kubernetes behavior best explains why this correction fits? Node-local DNS caching still requires Pod resolvers to reach the chosen local listener. 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. Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. ExplanationCorrect Answer A:Node-local DNS caching still requires Pod resolvers to reach the chosen local listener. This explains why the proposed action—align the node-local cache listen IP and Pod resolver configuration with the deployed cache topology.—is appropriate. Direct confirmation is: Queries on affected nodes reach the cache and fall back to upstream CoreDNS appropriately.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: Node-local DNS caching still requires Pod resolvers to reach the chosen local listener. Apply it by: Align the node-local cache listen IP and Pod resolver configuration with the deployed cache topology. 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: Node-local DNS caching still requires Pod resolvers to reach the chosen local listener. Apply it by: Align the node-local cache listen IP and Pod resolver configuration with the deployed cache topology. D:Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. This does not establish the proposed intervention. The governing principle here is: Node-local DNS caching still requires Pod resolvers to reach the chosen local listener. Apply it by: Align the node-local cache listen IP and Pod resolver configuration with the deployed cache topology.
Question 32A memory alert reports high node utilization while the application Pod's working set remains stable and disk cache grows. An engineer recommends: Correlate node memory metrics with Pod usage, cache and eviction conditions before resizing the app. Which Kubernetes behavior best explains why this correction fits? OOMKilled is evidence of memory-limit or node memory pressure, not an ordinary successful exit. Node-wide utilization can hide a throttled or memory-constrained application container. kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. ExplanationCorrect Answer D:Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. This explains why the proposed action—correlate node memory metrics with Pod usage, cache and eviction conditions before resizing the app.—is appropriate. Direct confirmation is: Per-Pod and node metrics identify the actual source of growth and targeted action resolves pressure.Incorrect Answers A:OOMKilled is evidence of memory-limit or node memory pressure, not an ordinary successful exit. This does not establish the proposed intervention. The governing principle here is: Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. Apply it by: Correlate node memory metrics with Pod usage, cache and eviction conditions before resizing the app. B:Node-wide utilization can hide a throttled or memory-constrained application container. This does not establish the proposed intervention. The governing principle here is: Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. Apply it by: Correlate node memory metrics with Pod usage, cache and eviction conditions before resizing the app. C:kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. This does not establish the proposed intervention. The governing principle here is: Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. Apply it by: Correlate node memory metrics with Pod usage, cache and eviction conditions before resizing the app.
Question 33External traffic reaches a NodePort on one node but not others after a kube-proxy upgrade. What is the most direct consequence if the underlying problem is left unresolved? Application integrations can fail despite healthy in-cluster routing. Valid backend Pods may be hidden behind incorrect ingress rules. Incident scope can remain node-specific despite healthy central CoreDNS. Traffic can become node-dependent and intermittent. ExplanationCorrect Answer D:Traffic can become node-dependent and intermittent. This directly follows from the failed condition. The preventive correction is: Inspect service proxy health, node firewall paths and the installed cluster dataplane implementation. The governing Kubernetes behavior is: Service reachability depends on node packet-forwarding rules and network acceptance at entry nodes.Incorrect Answers A:Egress isolation may deny flows independently of Service discovery and Pod health. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Traffic can become node-dependent and intermittent. B:Ingress routing adds a separate HTTP match layer beyond normal Service reachability. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Traffic can become node-dependent and intermittent. C:Per-node DNS cache configuration can produce node-specific resolution failures. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Traffic can become node-dependent and intermittent.
Question 34The API server is running but writes fail after etcd loses quorum during maintenance. Following the proposed change—Inspect etcd membership and quorum health, then restore sufficient approved voting members—which observation best demonstrates that the particular fault is resolved? The membership list includes the new peer and quorum health remains good after failure testing. Members form a healthy quorum and expected Kubernetes objects are visible before traffic is restored. etcd endpoint health and a safe API create or update operation both succeed. The API server static Pod starts and authenticated kubectl requests succeed. ExplanationCorrect Answer C:etcd endpoint health and a safe API create or update operation both succeed. This validates the stated intervention—inspect etcd membership and quorum health, then restore sufficient approved voting members.—rather than an unrelated cluster change. The relevant mechanism is: Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage.Incorrect Answers A:A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: etcd endpoint health and a safe API create or update operation both succeed. B:Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: etcd endpoint health and a safe API create or update operation both succeed. D: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: etcd endpoint health and a safe API create or update operation both succeed.
Question 35A workload on a small node suffers severe CPU throttling despite reported CPU usage below node capacity. An engineer recommends: Compare configured CPU limits and container throttling metrics before changing node size. Which Kubernetes behavior best explains why this correction fits? Node-wide utilization can hide a throttled or memory-constrained application container. Scheduling uses resource requests and constraints, not recent utilization percentages alone. Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. CPU limits may cause throttling independent of overall node idle time. ExplanationCorrect Answer D:CPU limits may cause throttling independent of overall node idle time. This explains why the proposed action—compare configured CPU limits and container throttling metrics before changing node size.—is appropriate. Direct confirmation is: Throttle counters decline and application latency improves after a justified limit adjustment.Incorrect Answers A:Node-wide utilization can hide a throttled or memory-constrained application container. This does not establish the proposed intervention. The governing principle here is: CPU limits may cause throttling independent of overall node idle time. Apply it by: Compare configured CPU limits and container throttling metrics before changing node size. B:Scheduling uses resource requests and constraints, not recent utilization percentages alone. This does not establish the proposed intervention. The governing principle here is: CPU limits may cause throttling independent of overall node idle time. Apply it by: Compare configured CPU limits and container throttling metrics before changing node size. C:Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. This does not establish the proposed intervention. The governing principle here is: CPU limits may cause throttling independent of overall node idle time. Apply it by: Compare configured CPU limits and container throttling metrics before changing node size.
Question 36A node is overrun by image garbage collection activity during every deployment wave. Which Kubernetes administration action most directly addresses the observed failure? Compare configured CPU limits and container throttling metrics before changing node size. Correlate node memory metrics with Pod usage, cache and eviction conditions before resizing the app. Inspect image filesystem consumption and kubelet garbage collection thresholds before changing policies. Inspect Pod-level CPU and memory use and component metrics with kubectl top and relevant monitoring. ExplanationCorrect Answer C:Inspect image filesystem consumption and kubelet garbage collection thresholds before changing policies. This corrects the specific failure because image storage pressure and image garbage collection are distinct from application CPU demand. Verify it by checking: Image filesystem usage stabilizes and Pod starts remain timely during controlled releases.Incorrect Answers A:CPU limits may cause throttling independent of overall node idle time. That is relevant to a different intervention. For the stated situation, the required action is: Inspect image filesystem consumption and kubelet garbage collection thresholds before changing policies. The governing reason is: Image storage pressure and image garbage collection are distinct from application CPU demand. B:Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. That is relevant to a different intervention. For the stated situation, the required action is: Inspect image filesystem consumption and kubelet garbage collection thresholds before changing policies. The governing reason is: Image storage pressure and image garbage collection are distinct from application CPU demand. D:Node-wide utilization can hide a throttled or memory-constrained application container. That is relevant to a different intervention. For the stated situation, the required action is: Inspect image filesystem consumption and kubelet garbage collection thresholds before changing policies. The governing reason is: Image storage pressure and image garbage collection are distinct from application CPU demand.
Question 37A development team asks for expanding a live filesystem PVC but its StorageClass disables allowVolumeExpansion. Following the proposed change—Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow—which observation best demonstrates that the particular fault is resolved? A test PVC becomes Bound and the expected CSI volume is created. The PVC is Bound and a consumer on each eligible worker mounts and reads the volume. A test PV is created with the required encryption setting reported by the storage provider. PVC capacity grows to the requested value and the filesystem reports additional usable space. ExplanationCorrect Answer D:PVC capacity grows to the requested value and the filesystem reports additional usable space. This validates the stated intervention—use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow.—rather than an unrelated cluster change. The relevant mechanism is: PVC size expansion depends on both StorageClass permission and storage-driver capabilities.Incorrect Answers A:Dynamic provisioning depends on a controller that recognizes the StorageClass provisioner identifier. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: PVC capacity grows to the requested value and the filesystem reports additional usable space. B:A controller may provision a volume while the node-side CSI plugin is still required to mount it. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: PVC capacity grows to the requested value and the filesystem reports additional usable space. C:StorageClass parameters are driver-specific and determine backend provisioning behavior. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: PVC capacity grows to the requested value and the filesystem reports additional usable space.
Question 38A webhook service's certificate expires and API object creation fails with an admission webhook TLS error. An engineer recommends: Renew the webhook serving certificate and align its caBundle and Service reference. Which Kubernetes behavior best explains why this correction fits? DNS resolution and a Service object do not guarantee a valid ready backend endpoint. Egress isolation may deny flows independently of Service discovery and Pod health. API admission webhooks require trusted TLS service connectivity during object admission. Services generally route only to endpoints considered ready, so Pod IP probes do not establish Service capacity. ExplanationCorrect Answer C:API admission webhooks require trusted TLS service connectivity during object admission. This explains why the proposed action—renew the webhook serving certificate and align its caBundle and Service reference.—is appropriate. Direct confirmation is: A safe object admission test passes with verified webhook TLS and expected policy behavior.Incorrect Answers A:DNS resolution and a Service object do not guarantee a valid ready backend endpoint. This does not establish the proposed intervention. The governing principle here is: API admission webhooks require trusted TLS service connectivity during object admission. Apply it by: Renew the webhook serving certificate and align its caBundle and Service reference. B:Egress isolation may deny flows independently of Service discovery and Pod health. This does not establish the proposed intervention. The governing principle here is: API admission webhooks require trusted TLS service connectivity during object admission. Apply it by: Renew the webhook serving certificate and align its caBundle and Service reference. D:Services generally route only to endpoints considered ready, so Pod IP probes do not establish Service capacity. This does not establish the proposed intervention. The governing principle here is: API admission webhooks require trusted TLS service connectivity during object admission. Apply it by: Renew the webhook serving certificate and align its caBundle and Service reference.
Question 39After restoring an etcd snapshot, an engineer starts two inconsistent members with mismatched cluster identifiers. An engineer recommends: Follow the supported etcd snapshot restore topology and consistent member configuration. Which Kubernetes behavior best explains why this correction fits? A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. Control-plane components need functional credentials and narrowly appropriate permissions to reconcile state. ExplanationCorrect Answer C:Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. This explains why the proposed action—follow the supported etcd snapshot restore topology and consistent member configuration.—is appropriate. Direct confirmation is: Members form a healthy quorum and expected Kubernetes objects are visible before traffic is restored.Incorrect Answers A:A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. This does not establish the proposed intervention. The governing principle here is: Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. Apply it by: Follow the supported etcd snapshot restore topology and consistent member configuration. 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: Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. Apply it by: Follow the supported etcd snapshot restore topology and consistent member configuration. D: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: Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. Apply it by: Follow the supported etcd snapshot restore topology and consistent member configuration.
Question 40A database password was placed in a ConfigMap visible to every application reader in the namespace. What is the most direct consequence if the underlying problem is left unresolved? Credentials can leak through broad configuration access. Pods can remain stuck on configuration errors despite valid image pulls. The workload may continue authenticating with revoked credentials. A stale configuration file may persist after a successful API change. ExplanationCorrect Answer A:Credentials can leak through broad configuration access. This directly follows from the failed condition. The preventive correction is: Move credentials to a Secret and restrict API access and storage handling appropriately. The governing Kubernetes behavior is: Secrets are intended for sensitive values but still require RBAC and protection at rest and in use.Incorrect Answers B:Secret key references are exact and missing mandatory keys prevent valid container configuration. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Credentials can leak through broad configuration access. C:Environment variables sourced from Secrets are fixed for the lifetime of a container process. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Credentials can leak through broad configuration access. D:ConfigMap volumes can update eventually, whereas a subPath-mounted key does not receive automatic updates. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Credentials can leak through broad configuration access.