Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 74
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.
Question 731
A streaming startup wants to expose a new recommendation API to a small slice of traffic first. What technical action should the platform team take in this situation?
Explanation
Correct Answer
Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. This resolves the issue because canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update. To verify, in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
Incorrect Answers
This option addresses the distinct objective “Configure Deployment rolling updates with availability safeguards”, not the immediate requirement. 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. For the stated case, canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
This option addresses the distinct objective “Understand readiness, liveness and startup probes as different signals”, not the immediate requirement. Readiness affects endpoint eligibility while liveness can cause restarts; a startup probe defers other probe checks until initialization succeeds. For the stated case, canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
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, canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
Question 732
A streaming startup wants to expose a new recommendation API to a small slice of traffic first. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update. It supports this action: Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. To confirm, in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
Incorrect Answers
That statement explains the distinct objective “Configure Deployment rolling updates with availability safeguards” rather than the cause in this case. The deciding mechanism here is that canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
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 canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
That statement explains the distinct objective “Use kubectl get and describe for distinct inspection needs” rather than the cause in this case. The deciding mechanism here is that canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
Question 733
A streaming startup wants to expose a new recommendation API to a small slice of traffic first. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule. This is the relevant test because canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
Incorrect Answers
This check would help evaluate the distinct objective “Use labels and selectors to connect resources predictably”, but not the required result. For this case, in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
This check would help evaluate the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”, but not the required result. For this case, in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
This check would help evaluate the distinct objective “Configure Deployment rolling updates with availability safeguards”, but not the required result. For this case, in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
Question 734
A streaming startup wants to expose a new recommendation API to a small slice of traffic first. The team suggests: “Change a Deployment image and label it a canary without controlling which requests reach new versus old Pods.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The observed rollout may expose far more users than intended because percentage routing was never configured. The shortcut creates this risk because canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
Incorrect Answers
That outcome concerns the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”; it is not the most direct consequence of this shortcut. The relevant consequence is that the observed rollout may expose far more users than intended because percentage routing was never configured.
That outcome concerns the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”; it is not the most direct consequence of this shortcut. The relevant consequence is that the observed rollout may expose far more users than intended because percentage routing was never configured.
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 the observed rollout may expose far more users than intended because percentage routing was never configured.
Question 735
A streaming startup wants to expose a new recommendation API to a small slice of traffic first. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
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. This pairing is justified because canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
Incorrect Answers
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 route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Its confirming test is to in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
This action and check address the distinct objective “Use kubectl logs and previous container logs to isolate application crashes” instead of the stated acceptance requirement. The matching action is to route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Its confirming test is to in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
This action and check address the distinct objective “Understand ports, targetPort and protocol mapping in a Service” instead of the stated acceptance requirement. The matching action is to route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Its confirming test is to in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
Question 736
A municipal payments team prepares a fully tested alternate release and wants controlled cutover with rollback. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
The situation is that a municipal payments team prepares a fully tested alternate release and wants controlled cutover with rollback. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. This resolves the issue because canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update. To verify, in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
Incorrect Answers
This option addresses the distinct objective “Externalize application configuration from an image while protecting secrets”, not the immediate requirement. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. For the stated case, canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
This option addresses the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, not the immediate requirement. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects. For the stated case, canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
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, canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
Question 737
A municipal payments team prepares a fully tested alternate release and wants controlled cutover with rollback. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
The situation is that a municipal payments team prepares a fully tested alternate release and wants controlled cutover with rollback. Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update. It supports this action: Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. To confirm, in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
Incorrect Answers
That statement explains the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” rather than the cause in this case. The deciding mechanism here is that canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
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 canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
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 canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
Question 738
A municipal payments team prepares a fully tested alternate release and wants controlled cutover with rollback. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
The situation is that a municipal payments team prepares a fully tested alternate release and wants controlled cutover with rollback. In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule. This is the relevant test because canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
Incorrect Answers
This check would help evaluate the distinct objective “Externalize application configuration from an image while protecting secrets”, but not the required result. For this case, in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
This check would help evaluate the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability”, but not the required result. For this case, in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
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, in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
Question 739
A municipal payments team prepares a fully tested alternate release and wants controlled cutover with rollback. A shortcut is proposed: “Change a Deployment image and label it a canary without controlling which requests reach new versus old Pods.” Which technical consequence follows most closely?
Explanation
Correct Answer
The situation is that a municipal payments team prepares a fully tested alternate release and wants controlled cutover with rollback. The observed rollout may expose far more users than intended because percentage routing was never configured. The shortcut creates this risk because canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
Incorrect Answers
That outcome concerns the distinct objective “Design a release rollback trigger from measurable service signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that the observed rollout may expose far more users than intended because percentage routing was never configured.
That outcome concerns the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”; it is not the most direct consequence of this shortcut. The relevant consequence is that the observed rollout may expose far more users than intended because percentage routing was never configured.
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 the observed rollout may expose far more users than intended because percentage routing was never configured.
Question 740
A municipal payments team prepares a fully tested alternate release and wants controlled cutover with rollback. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
The situation is that a municipal payments team prepares a fully tested alternate release and wants controlled cutover with rollback. 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. This pairing is justified because canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
Incorrect Answers
This action and check address the distinct objective “Configure Deployment rolling updates with availability safeguards” instead of the stated acceptance requirement. The matching action is to route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Its confirming test is to in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
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 route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Its confirming test is to in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
This action and check address the distinct objective “Recognize the kubelet role in local Pod lifecycle management” instead of the stated acceptance requirement. The matching action is to route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Its confirming test is to in a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 76 - 10 Questions (Last Reviewed 02-Nov-2026)