Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 80
Question 790
A bank needs one application image reused across branches without exposing connection secrets in its Git repository. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. 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. This pairing is justified because image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
Incorrect Answers
This action and check address the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” instead of the stated acceptance requirement. The matching action is to inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Its confirming test is to promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
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 inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Its confirming test is to promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
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 inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Its confirming test is to promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
Question 791
A charity checkout service sees a spike in failed transactions after a new version becomes ready. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. This resolves the issue because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. To verify, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
Incorrect Answers
This option addresses the distinct objective “Separate CI build verification from CD environment promotion”, not the immediate requirement. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
This option addresses the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, not the immediate requirement. Helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
This option addresses the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”, not the immediate requirement. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
Question 792
A charity checkout service sees a spike in failed transactions after a new version becomes ready. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. It supports this action: Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. To confirm, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
Incorrect Answers
That statement explains the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” rather than the cause in this case. The deciding mechanism here is that a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
That statement explains the distinct objective “Externalize application configuration from an image while protecting secrets” rather than the cause in this case. The deciding mechanism here is that a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
Question 793
A charity checkout service sees a spike in failed transactions after a new version becomes ready. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision. This is the relevant test because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
Incorrect Answers
This check would help evaluate the distinct objective “Define secure release governance with staged approvals and policy verification”, but not the required result. For this case, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
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, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
This check would help evaluate the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, but not the required result. For this case, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
Question 794
A charity checkout service sees a spike in failed transactions after a new version becomes ready. The change review contains this proposal: “Assume kubectl apply returned success means the new release is automatically safe for users.” What risk matters most?
Explanation
Correct Answer
Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted. The shortcut creates this risk because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
Incorrect Answers
That outcome concerns the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”; it is not the most direct consequence of this shortcut. The relevant consequence is that customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
That outcome concerns the distinct objective “Identify reconciliation work performed by kube-controller-manager”; it is not the most direct consequence of this shortcut. The relevant consequence is that customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
That outcome concerns the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”; it is not the most direct consequence of this shortcut. The relevant consequence is that customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
Question 795
A charity checkout service sees a spike in failed transactions after a new version becomes ready. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Acceptance evidence: Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision. This pairing is justified because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
Incorrect Answers
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 define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
This action and check address the distinct objective “Define secure release governance with staged approvals and policy verification” instead of the stated acceptance requirement. The matching action is to define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
This action and check address the distinct objective “Separate CI build verification from CD environment promotion” instead of the stated acceptance requirement. The matching action is to define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
Question 796
A college course service needs automated release gates beyond successful container startup. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
The situation is that a college course service needs automated release gates beyond successful container startup. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. This resolves the issue because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. To verify, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
Incorrect Answers
This option addresses the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, not the immediate requirement. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
This option addresses the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”, not the immediate requirement. HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
The situation is that a college course service needs automated release gates beyond successful container startup. This option addresses the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, not the immediate requirement. Helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
Question 797
A college course service needs automated release gates beyond successful container startup. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
The situation is that a college course service needs automated release gates beyond successful container startup. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. It supports this action: Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. To confirm, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
Incorrect Answers
That statement explains the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” rather than the cause in this case. The deciding mechanism here is that a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
The situation is that a college course service needs automated release gates beyond successful container startup. That statement explains the distinct objective “Externalize application configuration from an image while protecting secrets” rather than the cause in this case. The deciding mechanism here is that a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
That statement explains the distinct objective “Correlate application rollout revisions with error spikes” rather than the cause in this case. The deciding mechanism here is that a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
Question 798
A college course service needs automated release gates beyond successful container startup. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
The situation is that a college course service needs automated release gates beyond successful container startup. Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision. This is the relevant test because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
Incorrect Answers
This check would help evaluate the distinct objective “Use SLI and SLO measures to focus reliability objectives”, but not the required result. For this case, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
The situation is that a college course service needs automated release gates beyond successful container startup. 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, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
This check would help evaluate the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, but not the required result. For this case, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
Question 799
A college course service needs automated release gates beyond successful container startup. A shortcut is proposed: “Assume kubectl apply returned success means the new release is automatically safe for users.” Which technical consequence follows most closely?
Explanation
Correct Answer
The situation is that a college course service needs automated release gates beyond successful container startup. Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted. The shortcut creates this risk because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
Incorrect Answers
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 customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
That outcome concerns the distinct objective “Distinguish service mesh traffic management from external ingress routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
That outcome concerns the distinct objective “Configure Deployment rolling updates with availability safeguards”; it is not the most direct consequence of this shortcut. The relevant consequence is that customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
Question 800
A college course service needs automated release gates beyond successful container startup. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
The situation is that a college course service needs automated release gates beyond successful container startup. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Acceptance evidence: Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision. This pairing is justified because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
Incorrect Answers
This action and check address the distinct objective “Explain metrics, logs and traces as complementary observability signals” instead of the stated acceptance requirement. The matching action is to define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
The situation is that a college course service needs automated release gates beyond successful container startup. This action and check address the distinct objective “Separate CI build verification from CD environment promotion” instead of the stated acceptance requirement. The matching action is to define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 78 - 10 Questions (Last Reviewed 31-Oct-2026)
- Linux Foundation KCNA Practice Test 79 - 10 Questions (Last Reviewed 30-Oct-2026)
- Linux Foundation KCNA Practice Test 80 - 10 Questions (Last Reviewed 29-Oct-2026)
- Linux Foundation KCNA Practice Test 81 - 10 Questions (Last Reviewed 28-Oct-2026)
- Linux Foundation KCNA Practice Test 82 - 10 Questions (Last Reviewed 27-Oct-2026)