Question 290An etcd member is removed after a disk failure, but nobody checks whether the remaining members have quorum. An engineer recommends: Inspect etcd endpoint status and membership before modifying the cluster's voter set. Which Kubernetes behavior best explains why this correction fits? Quorum and replication do not protect against a common power or hypervisor failure domain. Highly available control planes depend on load-balanced API access and durable quorum-backed state. Etcd commits require a majority of voting members; removal and replacement must preserve quorum. A successful TCP handshake does not prove a particular API server is ready to serve requests. ExplanationCorrect Answer C:Etcd commits require a majority of voting members; removal and replacement must preserve quorum. This explains why the proposed action—inspect etcd endpoint status and membership before modifying the cluster's voter set.—is appropriate. Direct confirmation is: The member list and endpoint health show an operational majority before and after the change.Incorrect Answers A:Quorum and replication do not protect against a common power or hypervisor failure domain. This does not establish the proposed intervention. The governing principle here is: Etcd commits require a majority of voting members; removal and replacement must preserve quorum. Apply it by: Inspect etcd endpoint status and membership before modifying the cluster's voter set. B:Highly available control planes depend on load-balanced API access and durable quorum-backed state. This does not establish the proposed intervention. The governing principle here is: Etcd commits require a majority of voting members; removal and replacement must preserve quorum. Apply it by: Inspect etcd endpoint status and membership before modifying the cluster's voter set. D:A successful TCP handshake does not prove a particular API server is ready to serve requests. This does not establish the proposed intervention. The governing principle here is: Etcd commits require a majority of voting members; removal and replacement must preserve quorum. Apply it by: Inspect etcd endpoint status and membership before modifying the cluster's voter set.
Question 291A headless Service was created for a StatefulSet but clients still expect one virtual ClusterIP. Which Kubernetes administration action most directly addresses the observed failure? Return to ClusterIP and remove the unnecessary external frontend. Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required. Set the Service targetPort to the actual listener port or correctly named container port. Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing. ExplanationCorrect Answer D:Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing. This corrects the specific failure because a headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. Verify it by checking: 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. That is relevant to a different intervention. For the stated situation, the required action is: Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing. The governing reason is: A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. B:NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. That is relevant to a different intervention. For the stated situation, the required action is: Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing. The governing reason is: A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. C:Service port and targetPort describe different ends of the virtual forwarding path. That is relevant to a different intervention. For the stated situation, the required action is: Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing. The governing reason is: A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target.
Question 292A legacy Pod tries to contact a service outside its namespace using only a short name and accidentally reaches a local Service. Which Kubernetes administration action most directly addresses the observed failure? Use the intended Service name with namespace-aware DNS resolution and test reachability. Use the fully qualified service name or an explicitly namespace-qualified DNS reference. Use a Service DNS name or other stable discovery mechanism instead of a Pod IP. Validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families. ExplanationCorrect Answer B:Use the fully qualified service name or an explicitly namespace-qualified DNS reference. This corrects the specific failure because unqualified DNS lookups are affected by search domains in the caller's namespace. Verify it by checking: DNS resolution returns the intended namespace's Service IP and the target responds.Incorrect Answers A:Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement. That is relevant to a different intervention. For the stated situation, the required action is: Use the fully qualified service name or an explicitly namespace-qualified DNS reference. The governing reason is: Unqualified DNS lookups are affected by search domains in the caller's namespace. C:Pods are replaceable and their IP addresses can change even when the application identity remains. That is relevant to a different intervention. For the stated situation, the required action is: Use the fully qualified service name or an explicitly namespace-qualified DNS reference. The governing reason is: Unqualified DNS lookups are affected by search domains in the caller's namespace. D:Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration. That is relevant to a different intervention. For the stated situation, the required action is: Use the fully qualified service name or an explicitly namespace-qualified DNS reference. The governing reason is: Unqualified DNS lookups are affected by search domains in the caller's namespace.
Question 293A namespace selector policy appears to permit Pods from every namespace because it uses an empty namespaceSelector. What is the most direct consequence if the underlying problem is left unresolved? Selector confusion can either block legitimate clients or allow unwanted access. A blanket allow would erase the intended namespace segmentation. Cross-namespace access can expand well beyond the intended trust boundary. Applications may appear network-isolated because they cannot resolve healthy destinations. ExplanationCorrect Answer C:Cross-namespace access can expand well beyond the intended trust boundary. This directly follows from the failed condition. The preventive correction is: Use a namespaceSelector matching an explicitly approved label and combine with podSelector when appropriate. The governing Kubernetes behavior is: An empty namespaceSelector matches all namespaces; namespace and Pod peers must be scoped deliberately.Incorrect Answers A:A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Cross-namespace access can expand well beyond the intended trust boundary. B:NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Cross-namespace access can expand well beyond the intended trust boundary. D:DNS name resolution is a separate network flow from the application connection. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Cross-namespace access can expand well beyond the intended trust boundary.
Question 294A production cluster relies on one control-plane VM and its failure would remove API access. An engineer recommends: Design and test multiple control-plane nodes behind a durable API endpoint with compatible etcd quorum. Which Kubernetes behavior best explains why this correction fits? Highly available control planes depend on load-balanced API access and durable quorum-backed state. Quorum and replication do not protect against a common power or hypervisor failure domain. TLS clients verify the endpoint hostname against the presented certificate SANs. Clients and join operations need a durable API endpoint independent of one control-plane host. ExplanationCorrect Answer A:Highly available control planes depend on load-balanced API access and durable quorum-backed state. This explains why the proposed action—design and test multiple control-plane nodes behind a durable API endpoint with compatible etcd quorum.—is appropriate. Direct confirmation is: A simulated single-control-plane outage retains API availability and healthy etcd quorum.Incorrect Answers B:Quorum and replication do not protect against a common power or hypervisor failure domain. This does not establish the proposed intervention. The governing principle here is: Highly available control planes depend on load-balanced API access and durable quorum-backed state. Apply it by: Design and test multiple control-plane nodes behind a durable API endpoint with compatible etcd quorum. C:TLS clients verify the endpoint hostname against the presented certificate SANs. This does not establish the proposed intervention. The governing principle here is: Highly available control planes depend on load-balanced API access and durable quorum-backed state. Apply it by: Design and test multiple control-plane nodes behind a durable API endpoint with compatible etcd quorum. D:Clients and join operations need a durable API endpoint independent of one control-plane host. This does not establish the proposed intervention. The governing principle here is: Highly available control planes depend on load-balanced API access and durable quorum-backed state. Apply it by: Design and test multiple control-plane nodes behind a durable API endpoint with compatible etcd quorum.
Question 295A policy intended to permit only Pods labeled app=web selects the backend itself rather than the source peers. Which Kubernetes administration action most directly addresses the observed failure? Use a namespaceSelector matching an explicitly approved label and combine with podSelector when appropriate. Add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port. Permit DNS traffic to the intended cluster DNS endpoints under the egress policy. Separate the policy podSelector target from ingress from.podSelector peer matching. ExplanationCorrect Answer D:Separate the policy podSelector target from ingress from.podSelector peer matching. This corrects the specific failure because a NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. Verify it by checking: Only the intended web client can connect to the protected backend.Incorrect Answers A:An empty namespaceSelector matches all namespaces; namespace and Pod peers must be scoped deliberately. That is relevant to a different intervention. For the stated situation, the required action is: Separate the policy podSelector target from ingress from.podSelector peer matching. The governing reason is: A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. B:NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. That is relevant to a different intervention. For the stated situation, the required action is: Separate the policy podSelector target from ingress from.podSelector peer matching. The governing reason is: A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. C:DNS name resolution is a separate network flow from the application connection. That is relevant to a different intervention. For the stated situation, the required action is: Separate the policy podSelector target from ingress from.podSelector peer matching. The governing reason is: A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources.
Question 296A Pod uses a required key named DB_USER but the referenced Secret only contains username, causing startup failure. What is the most direct consequence if the underlying problem is left unresolved? The workload may continue authenticating with revoked credentials. Credentials can leak through broad configuration access. Repeated premature restarts can prevent the service from ever becoming ready. Pods can remain stuck on configuration errors despite valid image pulls. ExplanationCorrect Answer D:Pods can remain stuck on configuration errors despite valid image pulls. This directly follows from the failed condition. The preventive correction is: Align the Secret key name and the Pod's secretKeyRef with the application contract. The governing Kubernetes behavior is: Secret key references are exact and missing mandatory keys prevent valid container configuration.Incorrect Answers A: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: Pods can remain stuck on configuration errors despite valid image pulls. B:Secrets are intended for sensitive values but still require RBAC and protection at rest and in use. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Pods can remain stuck on configuration errors despite valid image pulls. C:Startup probes suppress other probe evaluation until the startup check succeeds. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Pods can remain stuck on configuration errors despite valid image pulls.
Question 297The API server is running but writes fail after etcd loses quorum during maintenance. Which Kubernetes administration action most directly addresses the observed failure? Inspect etcd membership and quorum health, then restore sufficient approved voting members. Use supported etcd member verification and safely add or reconcile the intended member. Follow the supported etcd snapshot restore topology and consistent member configuration. Inspect the kubelet-managed static Pod manifest and its container logs, then repair invalid API server flags. ExplanationCorrect Answer A:Inspect etcd membership and quorum health, then restore sufficient approved voting members. This corrects the specific failure because etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. Verify it by checking: etcd endpoint health and a safe API create or update operation both succeed.Incorrect Answers B:A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. That is relevant to a different intervention. For the stated situation, the required action is: Inspect etcd membership and quorum health, then restore sufficient approved voting members. The governing reason is: Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. C:Restored etcd members must agree on cluster identity and membership rather than mix prior data directories. That is relevant to a different intervention. For the stated situation, the required action is: Inspect etcd membership and quorum health, then restore sufficient approved voting members. The governing reason is: Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. D: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 etcd membership and quorum health, then restore sufficient approved voting members. The governing reason is: Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage.
Question 298A Deployment embeds a database host string in its image and each environment requires a different build. Following the proposed change—Externalize the host into a ConfigMap and consume it through environment variables or a mounted configuration volume—which observation best demonstrates that the particular fault is resolved? New Pods use the updated Secret value and old processes terminate in a controlled rollout. A ConfigMap change appears in the projected file and the application reloads it as intended. 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. ExplanationCorrect Answer D:A new environment receives the intended host configuration without rebuilding the image. This validates the stated intervention—externalize the host into a ConfigMap and consume it through environment variables or a mounted configuration volume.—rather than an unrelated cluster change. The relevant mechanism is: ConfigMaps separate nonsecret configuration from the application container image.Incorrect Answers A:Environment variables sourced from Secrets are fixed for the lifetime of a container process. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A new environment receives the intended host configuration without rebuilding the image. B:ConfigMap volumes can update eventually, whereas a subPath-mounted key does not receive automatic updates. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A new environment receives the intended host configuration without rebuilding the image. C: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: A new environment receives the intended host configuration without rebuilding the image.
Question 299A database PVC is created using ReadWriteOnce and two Pods on different nodes both expect simultaneous independent writes. What is the most direct consequence if the underlying problem is left unresolved? Replicas may remain Pending or see inconsistent shared content. Application startup can fail with permission-denied errors despite a bound PVC. Concurrent multi-node mounts may fail or create consistency risks. Persistent application data can be unintentionally destroyed. ExplanationCorrect Answer C:Concurrent multi-node mounts may fail or create consistency risks. This directly follows from the failed condition. The preventive correction is: Choose an access mode and storage backend compatible with the intended attach and sharing semantics. The governing Kubernetes behavior 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. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Concurrent multi-node mounts may fail or create consistency risks. B:Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Concurrent multi-node mounts may fail or create consistency risks. D:Reclaim policy determines what happens to backend storage after a bound claim is released. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Concurrent multi-node mounts may fail or create consistency risks.
Question 300A Pod cannot land on one node even after resource capacity is added because the node has an unexpected NoSchedule taint. What is the most direct consequence if the underlying problem is left unresolved? Pod evictions and admission failures may continue despite idle CPU. An administrative labeling error can strand healthy workloads. Capacity may sit unused while Pods remain Pending. Repeated OOM kills can degrade both batch work and neighboring services. ExplanationCorrect Answer C:Capacity may sit unused while Pods remain Pending. This directly follows from the failed condition. The preventive correction is: Inspect taints and remove the unintended taint or use narrowly authorized tolerations. The governing Kubernetes behavior is: Scheduler taints are placement constraints distinct from raw allocatable capacity.Incorrect Answers A: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: Capacity may sit unused while Pods remain Pending. B:Hard placement rules require actual matching node labels at scheduling time. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Capacity may sit unused while Pods remain Pending. D:The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Capacity may sit unused while Pods remain Pending.