Question 170A NodePort Service is accessible through worker addresses but an operator expects it to create a cloud load balancer automatically. Which Kubernetes administration action most directly addresses the observed failure? Return to ClusterIP and remove the unnecessary external frontend. Create and maintain appropriate EndpointSlice resources with correct labels and target addresses. Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required. Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing. ExplanationCorrect Answer C:Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required. This corrects the specific failure because nodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. Verify it by checking: The Service receives the expected load balancer ingress and end-to-end external probes succeed.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: Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required. The governing reason is: NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. B:Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. That is relevant to a different intervention. For the stated situation, the required action is: Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required. The governing reason is: NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. D:A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. That is relevant to a different intervention. For the stated situation, the required action is: Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required. The governing reason is: NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning.
Question 171An internal app needs to reach a Pod using its own namespace-local DNS alias, but the client uses a stale Pod hostname. What is the most direct consequence if the underlying problem is left unresolved? A valid local name can silently route requests to the wrong application. Clients may repeatedly contact stale or nonexistent endpoints. Direct Pod addressing can fail on ordinary rollout or eviction. Inter-node service calls can fail while same-node health checks pass. ExplanationCorrect Answer B:Clients may repeatedly contact stale or nonexistent endpoints. This directly follows from the failed condition. The preventive correction is: Use the intended Service name with namespace-aware DNS resolution and test reachability. The governing Kubernetes behavior is: Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement.Incorrect Answers A:Unqualified DNS lookups are affected by search domains in the caller's namespace. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Clients may repeatedly contact stale or nonexistent endpoints. C:Pods are replaceable and their IP addresses can change even when the application identity remains. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Clients may repeatedly contact stale or nonexistent endpoints. D:Kubernetes expects Pod-to-Pod reachability without application-managed NAT across nodes. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Clients may repeatedly contact stale or nonexistent endpoints.
Question 172A NodePort Service is accessible through worker addresses but an operator expects it to create a cloud load balancer automatically. What is the most direct consequence if the underlying problem is left unresolved? An unnecessary public endpoint can expose a sensitive internal database. A Service can exist with no routable destination at all. External clients may remain without a stable supported entry point. Clients relying on VIP semantics can fail or choose the wrong replica. ExplanationCorrect Answer C:External clients may remain without a stable supported entry point. This directly follows from the failed condition. The preventive correction is: Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required. The governing Kubernetes behavior is: NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning.Incorrect Answers A: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: External clients may remain without a stable supported entry point. B:Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: External clients may remain without a stable supported entry point. D:A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: External clients may remain without a stable supported entry point.
Question 173A team uses kubectl logs against a Pending Pod and assumes no log output proves the image is healthy. What is the most direct consequence if the underlying problem is left unresolved? The first crash cause may be lost behind successful restart messages. Image or scheduling failures can be mistaken for silent application crashes. Failures can go undetected because the standard logging path is silent. Large unscoped logs can bury the critical event and waste incident time. ExplanationCorrect Answer B:Image or scheduling failures can be mistaken for silent application crashes. This directly follows from the failed condition. The preventive correction is: Inspect Pod events and waiting reasons before expecting a container log stream. The governing Kubernetes behavior is: Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis.Incorrect Answers A:Restarted containers can have a previous log stream that is distinct from the current one. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Image or scheduling failures can be mistaken for silent application crashes. C:kubectl logs primarily reads the container runtime's captured stdout and stderr streams. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Image or scheduling failures can be mistaken for silent application crashes. D:kubectl log filters help isolate relevant events and reduce diagnostic noise. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Image or scheduling failures can be mistaken for silent application crashes.
Question 174An application has no resource limits and one request can exhaust memory on the node. What is the most direct consequence if the underlying problem is left unresolved? Traffic may reach an uninitialized instance and fail transiently. A single Pod may destabilize other workloads sharing the node. New workers may operate without required host-level observability. Repeated premature restarts can prevent the service from ever becoming ready. ExplanationCorrect Answer B:A single Pod may destabilize other workloads sharing the node. This directly follows from the failed condition. The preventive correction is: Assign realistic resource requests and memory limits, then load-test under expected peaks. The governing Kubernetes behavior is: Requests guide scheduling while limits constrain runtime resource consumption.Incorrect Answers A:A failed readiness probe removes Pod endpoints from Services without necessarily restarting the container. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A single Pod may destabilize other workloads sharing the node. C:DaemonSets ensure eligible nodes run a copy of the node-level workload. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A single Pod may destabilize other workloads sharing the node. D: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: A single Pod may destabilize other workloads sharing the node.
Question 175The API server advertises an obsolete host IP after an infrastructure migration and workers fail to reconnect. Following the proposed change—Correct the supported advertise-address and stable endpoint configuration with matching certificates—which observation best demonstrates that the particular fault is resolved? Worker kubelet connections and administrator requests succeed using current endpoints. The API server static Pod starts and authenticated kubectl requests succeed. The membership list includes the new peer and quorum health remains good after failure testing. The specific controller resumes writes and unauthorized privileges remain denied. ExplanationCorrect Answer A:Worker kubelet connections and administrator requests succeed using current endpoints. This validates the stated intervention—correct the supported advertise-address and stable endpoint configuration with matching certificates.—rather than an unrelated cluster change. The relevant mechanism is: Control-plane advertised addresses must be reachable through the cluster's intended topology.Incorrect Answers B: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: Worker kubelet connections and administrator requests succeed using current endpoints. C: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: Worker kubelet connections and administrator requests succeed using current endpoints. D:Control-plane components need functional credentials and narrowly appropriate permissions to reconcile state. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Worker kubelet connections and administrator requests succeed using current endpoints.
Question 176An Ingress object is present but no controller is installed and the Service remains unreachable from outside. Following the proposed change—Install and select a supported Ingress controller, then test its address and routing status—which observation best demonstrates that the particular fault is resolved? Controller events clear missing-Service errors and the hostname reaches the new backend. The controller reconciles the Ingress and an external host/path probe reaches the Service. Explicit /checkout and / paths each route to the intended backend under integration tests. The HTTPS listener presents the intended certificate for the host and forwards to the backend. ExplanationCorrect Answer B:The controller reconciles the Ingress and an external host/path probe reaches the Service. This validates the stated intervention—install and select a supported Ingress controller, then test its address and routing status.—rather than an unrelated cluster change. The relevant mechanism is: Ingress API objects do not themselves implement HTTP routing; a controller supplies the dataplane.Incorrect Answers A:Ingress rules point to Services by name and port within their namespace. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The controller reconciles the Ingress and an external host/path probe reaches the Service. C:HTTP path matching and precedence affect which Service receives a request. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The controller reconciles the Ingress and an external host/path probe reaches the Service. D:Ingress TLS termination depends on a usable referenced Secret and an active controller. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The controller reconciles the Ingress and an external host/path probe reaches the Service.
Question 177An API team assumes a Pod's IP remains stable across rescheduling and hardcodes it into client configuration. What is the most direct consequence if the underlying problem is left unresolved? Clients may repeatedly contact stale or nonexistent endpoints. Direct Pod addressing can fail on ordinary rollout or eviction. Some clients can fail even when the Service appears reachable by another family. Inter-node service calls can fail while same-node health checks pass. ExplanationCorrect Answer B:Direct Pod addressing can fail on ordinary rollout or eviction. This directly follows from the failed condition. The preventive correction is: Use a Service DNS name or other stable discovery mechanism instead of a Pod IP. The governing Kubernetes behavior is: Pods are replaceable and their IP addresses can change even when the application identity remains.Incorrect Answers A:Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Direct Pod addressing can fail on ordinary rollout or eviction. C:Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Direct Pod addressing can fail on ordinary rollout or eviction. D:Kubernetes expects Pod-to-Pod reachability without application-managed NAT across nodes. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Direct Pod addressing can fail on ordinary rollout or eviction.
Question 178A legacy Pod tries to contact a service outside its namespace using only a short name and accidentally reaches a local Service. Following the proposed change—Use the fully qualified service name or an explicitly namespace-qualified DNS reference—which observation best demonstrates that the particular fault is resolved? DNS resolution returns the intended namespace's Service IP and the target responds. The client resolves the current Service record and reaches a ready backend. Clients continue connecting after the target Pod is deleted and replaced. A test client connects over each supported IP family to healthy backends. ExplanationCorrect Answer A:DNS resolution returns the intended namespace's Service IP and the target responds. This validates the stated intervention—use the fully qualified service name or an explicitly namespace-qualified DNS reference.—rather than an unrelated cluster change. The relevant mechanism is: Unqualified DNS lookups are affected by search domains in the caller's namespace.Incorrect Answers B:Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: DNS resolution returns the intended namespace's Service IP and the target responds. C:Pods are replaceable and their IP addresses can change even when the application identity remains. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: DNS resolution returns the intended namespace's Service IP and the target responds. D:Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: DNS resolution returns the intended namespace's Service IP and the target responds.
Question 179A Service sends requests to a Pod that reports Running but fails readiness checks. An engineer recommends: Make the Pod's readiness probe meaningful and confirm only ready endpoints receive traffic. Which Kubernetes behavior best explains why this correction fits? Selector-backed Services route through EndpointSlices populated from matching eligible Pods. ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported. Readiness controls endpoint eligibility; Pod phase Running alone does not guarantee serving capacity. A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. ExplanationCorrect Answer C:Readiness controls endpoint eligibility; Pod phase Running alone does not guarantee serving capacity. This explains why the proposed action—make the Pod's readiness probe meaningful and confirm only ready endpoints receive traffic.—is appropriate. Direct confirmation is: EndpointSlices exclude the unready Pod and traffic flows only to healthy replicas.Incorrect Answers A:Selector-backed Services route through EndpointSlices populated from matching eligible Pods. This does not establish the proposed intervention. The governing principle here is: Readiness controls endpoint eligibility; Pod phase Running alone does not guarantee serving capacity. Apply it by: Make the Pod's readiness probe meaningful and confirm only ready endpoints receive traffic. B: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: Readiness controls endpoint eligibility; Pod phase Running alone does not guarantee serving capacity. Apply it by: Make the Pod's readiness probe meaningful and confirm only ready endpoints receive traffic. D:A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. This does not establish the proposed intervention. The governing principle here is: Readiness controls endpoint eligibility; Pod phase Running alone does not guarantee serving capacity. Apply it by: Make the Pod's readiness probe meaningful and confirm only ready endpoints receive traffic.
Question 180A new HA control-plane node receives a certificate that omits the load-balanced API hostname from its SANs. What is the most direct consequence if the underlying problem is left unresolved? Certificate name mismatch can block administrative and node API access. A single failed VM can halt changes and prevent the control plane from reconciling. Clients may receive repeated failed API requests despite healthy peer servers. An infrastructure failure can remove multiple quorum voters at once. ExplanationCorrect Answer A:Certificate name mismatch can block administrative and node API access. This directly follows from the failed condition. The preventive correction is: Issue certificates that include the approved stable API endpoint and node identities. The governing Kubernetes behavior is: TLS clients verify the endpoint hostname against the presented certificate SANs.Incorrect Answers B:Highly available control planes depend on load-balanced API access and durable quorum-backed state. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Certificate name mismatch can block administrative and node API access. C:A successful TCP handshake does not prove a particular API server is ready to serve requests. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Certificate name mismatch can block administrative and node API access. D:Quorum and replication do not protect against a common power or hypervisor failure domain. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Certificate name mismatch can block administrative and node API access.