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.
Question 41A Secret update is expected to replace a running process's environment value immediately without restarting the container. What is the most direct consequence if the underlying problem is left unresolved? Pods can remain stuck on configuration errors despite valid image pulls. Hardcoded configuration creates drift across environments and unnecessary image rebuilds. The workload may continue authenticating with revoked credentials. Credentials can leak through broad configuration access. ExplanationCorrect Answer C:The workload may continue authenticating with revoked credentials. This directly follows from the failed condition. The preventive correction is: Roll out the workload or make the application reread supported projected files as required. The governing Kubernetes behavior is: Environment variables sourced from Secrets are fixed for the lifetime of a container process.Incorrect Answers A: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: The workload may continue authenticating with revoked credentials. B:ConfigMaps separate nonsecret configuration from the application container image. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: The workload may continue authenticating with revoked credentials. D: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: The workload may continue authenticating with revoked credentials.
Question 42A webhook service's certificate expires and API object creation fails with an admission webhook TLS error. Which Kubernetes administration action most directly addresses the observed failure? Compare Service selectors, ready EndpointSlices and actual container listener ports. Renew the webhook serving certificate and align its caBundle and Service reference. Inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS. Inspect EndpointSlice ready conditions and repair readiness before declaring the Service operational. ExplanationCorrect Answer B:Renew the webhook serving certificate and align its caBundle and Service reference. This corrects the specific failure because aPI admission webhooks require trusted TLS service connectivity during object admission. Verify it by checking: 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. That is relevant to a different intervention. For the stated situation, the required action is: Renew the webhook serving certificate and align its caBundle and Service reference. The governing reason is: API admission webhooks require trusted TLS service connectivity during object admission. C:Egress isolation may deny flows independently of Service discovery and Pod health. That is relevant to a different intervention. For the stated situation, the required action is: Renew the webhook serving certificate and align its caBundle and Service reference. The governing reason is: API admission webhooks require trusted TLS service connectivity during object admission. D:Services generally route only to endpoints considered ready, so Pod IP probes do not establish Service capacity. That is relevant to a different intervention. For the stated situation, the required action is: Renew the webhook serving certificate and align its caBundle and Service reference. The governing reason is: API admission webhooks require trusted TLS service connectivity during object admission.
Question 43A rollout is blocked because a PodDisruptionBudget allows no voluntary disruption during the worker drain. An engineer recommends: Inspect the PodDisruptionBudget and safely increase available replicas or adjust policy before retrying drain. Which Kubernetes behavior best explains why this correction fits? A drain evicts eligible Pods through the API and respects disruption policies unlike abrupt host shutdown. The eviction API respects PodDisruptionBudget limits for voluntary disruption. Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. Cordon status prevents new scheduling even when the node is otherwise Ready. ExplanationCorrect Answer B:The eviction API respects PodDisruptionBudget limits for voluntary disruption. This explains why the proposed action—inspect the PodDisruptionBudget and safely increase available replicas or adjust policy before retrying drain.—is appropriate. Direct confirmation is: PDB allowedDisruptions increases and a retried drain succeeds without reducing healthy replicas below policy.Incorrect Answers A:A drain evicts eligible Pods through the API and respects disruption policies unlike abrupt host shutdown. This does not establish the proposed intervention. The governing principle here is: The eviction API respects PodDisruptionBudget limits for voluntary disruption. Apply it by: Inspect the PodDisruptionBudget and safely increase available replicas or adjust policy before retrying drain. C:Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. This does not establish the proposed intervention. The governing principle here is: The eviction API respects PodDisruptionBudget limits for voluntary disruption. Apply it by: Inspect the PodDisruptionBudget and safely increase available replicas or adjust policy before retrying drain. D:Cordon status prevents new scheduling even when the node is otherwise Ready. This does not establish the proposed intervention. The governing principle here is: The eviction API respects PodDisruptionBudget limits for voluntary disruption. Apply it by: Inspect the PodDisruptionBudget and safely increase available replicas or adjust policy before retrying drain.
Question 44Two Ingress rules share one hostname with overlapping paths and an unexpected backend receives checkout requests. Which Kubernetes administration action most directly addresses the observed failure? Install and select a supported Ingress controller, then test its address and routing status. Define unambiguous host/path matching priorities and verify controller-specific reconciliation. Update the Ingress backend service.name and the correct service port reference. Create the correctly typed TLS Secret in the same namespace and reference it in the Ingress. ExplanationCorrect Answer B:Define unambiguous host/path matching priorities and verify controller-specific reconciliation. This corrects the specific failure because hTTP path matching and precedence affect which Service receives a request. Verify it by checking: Explicit /checkout and / paths each route to the intended backend under integration tests.Incorrect Answers A:Ingress API objects do not themselves implement HTTP routing; a controller supplies the dataplane. That is relevant to a different intervention. For the stated situation, the required action is: Define unambiguous host/path matching priorities and verify controller-specific reconciliation. The governing reason is: HTTP path matching and precedence affect which Service receives a request. C:Ingress rules point to Services by name and port within their namespace. That is relevant to a different intervention. For the stated situation, the required action is: Define unambiguous host/path matching priorities and verify controller-specific reconciliation. The governing reason is: HTTP path matching and precedence affect which Service receives a request. D:Ingress TLS termination depends on a usable referenced Secret and an active controller. That is relevant to a different intervention. For the stated situation, the required action is: Define unambiguous host/path matching priorities and verify controller-specific reconciliation. The governing reason is: HTTP path matching and precedence affect which Service receives a request.
Question 45A Pod mounts an emptyDir volume for application scratch data and expects its contents to survive Pod deletion. An engineer recommends: Move durable state to a PVC and reserve emptyDir for the lifetime of a Pod. Which Kubernetes behavior best explains why this correction fits? emptyDir follows the Pod lifetime and is removed when that Pod ceases to exist. Reclaim policy determines what happens to backend storage after a bound claim is released. hostPath refers to a specific node filesystem and does not provide cluster-wide data mobility. Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. ExplanationCorrect Answer A:emptyDir follows the Pod lifetime and is removed when that Pod ceases to exist. This explains why the proposed action—move durable state to a PVC and reserve emptyDir for the lifetime of a Pod.—is appropriate. Direct confirmation is: A replacement Pod retrieves persistent data from its PVC while scratch data is disposable.Incorrect Answers B:Reclaim policy determines what happens to backend storage after a bound claim is released. This does not establish the proposed intervention. The governing principle here is: emptyDir follows the Pod lifetime and is removed when that Pod ceases to exist. Apply it by: Move durable state to a PVC and reserve emptyDir for the lifetime of a Pod. C:hostPath refers to a specific node filesystem and does not provide cluster-wide data mobility. This does not establish the proposed intervention. The governing principle here is: emptyDir follows the Pod lifetime and is removed when that Pod ceases to exist. Apply it by: Move durable state to a PVC and reserve emptyDir for the lifetime of a Pod. D:Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. This does not establish the proposed intervention. The governing principle here is: emptyDir follows the Pod lifetime and is removed when that Pod ceases to exist. Apply it by: Move durable state to a PVC and reserve emptyDir for the lifetime of a Pod.
Question 46An old PV is marked Released after its claim was deleted but an operator assumes it will auto-bind to any new claim. Following the proposed change—Perform the approved reclaim and rebind procedure, including handling stale claimRef where safe—which observation best demonstrates that the particular fault is resolved? The Pod's namespace contains the referenced claim and volume mounts successfully. The PVC binds the expected PV and a consumer Pod mounts it successfully. The cloned claim contains the expected data under the supported source and namespace rules. The PV is Available or intentionally bound to the new approved PVC without losing data. ExplanationCorrect Answer D:The PV is Available or intentionally bound to the new approved PVC without losing data. This validates the stated intervention—perform the approved reclaim and rebind procedure, including handling stale claimRef where safe.—rather than an unrelated cluster change. The relevant mechanism is: A Released PV may preserve its previous claim reference until an administrator makes it available.Incorrect Answers A:PVCs are namespace-scoped and Pods cannot mount another namespace's claim by name. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The PV is Available or intentionally bound to the new approved PVC without losing data. B:A PVC must satisfy PV binding predicates, not merely request a compatible size. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The PV is Available or intentionally bound to the new approved PVC without losing data. C:PVC cloning and dataSource references have scope and driver capability constraints. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The PV is Available or intentionally bound to the new approved PVC without losing data.
Question 47A nightly maintenance action is managed through a manually recreated Pod and frequently misses its schedule. Which Kubernetes administration action most directly addresses the observed failure? Define a Job with suitable completions, parallelism and retry policy instead of a long-lived Deployment. Use rollout history to identify the last healthy revision and roll back the Deployment to it. Create a CronJob with an approved schedule, concurrencyPolicy and missed-run behavior. Configure rolling-update maxUnavailable and maxSurge according to available capacity and readiness requirements. ExplanationCorrect Answer C:Create a CronJob with an approved schedule, concurrencyPolicy and missed-run behavior. This corrects the specific failure because cronJobs create Jobs according to schedule while controlling overlap and missed executions. Verify it by checking: Scheduled Jobs appear at expected times and overlapping runs follow the configured policy.Incorrect Answers A:Jobs manage successful completion of finite work; Deployments maintain continuous desired replicas. That is relevant to a different intervention. For the stated situation, the required action is: Create a CronJob with an approved schedule, concurrencyPolicy and missed-run behavior. The governing reason is: CronJobs create Jobs according to schedule while controlling overlap and missed executions. B:Deployment revisions track supported rollout history and a rollback restores a previous Pod template. That is relevant to a different intervention. For the stated situation, the required action is: Create a CronJob with an approved schedule, concurrencyPolicy and missed-run behavior. The governing reason is: CronJobs create Jobs according to schedule while controlling overlap and missed executions. D:The Deployment rollout strategy controls the allowed temporary excess and unavailable replicas. That is relevant to a different intervention. For the stated situation, the required action is: Create a CronJob with an approved schedule, concurrencyPolicy and missed-run behavior. The governing reason is: CronJobs create Jobs according to schedule while controlling overlap and missed executions.
Question 48A kubeadm-renewed API certificate omits a valid DNS SAN and kubectl fails with a hostname validation error. What is the most direct consequence if the underlying problem is left unresolved? Time skew can mimic certificate expiration and create avoidable credential replacement. Cluster control functions remain unavailable while the API server fails. Nodes may become isolated from an otherwise running API process. Administrative automation can stop working after certificate rotation. ExplanationCorrect Answer D:Administrative automation can stop working after certificate rotation. This directly follows from the failed condition. The preventive correction is: Regenerate the affected serving certificate with the actual API endpoint names and rotate it safely. The governing Kubernetes behavior is: Clients validate control-plane TLS certificate identity before trusting API responses.Incorrect Answers A:TLS certificate validity periods depend on reasonable clock agreement between peers. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Administrative automation can stop working after certificate rotation. B:kubeadm control-plane components often run as static Pods from local manifests. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Administrative automation can stop working after certificate rotation. C:Control-plane advertised addresses must be reachable through the cluster's intended topology. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Administrative automation can stop working after certificate rotation.
Question 49A new cluster uses a hostname as the API endpoint but its DNS record points to a decommissioned load balancer. An engineer recommends: Validate the stable controlPlaneEndpoint name and its reachable load balancer before kubeadm initialization. Which Kubernetes behavior best explains why this correction fits? Node prerequisites must be consistent with kubelet behavior and runtime support. Bootstrap and reconciliation require distinct network flows among the API server, etcd, and nodes. Clients and join operations need a durable API endpoint independent of one control-plane host. The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings. ExplanationCorrect Answer C:Clients and join operations need a durable API endpoint independent of one control-plane host. This explains why the proposed action—validate the stable controlPlaneEndpoint name and its reachable load balancer before kubeadm initialization.—is appropriate. Direct confirmation is: The endpoint resolves to an active listener and kubeadm discovery succeeds from a worker.Incorrect Answers A:Node prerequisites must be consistent with kubelet behavior and runtime support. This does not establish the proposed intervention. The governing principle here is: Clients and join operations need a durable API endpoint independent of one control-plane host. Apply it by: Validate the stable controlPlaneEndpoint name and its reachable load balancer before kubeadm initialization. B:Bootstrap and reconciliation require distinct network flows among the API server, etcd, and nodes. This does not establish the proposed intervention. The governing principle here is: Clients and join operations need a durable API endpoint independent of one control-plane host. Apply it by: Validate the stable controlPlaneEndpoint name and its reachable load balancer before kubeadm initialization. D:The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings. This does not establish the proposed intervention. The governing principle here is: Clients and join operations need a durable API endpoint independent of one control-plane host. Apply it by: Validate the stable controlPlaneEndpoint name and its reachable load balancer before kubeadm initialization.
Question 50A policy permits application TCP egress but forgets DNS and Pods cannot resolve Service names. An engineer recommends: Permit DNS traffic to the intended cluster DNS endpoints under the egress policy. Which Kubernetes behavior best explains why this correction fits? An egress-isolated Pod needs an explicit permitted path to each required destination. DNS name resolution is a separate network flow from the application connection. NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. Ingress and egress restrictions are evaluated independently and policy effects compose additively. ExplanationCorrect Answer B:DNS name resolution is a separate network flow from the application connection. This explains why the proposed action—permit DNS traffic to the intended cluster DNS endpoints under the egress policy.—is appropriate. Direct confirmation is: The Pod resolves a Service name and reaches it while unrelated outbound access remains denied.Incorrect Answers A: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: DNS name resolution is a separate network flow from the application connection. Apply it by: Permit DNS traffic to the intended cluster DNS endpoints under the egress policy. 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: DNS name resolution is a separate network flow from the application connection. Apply it by: Permit DNS traffic to the intended cluster DNS endpoints under the egress policy. 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: DNS name resolution is a separate network flow from the application connection. Apply it by: Permit DNS traffic to the intended cluster DNS endpoints under the egress policy.