Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 36
Question 350
A retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Acceptance evidence: Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment. This pairing is justified because a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Incorrect Answers
This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
This action and check address the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” instead of the stated acceptance requirement. The matching action is to run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
This action and check address the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” instead of the stated acceptance requirement. The matching action is to run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
Question 351
A student edits an application configuration file inside a Pod and loses the change after rollout. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. This resolves the issue because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. To verify, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
Incorrect Answers
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, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
This option addresses the distinct objective “Use nodeSelector to place a workload on nodes with required labels”, not the immediate requirement. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. For the stated case, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
This option addresses the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability”, not the immediate requirement. PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend. For the stated case, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
Question 352
A student edits an application configuration file inside a Pod and loses the change after rollout. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. It supports this action: Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. To confirm, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
Incorrect Answers
That statement explains the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
That statement explains the distinct objective “Distinguish the CNI Pod network from Service discovery and routing” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
That statement explains the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
Question 353
A student edits an application configuration file inside a Pod and loses the change after rollout. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears. This is the relevant test because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
Incorrect Answers
This check would help evaluate the distinct objective “Use image provenance and policy controls without trusting mutable tags”, but not the required result. For this case, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
This check would help evaluate the distinct objective “Use an immutable image digest for exact deployment provenance”, but not the required result. For this case, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
This check would help evaluate the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, but not the required result. For this case, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
Question 354
A student edits an application configuration file inside a Pod and loses the change after rollout. An engineer proposes: “Patch binaries manually inside a running container and assume the same patched bits automatically appear in newly started Pods.” What adverse outcome would be most direct?
Explanation
Correct Answer
Replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior. The shortcut creates this risk because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
Incorrect Answers
That outcome concerns the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.
That outcome concerns the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.
That outcome concerns the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.
Question 355
A student edits an application configuration file inside a Pod and loses the change after rollout. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Acceptance evidence: Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears. This pairing is justified because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
Incorrect Answers
This action and check address the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
This action and check address the distinct objective “Separate kube-scheduler decisions from kubelet execution” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
This action and check address the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
Question 356
A retail site ships a signed image and wants equivalent runtime contents across nodes. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. This resolves the issue because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. To verify, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
Incorrect Answers
This option addresses the distinct objective “Use kubectl get and describe for distinct inspection needs”, not the immediate requirement. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. For the stated case, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
This option addresses the distinct objective “Design a release rollback trigger from measurable service signals”, not the immediate requirement. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. For the stated case, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
This option addresses the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, not the immediate requirement. EmptyDir is initialized for a Pod and its contents can be shared among containers but do not survive the Pod's removal. For the stated case, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
Question 357
A retail site ships a signed image and wants equivalent runtime contents across nodes. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. It supports this action: Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. To confirm, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
Incorrect Answers
The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. That statement explains the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
That statement explains the distinct objective “Use image provenance and policy controls without trusting mutable tags” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
That statement explains the distinct objective “Use an immutable image digest for exact deployment provenance” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
Question 358
A retail site ships a signed image and wants equivalent runtime contents across nodes. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears. This is the relevant test because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
Incorrect Answers
This check would help evaluate the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, but not the required result. For this case, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
This check would help evaluate the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”, but not the required result. For this case, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
This check would help evaluate the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, but not the required result. For this case, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
Question 359
A retail site ships a signed image and wants equivalent runtime contents across nodes. The team suggests: “Patch binaries manually inside a running container and assume the same patched bits automatically appear in newly started Pods.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. Replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior. The shortcut creates this risk because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
Incorrect Answers
That outcome concerns the distinct objective “Understand readiness, liveness and startup probes as different signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.
That outcome concerns the distinct objective “Use SLI and SLO measures to focus reliability objectives”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.
That outcome concerns the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.
Question 360
A retail site ships a signed image and wants equivalent runtime contents across nodes. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Acceptance evidence: Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears. This pairing is justified because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
Incorrect Answers
This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
This action and check address the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
This action and check address the distinct objective “Use an immutable image digest for exact deployment provenance” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 34 - 10 Questions (Last Reviewed 18-Oct-2026)
- Linux Foundation KCNA Practice Test 35 - 10 Questions (Last Reviewed 17-Oct-2026)
- Linux Foundation KCNA Practice Test 36 - 10 Questions (Last Reviewed 16-Oct-2026)
- Linux Foundation KCNA Practice Test 37 - 10 Questions (Last Reviewed 15-Oct-2026)
- Linux Foundation KCNA Practice Test 38 - 10 Questions (Last Reviewed 14-Oct-2026)