Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 75
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.
Question 741
A nonprofit platform team wants Git to be the recorded source of truth for Kubernetes service manifests. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. This resolves the issue because gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. To verify, change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
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, gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
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, gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
This option addresses the distinct objective “Identify reconciliation work performed by kube-controller-manager”, not the immediate requirement. The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state. For the stated case, gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
Question 742
A nonprofit platform team wants Git to be the recorded source of truth for Kubernetes service manifests. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. It supports this action: Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. To confirm, change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
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 gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
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 gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
That statement explains the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership” rather than the cause in this case. The deciding mechanism here is that gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
Question 743
A nonprofit platform team wants Git to be the recorded source of truth for Kubernetes service manifests. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value. This is the relevant test because gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
Incorrect Answers
This check would help evaluate the distinct objective “Instrument services with OpenTelemetry context propagation”, but not the required result. For this case, change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
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, change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
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, change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
Question 744
A nonprofit platform team wants Git to be the recorded source of truth for Kubernetes service manifests. An engineer proposes: “Emergency-edit live production Deployments indefinitely while the GitOps controller still enforces an older repository state.” What adverse outcome would be most direct?
Explanation
Correct Answer
The change is repeatedly reverted, making incident response and audit history inconsistent. The shortcut creates this risk because gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
Incorrect Answers
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 the change is repeatedly reverted, making incident response and audit history inconsistent.
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 the change is repeatedly reverted, making incident response and audit history inconsistent.
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 change is repeatedly reverted, making incident response and audit history inconsistent.
Question 745
A nonprofit platform team wants Git to be the recorded source of truth for Kubernetes service manifests. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Acceptance evidence: Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value. This pairing is justified because gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
Incorrect Answers
This action and check address the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership” instead of the stated acceptance requirement. The matching action is to store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Its confirming test is to change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
This action and check address the distinct objective “Design a release rollback trigger from measurable service signals” instead of the stated acceptance requirement. The matching action is to store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Its confirming test is to change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
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 store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Its confirming test is to change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
Question 746
A retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
The situation is that a retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. This resolves the issue because gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. To verify, change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
Incorrect Answers
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, gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
This option addresses the distinct objective “Use Events and pod describe for failed volume mounting”, not the immediate requirement. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. For the stated case, gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
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, gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
Question 747
A retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The situation is that a retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. It supports this action: Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. To confirm, change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
Incorrect Answers
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 gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
That statement explains the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees” rather than the cause in this case. The deciding mechanism here is that gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
That statement explains the distinct objective “Define secure release governance with staged approvals and policy verification” rather than the cause in this case. The deciding mechanism here is that gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
Question 748
A retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
The situation is that a retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value. This is the relevant test because gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
Incorrect Answers
This check would help evaluate the distinct objective “Distinguish etcd persistence from running workload data”, but not the required result. For this case, change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
The situation is that a retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. 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, change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
This check would help evaluate the distinct objective “Separate CI build verification from CD environment promotion”, but not the required result. For this case, change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
Question 749
A retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. An engineer proposes: “Emergency-edit live production Deployments indefinitely while the GitOps controller still enforces an older repository state.” What adverse outcome would be most direct?
Explanation
Correct Answer
The situation is that a retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. The change is repeatedly reverted, making incident response and audit history inconsistent. The shortcut creates this risk because gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
Incorrect Answers
That outcome concerns the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the change is repeatedly reverted, making incident response and audit history inconsistent.
That outcome concerns the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the change is repeatedly reverted, making incident response and audit history inconsistent.
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 change is repeatedly reverted, making incident response and audit history inconsistent.
Question 750
A retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Acceptance evidence: Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value. This pairing is justified because gitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
Incorrect Answers
The situation is that a retailer notices that manual kubectl changes vanish when its Argo CD reconciler runs. This action and check address the distinct objective “Design a release rollback trigger from measurable service signals” instead of the stated acceptance requirement. The matching action is to store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Its confirming test is to change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
This action and check address the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” instead of the stated acceptance requirement. The matching action is to store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Its confirming test is to change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
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 store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Its confirming test is to change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 77 - 10 Questions (Last Reviewed 01-Nov-2026)