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 29

Question 280

A college live-stream service needs to avoid putting every replica on the same machine during exams. Which implementation together with matching acceptance evidence best meets this case?

  1. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
  2. 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.
  3. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Acceptance evidence: Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
  4. 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.

Explanation

Correct Answer

A:

The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers. This pairing is justified because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Incorrect Answers

B:

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 configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

C:

This action and check address the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

D:

This action and check address the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

Question 281

A small analytics service prefers being scheduled near a low-latency cache. Which engineering approach is the most appropriate for this cloud-native case?

  1. Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic.
  2. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate.
  3. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism.
  4. Inspect image default command and Pod command or args settings to determine what executable starts in the container.

Explanation

Correct Answer

A:

Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. This resolves the issue because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. To verify, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Incorrect Answers

B:

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, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

C:

This option addresses the distinct objective “Design a release rollback trigger from measurable service signals”, not the immediate requirement. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. For the stated case, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

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, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Question 282

A small analytics service prefers being scheduled near a low-latency cache. What infrastructure principle makes the correct treatment effective?

  1. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
  2. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
  3. Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
  4. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Explanation

Correct Answer

D:

Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. It supports this action: Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. To confirm, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Incorrect Answers

A:

That statement explains the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” rather than the cause in this case. The deciding mechanism here is that pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

B:

That statement explains the distinct objective “Run images with least-privilege runtime security contexts” rather than the cause in this case. The deciding mechanism here is that pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

C:

That statement explains the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” rather than the cause in this case. The deciding mechanism here is that pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Question 283

A small analytics service prefers being scheduled near a low-latency cache. What verification result would most convincingly distinguish a working solution from a claim?

  1. Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  2. Describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events.
  3. Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  4. Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Explanation

Correct Answer

D:

Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately. This is the relevant test because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, but not the required result. For this case, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

B:

This check would help evaluate the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, but not the required result. For this case, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

C:

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, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Question 284

A small analytics service prefers being scheduled near a low-latency cache. The change review contains this proposal: “Set podAffinity for a backend and treat same-node placement as authorization to read another Pod's private files.” What risk matters most?

  1. The scheduler could place multiple replicas together, leaving a node without the intended local collector.
  2. The workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
  3. The true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.
  4. An unsupported runtime assumption misdirects troubleshooting and may block node bootstrap.

Explanation

Correct Answer

B:

The workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured. The shortcut creates this risk because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Incorrect Answers

A:

That outcome concerns the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.

C:

That outcome concerns the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.

D:

That outcome concerns the distinct objective “Explain the container runtime interface without conflating it with the control plane”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.

Question 285

A small analytics service prefers being scheduled near a low-latency cache. Which implementation together with matching acceptance evidence best meets this case?

  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. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Acceptance evidence: Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
  3. 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.
  4. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Acceptance evidence: Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Explanation

Correct Answer

C:

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. This pairing is justified because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

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 choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Its confirming test is to apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

B:

This action and check address the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” instead of the stated acceptance requirement. The matching action is to choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Its confirming test is to apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

D:

This action and check address the distinct objective “Distinguish preferred node affinity from required scheduling rules” instead of the stated acceptance requirement. The matching action is to choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Its confirming test is to apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Question 286

A retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic.
  2. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure.
  3. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope.
  4. Send cluster changes through the authenticated Kubernetes API and inspect the object returned by the API server rather than changing node processes directly.

Explanation

Correct Answer

A:

The situation is that a retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. This resolves the issue because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. To verify, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Incorrect Answers

B:

This option addresses the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, not the immediate requirement. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. For the stated case, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

C:

This option addresses the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, not the immediate requirement. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. For the stated case, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

D:

This option addresses the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”, not the immediate requirement. The kube-apiserver validates authorized API requests and exposes the declarative resource interface; kubelets and controllers subsequently reconcile the saved desired state. For the stated case, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Question 287

A retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Which causal explanation supports the intended design choice?

  1. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
  2. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
  3. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
  4. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Explanation

Correct Answer

C:

The situation is that a retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. It supports this action: Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. To confirm, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Incorrect Answers

A:

That statement explains the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” rather than the cause in this case. The deciding mechanism here is that pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

B:

That statement explains the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” rather than the cause in this case. The deciding mechanism here is that pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

D:

That statement explains the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” rather than the cause in this case. The deciding mechanism here is that pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Question 288

A retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Which test provides the strongest evidence of a correct implementation?

  1. Compare the governance and release activity of two projects and document which operational support and security tests are still required.
  2. Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
  3. Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  4. Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Explanation

Correct Answer

D:

The situation is that a retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately. This is the relevant test because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Incorrect Answers

A:

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, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

B:

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, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

C:

This check would help evaluate the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, but not the required result. For this case, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Question 289

A retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. A shortcut is proposed: “Set podAffinity for a backend and treat same-node placement as authorization to read another Pod's private files.” Which technical consequence follows most closely?

  1. The workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
  2. A single node failure can take down all replicas despite a desired count greater than one.
  3. A failed release can leave the service unavailable with no retained tested deployment revision.
  4. Applications fail on migration when plugin behavior or provider-specific components were never evaluated.

Explanation

Correct Answer

A:

The situation is that a retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. The workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured. The shortcut creates this risk because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Incorrect Answers

B:

That outcome concerns the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.

C:

That outcome concerns the distinct objective “Use rollout status and undo to validate and recover a Deployment release”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.

D:

That outcome concerns the distinct objective “Understand open standards and vendor-neutral community collaboration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.

Question 290

A retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Which combined solution and independent check are most directly justified?

  1. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Acceptance evidence: In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.
  2. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
  3. 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.
  4. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Acceptance evidence: Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

Explanation

Correct Answer

C:

The situation is that a retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. 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. This pairing is justified because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Incorrect Answers

A:

This action and check address the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” instead of the stated acceptance requirement. The matching action is to choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Its confirming test is to apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

B:

This action and check address the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” instead of the stated acceptance requirement. The matching action is to choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Its confirming test is to apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

D:

This action and check address the distinct objective “Use Events and pod describe for failed volume mounting” instead of the stated acceptance requirement. The matching action is to choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Its confirming test is to apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests