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 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?

  1. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  2. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Acceptance evidence: Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
  3. 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.
  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

C:

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

A:

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.

B:

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.

D:

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?

  1. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement.
  2. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller.
  3. Configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization.
  4. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads.

Explanation

Correct Answer

B:

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

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, 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.

C:

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.

D:

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?

  1. 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.
  2. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings.
  3. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.
  4. 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  2. Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
  3. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
  4. Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. The Pod continues restarting because Service DNS configuration is not the cause of the process exit.
  2. The observed rollout may expose far more users than intended because percentage routing was never configured.
  3. DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
  4. New Pods can remain Pending even when the controller increases desired replica count.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. 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.
  2. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Acceptance evidence: Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.
  3. 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.
  4. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. Acceptance evidence: Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.

Explanation

Correct Answer

C:

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 “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.

B:

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.

D:

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?

  1. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image.
  2. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security.
  3. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped.
  4. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller.

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. 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

A:

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.

B:

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.

C:

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?

  1. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.
  2. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.
  3. 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.
  4. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.

Explanation

Correct Answer

C:

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

A:

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.

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 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.

D:

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?

  1. In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  2. Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
  3. Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  4. In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
  2. The command can mutate production objects although the operator intended a disposable laboratory cluster.
  3. The production binary can differ from the validated image even though the release version label matches.
  4. The observed rollout may expose far more users than intended because percentage routing was never configured.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests