Linux Foundation KCNA Dumps
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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
- Linux Foundation KCNA Practice Test 71 - 10 Questions (Last Reviewed 07-Nov-2026)
- Linux Foundation KCNA Practice Test 72 - 10 Questions (Last Reviewed 06-Nov-2026)
- Linux Foundation KCNA Practice Test 73 - 10 Questions (Last Reviewed 05-Nov-2026)
- Linux Foundation KCNA Practice Test 74 - 10 Questions (Last Reviewed 04-Nov-2026)
- Linux Foundation KCNA Practice Test 75 - 10 Questions (Last Reviewed 03-Nov-2026)