Practice Exams:

Linux Foundation KCNA Dumps

EXAM: Kubernetes and Cloud Native Associate
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

KCNA Premium Bundle


  • Premium File 333 Questions & Answers
  • Training Course 54 Lectures
  • Study Guide 410 Pages

Linux Foundation KCNA Practice Test 34

Question 330

A municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. What pair of supported action and practical verification should be approved?

  1. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Acceptance evidence: Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.
  2. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  3. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Acceptance evidence: Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
  4. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Explanation

Correct Answer

A:

The situation is that a municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Acceptance evidence: Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule. This pairing is justified because under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Incorrect Answers

B:

This action and check address the distinct objective “Explain the container runtime interface without conflating it with the control plane” instead of the stated acceptance requirement. The matching action is to apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

C:

This action and check address the distinct objective “Investigate readiness failures separately from liveness-related restarts” instead of the stated acceptance requirement. The matching action is to apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

D:

This action and check address the distinct objective “Use nodeSelector to place a workload on nodes with required labels” instead of the stated acceptance requirement. The matching action is to apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Question 331

A library's report generator is repeatedly OOMKilled while its Pod remains scheduled on the same node. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access.
  2. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure.
  3. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate.
  4. Inspect image default command and Pod command or args settings to determine what executable starts in the container.

Explanation

Correct Answer

B:

Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. This resolves the issue because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. To verify, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

Incorrect Answers

A:

This option addresses the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”, not the immediate requirement. Service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure. For the stated case, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

C:

This option addresses the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, not the immediate requirement. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. For the stated case, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

D:

This option addresses the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, not the immediate requirement. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. For the stated case, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Question 332

A library's report generator is repeatedly OOMKilled while its Pod remains scheduled on the same node. Which platform mechanism explains why the suitable approach works?

  1. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
  2. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
  3. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
  4. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Explanation

Correct Answer

A:

CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. It supports this action: Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. To confirm, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

Incorrect Answers

B:

That statement explains the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

C:

That statement explains the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

D:

That statement explains the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Question 333

A library's report generator is repeatedly OOMKilled while its Pod remains scheduled on the same node. Which controlled observation would best validate the intended improvement?

  1. Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  2. Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
  3. Compare the governance and release activity of two projects and document which operational support and security tests are still required.
  4. Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

Explanation

Correct Answer

A:

Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod. This is the relevant test because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”, but not the required result. For this case, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

C:

This check would help evaluate the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, but not the required result. For this case, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

D:

This check would help evaluate the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”, but not the required result. For this case, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

Question 334

A library's report generator is repeatedly OOMKilled while its Pod remains scheduled on the same node. An engineer proposes: “Treat an OOMKilled container as a DNS connectivity problem and change Service names instead of resource settings.” What adverse outcome would be most direct?

  1. Clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
  2. The Pod remains unschedulable because requested capacity and node feasibility did not change.
  3. A workload continues crashing because the root cause is memory exhaustion, not name resolution.
  4. The edit is invisible to the API and controller reconciliation, so subsequent node restarts or scheduling can discard it.

Explanation

Correct Answer

C:

A workload continues crashing because the root cause is memory exhaustion, not name resolution. The shortcut creates this risk because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Incorrect Answers

A:

That outcome concerns the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.

B:

That outcome concerns the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.

D:

That outcome concerns the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.

Question 335

A library's report generator is repeatedly OOMKilled while its Pod remains scheduled on the same node. What pair of supported action and practical verification should be approved?

  1. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Acceptance evidence: Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
  2. Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Acceptance evidence: Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
  3. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Acceptance evidence: Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  4. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Acceptance evidence: Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Explanation

Correct Answer

C:

Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Acceptance evidence: Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod. This pairing is justified because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Incorrect Answers

A:

This action and check address the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” instead of the stated acceptance requirement. The matching action is to review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

B:

This action and check address the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” instead of the stated acceptance requirement. The matching action is to review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

D:

This action and check address the distinct objective “Identify reconciliation work performed by kube-controller-manager” instead of the stated acceptance requirement. The matching action is to review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

Question 336

A factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. What technical action should the platform team take in this situation?

  1. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root.
  2. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy.
  3. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones.
  4. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure.

Explanation

Correct Answer

D:

The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. This resolves the issue because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. To verify, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

Incorrect Answers

A:

This option addresses the distinct objective “Run images with least-privilege runtime security contexts”, not the immediate requirement. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. For the stated case, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

B:

This option addresses the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”, not the immediate requirement. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support. For the stated case, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

C:

This option addresses the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, not the immediate requirement. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable. For the stated case, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Question 337

A factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
  2. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.
  3. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
  4. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Explanation

Correct Answer

C:

The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. It supports this action: Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. To confirm, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

Incorrect Answers

A:

That statement explains the distinct objective “Use nodeSelector to place a workload on nodes with required labels” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

B:

That statement explains the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

D:

That statement explains the distinct objective “Use kubectl get and describe for distinct inspection needs” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Question 338

A factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. What acceptance check most directly confirms this requirement is met?

  1. Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  2. Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  3. Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
  4. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Explanation

Correct Answer

A:

The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod. This is the relevant test because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Use nodeSelector to place a workload on nodes with required labels”, but not the required result. For this case, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

C:

This check would help evaluate the distinct objective “Distinguish etcd persistence from running workload data”, but not the required result. For this case, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

D:

This check would help evaluate the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”, but not the required result. For this case, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

Question 339

A factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. The team suggests: “Treat an OOMKilled container as a DNS connectivity problem and change Service names instead of resource settings.” Which failure should the reviewer anticipate?

  1. The Pod remains unschedulable because requested capacity and node feasibility did not change.
  2. A workload continues crashing because the root cause is memory exhaustion, not name resolution.
  3. Operators can see the metadata but the Service cannot select the desired Pods using that annotation.
  4. Credentials can leak through registries and the binaries cannot be compared as the same tested artifact.

Explanation

Correct Answer

B:

The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. A workload continues crashing because the root cause is memory exhaustion, not name resolution. The shortcut creates this risk because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Incorrect Answers

A:

The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. That outcome concerns the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.

C:

That outcome concerns the distinct objective “Use annotations for tool metadata rather than workload selection”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.

D:

That outcome concerns the distinct objective “Externalize application configuration from an image while protecting secrets”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.

Question 340

A factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. Which engineering change and test jointly addresses the scenario?

  1. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Acceptance evidence: In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  2. Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Acceptance evidence: Set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
  3. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Acceptance evidence: Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  4. Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Acceptance evidence: Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Explanation

Correct Answer

C:

The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Acceptance evidence: Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod. This pairing is justified because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Incorrect Answers

A:

This action and check address the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” instead of the stated acceptance requirement. The matching action is to review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

B:

This action and check address the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes” instead of the stated acceptance requirement. The matching action is to review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

D:

This action and check address the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” instead of the stated acceptance requirement. The matching action is to review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests