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 73

Question 720

A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Which implementation together with matching acceptance evidence best meets this case?

  1. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Acceptance evidence: Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
  2. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Acceptance evidence: Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
  3. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Acceptance evidence: Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  4. Use emptyDir for temporary sharing between containers within a Pod, and PVC-backed storage when data must survive Pod replacement. Acceptance evidence: Write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics.

Explanation

Correct Answer

A:

The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Acceptance evidence: Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior. This pairing is justified because a PV reclaim policy controls how underlying storage is treated after claim release; deleting the Pod and deleting the PVC are distinct events with different effects.

Incorrect Answers

B:

This action and check address the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

C:

This action and check address the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

D:

This action and check address the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Question 721

A hospital portal wants a no-disruption upgrade across several application replicas. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments.
  2. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement.
  3. Pin validated production images by registry digest and promote the same signed artifact across environments.
  4. Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression.

Explanation

Correct Answer

B:

Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. This resolves the issue because a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available. To verify, upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

Incorrect Answers

A:

This option addresses the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”, not the immediate requirement. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files. For the stated case, a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

C:

This option addresses the distinct objective “Use an immutable image digest for exact deployment provenance”, not the immediate requirement. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. For the stated case, a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

D:

This option addresses the distinct objective “Correlate application rollout revisions with error spikes”, not the immediate requirement. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality. For the stated case, a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Question 722

A hospital portal wants a no-disruption upgrade across several application replicas. Which platform mechanism explains why the suitable approach works?

  1. A rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.
  2. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
  3. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
  4. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Explanation

Correct Answer

A:

A rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available. It supports this action: Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. To confirm, upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

Incorrect Answers

B:

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 a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

C:

That statement explains the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend” rather than the cause in this case. The deciding mechanism here is that a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

D:

That statement explains the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” rather than the cause in this case. The deciding mechanism here is that a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Question 723

A hospital portal wants a no-disruption upgrade across several application replicas. Which controlled observation would best validate the intended improvement?

  1. In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  2. Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  3. Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.
  4. Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.

Explanation

Correct Answer

C:

Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability. This is the relevant test because a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”, but not the required result. For this case, upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

B:

This check would help evaluate the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”, but not the required result. For this case, upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

D:

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, upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

Question 724

A hospital portal wants a no-disruption upgrade across several application replicas. An engineer proposes: “Set maxUnavailable equal to all replicas on a mission-critical API and assume the word rolling guarantees zero downtime.” What adverse outcome would be most direct?

  1. The workload gains unnecessary listening services and mutable changes that disappear on replacement.
  2. The production binary can differ from the validated image even though the release version label matches.
  3. The image-pull issue stays unresolved because etcd is not the node component managing container starts.
  4. All existing Pods could become unavailable before replacements pass readiness, breaking live requests.

Explanation

Correct Answer

D:

All existing Pods could become unavailable before replacements pass readiness, breaking live requests. The shortcut creates this risk because a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”; it is not the most direct consequence of this shortcut. The relevant consequence is that all existing Pods could become unavailable before replacements pass readiness, breaking live requests.

B:

That outcome concerns the distinct objective “Separate CI build verification from CD environment promotion”; it is not the most direct consequence of this shortcut. The relevant consequence is that all existing Pods could become unavailable before replacements pass readiness, breaking live requests.

C:

That outcome concerns the distinct objective “Recognize the kubelet role in local Pod lifecycle management”; it is not the most direct consequence of this shortcut. The relevant consequence is that all existing Pods could become unavailable before replacements pass readiness, breaking live requests.

Question 725

A hospital portal wants a no-disruption upgrade across several application replicas. What pair of supported action and practical verification should be approved?

  1. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Acceptance evidence: Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.
  2. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Acceptance evidence: Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
  3. 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.
  4. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Acceptance evidence: Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Explanation

Correct Answer

A:

Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Acceptance evidence: Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability. This pairing is justified because a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Incorrect Answers

B:

This action and check address the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” instead of the stated acceptance requirement. The matching action is to choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Its confirming test is to upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

C:

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 choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Its confirming test is to upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

D:

This action and check address the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” instead of the stated acceptance requirement. The matching action is to choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Its confirming test is to upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

Question 726

A university course API needs an explicit release budget while rotating images during class registration. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected.
  2. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped.
  3. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement.
  4. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup.

Explanation

Correct Answer

C:

The situation is that a university course API needs an explicit release budget while rotating images during class registration. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. This resolves the issue because a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available. To verify, upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

Incorrect Answers

A:

This option addresses the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, not the immediate requirement. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. For the stated case, a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

B:

This option addresses the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, not the immediate requirement. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. For the stated case, a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

D:

This option addresses the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”, not the immediate requirement. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings. For the stated case, a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Question 727

A university course API needs an explicit release budget while rotating images during class registration. Which causal explanation supports the intended design choice?

  1. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
  2. CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.
  3. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.
  4. A rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Explanation

Correct Answer

D:

The situation is that a university course API needs an explicit release budget while rotating images during class registration. A rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available. It supports this action: Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. To confirm, upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

Incorrect Answers

A:

That statement explains the distinct objective “Apply GitOps reconciliation with a version-controlled desired state” rather than the cause in this case. The deciding mechanism here is that a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

B:

That statement explains the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core” rather than the cause in this case. The deciding mechanism here is that a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

C:

That statement explains the distinct objective “Separate CI build verification from CD environment promotion” rather than the cause in this case. The deciding mechanism here is that a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Question 728

A university course API needs an explicit release budget while rotating images during class registration. Which test provides the strongest evidence of a correct implementation?

  1. Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.
  2. Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
  3. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  4. Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

Explanation

Correct Answer

A:

The situation is that a university course API needs an explicit release budget while rotating images during class registration. Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability. This is the relevant test because a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, but not the required result. For this case, upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

C:

This check would help evaluate the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, but not the required result. For this case, upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

D:

This check would help evaluate the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”, but not the required result. For this case, upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

Question 729

A university course API needs an explicit release budget while rotating images during class registration. A shortcut is proposed: “Set maxUnavailable equal to all replicas on a mission-critical API and assume the word rolling guarantees zero downtime.” Which technical consequence follows most closely?

  1. All existing Pods could become unavailable before replacements pass readiness, breaking live requests.
  2. The change is repeatedly reverted, making incident response and audit history inconsistent.
  3. Incident diagnosis confuses placement failures with container startup errors and targets the wrong component.
  4. An urgent fix is applied to only one environment and configuration drift grows difficult to audit.

Explanation

Correct Answer

A:

The situation is that a university course API needs an explicit release budget while rotating images during class registration. All existing Pods could become unavailable before replacements pass readiness, breaking live requests. The shortcut creates this risk because a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Incorrect Answers

B:

That outcome concerns the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”; it is not the most direct consequence of this shortcut. The relevant consequence is that all existing Pods could become unavailable before replacements pass readiness, breaking live requests.

C:

That outcome concerns the distinct objective “Separate kube-scheduler decisions from kubelet execution”; it is not the most direct consequence of this shortcut. The relevant consequence is that all existing Pods could become unavailable before replacements pass readiness, breaking live requests.

D:

That outcome concerns the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”; it is not the most direct consequence of this shortcut. The relevant consequence is that all existing Pods could become unavailable before replacements pass readiness, breaking live requests.

Question 730

A university course API needs an explicit release budget while rotating images during class registration. Which combined solution and independent check are most directly justified?

  1. 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.
  2. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Acceptance evidence: Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
  3. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Acceptance evidence: Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.
  4. 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.

Explanation

Correct Answer

C:

The situation is that a university course API needs an explicit release budget while rotating images during class registration. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Acceptance evidence: Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability. This pairing is justified because a rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.

Incorrect Answers

A:

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 choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Its confirming test is to upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

B:

This action and check address the distinct objective “Externalize application configuration from an image while protecting secrets” instead of the stated acceptance requirement. The matching action is to choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Its confirming test is to upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

D:

The situation is that a university course API needs an explicit release budget while rotating images during class registration. 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 choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Its confirming test is to upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests