Practice Exams:

Linux Foundation KCNA Dumps

EXAM: Kubernetes and Cloud Native Associate
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

KCNA Premium Bundle


  • Premium File 333 Questions & Answers
  • Training Course 54 Lectures
  • Study Guide 410 Pages

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?

  1. 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.
  2. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup. Acceptance evidence: Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.
  3. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API. Acceptance evidence: Describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events.
  4. 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement.
  2. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped.
  3. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism.
  4. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
  2. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.
  3. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
  4. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
  2. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  3. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  4. In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. An urgent fix is applied to only one environment and configuration drift grows difficult to audit.
  2. The change is repeatedly reverted, making incident response and audit history inconsistent.
  3. The operator can interrupt healthy networking while the original admission or image problem persists.
  4. The command can mutate production objects although the operator intended a disposable laboratory cluster.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. 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.
  2. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Acceptance evidence: List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
  3. 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.
  4. 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.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped.
  2. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads.
  3. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code.
  4. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.
  2. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
  3. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
  4. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
  2. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  3. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  4. Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. The change is repeatedly reverted, making incident response and audit history inconsistent.
  2. The replacement also fails while operators lack the information needed to identify the application error.
  3. Compromised credentials can perform widespread cluster changes without attribution or least privilege.
  4. Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. 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.
  2. 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.
  3. 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.
  4. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Acceptance evidence: Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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