Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 79
Question 780
A college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. 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. This pairing is justified because kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.
Incorrect Answers
This action and check address the distinct objective “Correlate application rollout revisions with error spikes” instead of the stated acceptance requirement. The matching action is to keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Its confirming test is to run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.
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 keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Its confirming test is to run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.
This action and check address the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” instead of the stated acceptance requirement. The matching action is to keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Its confirming test is to run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.
Question 781
A university portal uses distinct nonsecret service URLs and credentials in staging and production. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. This resolves the issue because image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. To verify, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
Incorrect Answers
This option addresses the distinct objective “Distinguish Deployment desired state from a manually created Pod”, not the immediate requirement. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. For the stated case, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
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, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
This option addresses the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”, not the immediate requirement. Kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. For the stated case, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
Question 782
A university portal uses distinct nonsecret service URLs and credentials in staging and production. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. It supports this action: Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. To confirm, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
Incorrect Answers
That statement explains the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts” rather than the cause in this case. The deciding mechanism here is that image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
That statement explains the distinct objective “Understand readiness, liveness and startup probes as different signals” rather than the cause in this case. The deciding mechanism here is that image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
That statement explains the distinct objective “Design a release rollback trigger from measurable service signals” rather than the cause in this case. The deciding mechanism here is that image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
Question 783
A university portal uses distinct nonsecret service URLs and credentials in staging and production. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers. This is the relevant test 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 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, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
This check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
This check would help evaluate the distinct objective “Separate CI build verification from CD environment promotion”, but not the required result. For this case, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
Question 784
A university portal uses distinct nonsecret service URLs and credentials in staging and production. The change review contains this proposal: “Compile the database password directly into an application image for each environment and call those artifacts identical releases.” What risk matters most?
Explanation
Correct Answer
Credentials can leak through registries and the binaries cannot be compared as the same tested artifact. The shortcut creates this risk because image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
Incorrect Answers
That outcome concerns the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”; it is not the most direct consequence of this shortcut. The relevant consequence is that credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
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 credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
That outcome concerns the distinct objective “Use Pods as the shared network and storage execution unit”; it is not the most direct consequence of this shortcut. The relevant consequence is that credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
Question 785
A university portal uses distinct nonsecret service URLs and credentials in staging and production. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
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 “Apply GitOps reconciliation with a version-controlled desired state” 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 kubectl get and describe for distinct inspection needs” 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 Helm charts for parameterized application packages without equating them to cluster controllers” 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 786
A bank needs one application image reused across branches without exposing connection secrets in its Git repository. What technical action should the platform team take in this situation?
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. This resolves the issue because image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. To verify, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
Incorrect Answers
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, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
This option addresses the distinct objective “Distinguish a container image from a running container and its writable layer”, not the immediate requirement. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. For the stated case, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
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, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
Question 787
A bank needs one application image reused across branches without exposing connection secrets in its Git repository. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. It supports this action: Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. To confirm, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
Incorrect Answers
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 image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
That statement explains the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” rather than the cause in this case. The deciding mechanism here is that image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
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 image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
Question 788
A bank needs one application image reused across branches without exposing connection secrets in its Git repository. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers. This is the relevant test 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 check would help evaluate the distinct objective “Configure Deployment rolling updates with availability safeguards”, but not the required result. For this case, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. This check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
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, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
Question 789
A bank needs one application image reused across branches without exposing connection secrets in its Git repository. The team suggests: “Compile the database password directly into an application image for each environment and call those artifacts identical releases.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. Credentials can leak through registries and the binaries cannot be compared as the same tested artifact. The shortcut creates this risk because image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
Incorrect Answers
The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. 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 credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
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 credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
That outcome concerns the distinct objective “Use annotations for tool metadata rather than workload selection”; it is not the most direct consequence of this shortcut. The relevant consequence is that credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 77 - 10 Questions (Last Reviewed 01-Nov-2026)
- 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)