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.
Question 181A Deployment embeds a database host string in its image and each environment requires a different build. What is the most direct consequence if the underlying problem is left unresolved? The workload may continue authenticating with revoked credentials. A stale configuration file may persist after a successful API change. Pods can remain stuck on configuration errors despite valid image pulls. Hardcoded configuration creates drift across environments and unnecessary image rebuilds. ExplanationCorrect Answer D:Hardcoded configuration creates drift across environments and unnecessary image rebuilds. This directly follows from the failed condition. The preventive correction is: Externalize the host into a ConfigMap and consume it through environment variables or a mounted configuration volume. The governing Kubernetes behavior 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. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Hardcoded configuration creates drift across environments and unnecessary image rebuilds. B: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: Hardcoded configuration creates drift across environments and unnecessary image rebuilds. C: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: Hardcoded configuration creates drift across environments and unnecessary image rebuilds.
Question 182A Pod can resolve internal Services but outbound internet requests hang after a new default-deny egress policy. An engineer recommends: Inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS. Which Kubernetes behavior best explains why this correction fits? Both source egress and destination ingress policies can restrict a cross-namespace flow. Per-node DNS cache configuration can produce node-specific resolution failures. Service reachability depends on node packet-forwarding rules and network acceptance at entry nodes. Egress isolation may deny flows independently of Service discovery and Pod health. ExplanationCorrect Answer D:Egress isolation may deny flows independently of Service discovery and Pod health. This explains why the proposed action—inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS.—is appropriate. Direct confirmation is: Approved external probes succeed while prohibited destinations remain blocked.Incorrect Answers A:Both source egress and destination ingress policies can restrict a cross-namespace flow. This does not establish the proposed intervention. The governing principle here is: Egress isolation may deny flows independently of Service discovery and Pod health. Apply it by: Inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS. B:Per-node DNS cache configuration can produce node-specific resolution failures. This does not establish the proposed intervention. The governing principle here is: Egress isolation may deny flows independently of Service discovery and Pod health. Apply it by: Inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS. C:Service reachability depends on node packet-forwarding rules and network acceptance at entry nodes. This does not establish the proposed intervention. The governing principle here is: Egress isolation may deny flows independently of Service discovery and Pod health. Apply it by: Inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS.
Question 183A log-gathering command returns nothing because the responder queried an old namespace after a team migration. Which Kubernetes administration action most directly addresses the observed failure? Use time-scoped and bounded log retrieval with recorded Pod, container and timestamp context. Inspect Pod events and waiting reasons before expecting a container log stream. Retrieve the previous container instance logs and examine termination reason alongside current output. Resolve the actual namespace and label selector before requesting the current workload's logs. ExplanationCorrect Answer D:Resolve the actual namespace and label selector before requesting the current workload's logs. This corrects the specific failure because kubectl resource lookups are namespace-scoped unless explicitly configured otherwise. Verify it by checking: The queried Pods and log lines match the current deployment namespace and time window.Incorrect Answers A:kubectl log filters help isolate relevant events and reduce diagnostic noise. That is relevant to a different intervention. For the stated situation, the required action is: Resolve the actual namespace and label selector before requesting the current workload's logs. The governing reason is: kubectl resource lookups are namespace-scoped unless explicitly configured otherwise. B:Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis. That is relevant to a different intervention. For the stated situation, the required action is: Resolve the actual namespace and label selector before requesting the current workload's logs. The governing reason is: kubectl resource lookups are namespace-scoped unless explicitly configured otherwise. C:Restarted containers can have a previous log stream that is distinct from the current one. That is relevant to a different intervention. For the stated situation, the required action is: Resolve the actual namespace and label selector before requesting the current workload's logs. The governing reason is: kubectl resource lookups are namespace-scoped unless explicitly configured otherwise.
Question 184A shared media workload requires read/write access from Pods on many nodes but its storage backend supports only single-node access. Which Kubernetes administration action most directly addresses the observed failure? Use a ReadWriteMany-capable shared filesystem and a matching PV or StorageClass. Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access. Choose an access mode and storage backend compatible with the intended attach and sharing semantics. Use networked persistent storage or node-aware scheduling instead of assuming hostPath is portable. ExplanationCorrect Answer A:Use a ReadWriteMany-capable shared filesystem and a matching PV or StorageClass. This corrects the specific failure because kubernetes access modes express requested attachment semantics but cannot add capability to a backend. Verify it by checking: Pods on different workers simultaneously read and write a shared test file where supported.Incorrect Answers B:Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. That is relevant to a different intervention. For the stated situation, the required action is: Use a ReadWriteMany-capable shared filesystem and a matching PV or StorageClass. The governing reason is: Kubernetes access modes express requested attachment semantics but cannot add capability to a backend. C:ReadWriteOnce restricts volume mounting to one node, not globally one Pod; multi-node sharing needs backend support. That is relevant to a different intervention. For the stated situation, the required action is: Use a ReadWriteMany-capable shared filesystem and a matching PV or StorageClass. The governing reason is: Kubernetes access modes express requested attachment semantics but cannot add capability to a backend. D:hostPath refers to a specific node filesystem and does not provide cluster-wide data mobility. That is relevant to a different intervention. For the stated situation, the required action is: Use a ReadWriteMany-capable shared filesystem and a matching PV or StorageClass. The governing reason is: Kubernetes access modes express requested attachment semantics but cannot add capability to a backend.
Question 185A team wants its viewer ClusterRole to cover a new namespaced custom resource but the permissions do not propagate. An engineer recommends: Update the intended ClusterRole rules or its controlled aggregation labels and verify the bound roles. Which Kubernetes behavior best explains why this correction fits? Aggregated ClusterRoles rely on matching labels on source ClusterRoles; ordinary ClusterRoles do not aggregate automatically. A RoleBinding restricts a Role or referenced ClusterRole to its own namespace; a ClusterRoleBinding grants across namespaces. 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. ExplanationCorrect Answer A:Aggregated ClusterRoles rely on matching labels on source ClusterRoles; ordinary ClusterRoles do not aggregate automatically. This explains why the proposed action—update the intended ClusterRole rules or its controlled aggregation labels and verify the bound roles.—is appropriate. Direct confirmation is: The viewer can list only the approved custom resources in the bound namespace after reconciliation.Incorrect Answers B:A RoleBinding restricts a Role or referenced ClusterRole to its own namespace; a ClusterRoleBinding grants across namespaces. This does not establish the proposed intervention. The governing principle here is: Aggregated ClusterRoles rely on matching labels on source ClusterRoles; ordinary ClusterRoles do not aggregate automatically. Apply it by: Update the intended ClusterRole rules or its controlled aggregation labels and verify the bound roles. C: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: Aggregated ClusterRoles rely on matching labels on source ClusterRoles; ordinary ClusterRoles do not aggregate automatically. Apply it by: Update the intended ClusterRole rules or its controlled aggregation labels and verify the bound roles. D: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: Aggregated ClusterRoles rely on matching labels on source ClusterRoles; ordinary ClusterRoles do not aggregate automatically. Apply it by: Update the intended ClusterRole rules or its controlled aggregation labels and verify the bound roles.
Question 186A PVC remains Pending although a statically created PV exists with the same capacity because access modes differ. Which Kubernetes administration action most directly addresses the observed failure? Match the claim's accessModes, storage class and capacity to the intended static PV. Create or reference the PVC in the Pod's own namespace with the approved storage configuration. Perform the approved reclaim and rebind procedure, including handling stale claimRef where safe. Inspect VolumeAttachment objects, CSI controller and node logs, then clear a genuinely stale attachment using the documented driver process. ExplanationCorrect Answer A:Match the claim's accessModes, storage class and capacity to the intended static PV. This corrects the specific failure because a PVC must satisfy PV binding predicates, not merely request a compatible size. Verify it by checking: The PVC binds the expected PV and a consumer Pod mounts it successfully.Incorrect Answers B:PVCs are namespace-scoped and Pods cannot mount another namespace's claim by name. That is relevant to a different intervention. For the stated situation, the required action is: Match the claim's accessModes, storage class and capacity to the intended static PV. The governing reason is: A PVC must satisfy PV binding predicates, not merely request a compatible size. C:A Released PV may preserve its previous claim reference until an administrator makes it available. That is relevant to a different intervention. For the stated situation, the required action is: Match the claim's accessModes, storage class and capacity to the intended static PV. The governing reason is: A PVC must satisfy PV binding predicates, not merely request a compatible size. D:A Bound PVC proves allocation but not that attach, stage and publish operations have succeeded. That is relevant to a different intervention. For the stated situation, the required action is: Match the claim's accessModes, storage class and capacity to the intended static PV. The governing reason is: A PVC must satisfy PV binding predicates, not merely request a compatible size.
Question 187A NodePort Service succeeds from one worker but fails from another because a host firewall blocks its allocated port. What is the most direct consequence if the underlying problem is left unresolved? Inter-node service calls can fail while same-node health checks pass. Service traffic becomes dependent on which worker receives the connection. Some clients can fail even when the Service appears reachable by another family. Clients may repeatedly contact stale or nonexistent endpoints. ExplanationCorrect Answer B:Service traffic becomes dependent on which worker receives the connection. This directly follows from the failed condition. The preventive correction is: Validate permitted NodePort reachability and node firewall rules across required entry nodes. The governing Kubernetes behavior is: NodePort connectivity depends on node networking and service-proxy dataplane behavior, not just a valid Service object.Incorrect Answers A: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: Service traffic becomes dependent on which worker receives the connection. 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: Service traffic becomes dependent on which worker receives the connection. D: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: Service traffic becomes dependent on which worker receives the connection.
Question 188A NodeLocal DNSCache daemon runs but DNS failures happen only on nodes with a stale link-local resolver entry. Following the proposed change—Verify node-local DNS listener addresses and Pod resolv.conf propagation on affected nodes—which observation best demonstrates that the particular fault is resolved? Fresh Pods on previously broken nodes resolve internal and external names through the configured listener. Known Service names resolve and CoreDNS Pods have ready endpoints with successful queries. Approved external probes succeed while prohibited destinations remain blocked. EndpointSlices list ready Pods and a port-specific request succeeds after selector repair. ExplanationCorrect Answer A:Fresh Pods on previously broken nodes resolve internal and external names through the configured listener. This validates the stated intervention—verify node-local DNS listener addresses and Pod resolv.conf propagation on affected nodes.—rather than an unrelated cluster change. The relevant mechanism is: Per-node DNS cache configuration can produce node-specific resolution failures.Incorrect Answers B:Pod networking can work while the separate cluster DNS service path is unavailable. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Fresh Pods on previously broken nodes resolve internal and external names through the configured listener. C:Egress isolation may deny flows independently of Service discovery and Pod health. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Fresh Pods on previously broken nodes resolve internal and external names through the configured listener. D:DNS resolution and a Service object do not guarantee a valid ready backend endpoint. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Fresh Pods on previously broken nodes resolve internal and external names through the configured listener.
Question 189A kubeadm-renewed API certificate omits a valid DNS SAN and kubectl fails with a hostname validation error. Which Kubernetes administration action most directly addresses the observed failure? Restore accurate time synchronization before investigating certificate renewal. Inspect the kubelet-managed static Pod manifest and its container logs, then repair invalid API server flags. Correct the supported advertise-address and stable endpoint configuration with matching certificates. Regenerate the affected serving certificate with the actual API endpoint names and rotate it safely. ExplanationCorrect Answer D:Regenerate the affected serving certificate with the actual API endpoint names and rotate it safely. This corrects the specific failure because clients validate control-plane TLS certificate identity before trusting API responses. Verify it by checking: kubectl establishes a verified TLS session to the intended endpoint without insecure skipping.Incorrect Answers A:TLS certificate validity periods depend on reasonable clock agreement between peers. That is relevant to a different intervention. For the stated situation, the required action is: Regenerate the affected serving certificate with the actual API endpoint names and rotate it safely. The governing reason is: Clients validate control-plane TLS certificate identity before trusting API responses. 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: Regenerate the affected serving certificate with the actual API endpoint names and rotate it safely. The governing reason is: Clients validate control-plane TLS certificate identity before trusting API responses. C:Control-plane advertised addresses must be reachable through the cluster's intended topology. That is relevant to a different intervention. For the stated situation, the required action is: Regenerate the affected serving certificate with the actual API endpoint names and rotate it safely. The governing reason is: Clients validate control-plane TLS certificate identity before trusting API responses.
Question 190A storage policy requires encrypted volumes but an engineer creates a StorageClass without the provider's encryption parameters. 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. Install and verify the CSI node plugin on every eligible attachment node. Set exactly the intended default class annotation and specify storageClassName explicitly for critical claims. ExplanationCorrect Answer B:Define the correct CSI StorageClass parameters and verify the provisioned volume security properties. This corrects the specific failure because storageClass parameters are driver-specific and determine backend provisioning behavior. Verify it by checking: A test PV is created with the required encryption setting reported by the storage provider.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: Define the correct CSI StorageClass parameters and verify the provisioned volume security properties. The governing reason is: StorageClass parameters are driver-specific and determine backend provisioning behavior. C: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: Define the correct CSI StorageClass parameters and verify the provisioned volume security properties. The governing reason is: StorageClass parameters are driver-specific and determine backend provisioning behavior. D:PVCs without a specified class can inherit the cluster's default storage class. That is relevant to a different intervention. For the stated situation, the required action is: Define the correct CSI StorageClass parameters and verify the provisioned volume security properties. The governing reason is: StorageClass parameters are driver-specific and determine backend provisioning behavior.