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 76

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.

Question 751

A transport startup wants the exact tested backend image promoted to its production cluster. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage.
  2. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image.
  3. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism.
  4. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced.

Explanation

Correct Answer

A:

Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. This resolves the issue because continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments. To verify, trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Incorrect Answers

B:

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, continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

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, continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

D:

This option addresses the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, not the immediate requirement. Pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints. For the stated case, continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Question 752

A transport startup wants the exact tested backend image promoted to its production cluster. Which causal explanation supports the intended design choice?

  1. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings.
  2. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
  3. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.
  4. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Explanation

Correct Answer

D:

Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments. It supports this action: Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. To confirm, trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Incorrect Answers

A:

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 continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

B:

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 continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

C:

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 continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Question 753

A transport startup wants the exact tested backend image promoted to its production cluster. Which test provides the strongest evidence of a correct implementation?

  1. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  3. Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.
  4. Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Explanation

Correct Answer

D:

Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records. This is the relevant test because continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

B:

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, trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

C:

This check would help evaluate the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”, but not the required result. For this case, trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Question 754

A transport startup wants the exact tested backend image promoted to its production cluster. A shortcut is proposed: “Rebuild production containers from unreviewed dependency versions instead of promoting the same tested image artifact.” Which technical consequence follows most closely?

  1. The production binary can differ from the validated image even though the release version label matches.
  2. All existing Pods could become unavailable before replacements pass readiness, breaking live requests.
  3. Unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.
  4. The workload gains unnecessary listening services and mutable changes that disappear on replacement.

Explanation

Correct Answer

A:

The production binary can differ from the validated image even though the release version label matches. The shortcut creates this risk because continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Incorrect Answers

B:

That outcome concerns the distinct objective “Configure Deployment rolling updates with availability safeguards”; it is not the most direct consequence of this shortcut. The relevant consequence is that the production binary can differ from the validated image even though the release version label matches.

C:

That outcome concerns the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”; it is not the most direct consequence of this shortcut. The relevant consequence is that the production binary can differ from the validated image even though the release version label matches.

D:

That outcome concerns the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”; it is not the most direct consequence of this shortcut. The relevant consequence is that the production binary can differ from the validated image even though the release version label matches.

Question 755

A transport startup wants the exact tested backend image promoted to its production cluster. Which combined solution and independent check are most directly justified?

  1. Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Acceptance evidence: Compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
  2. 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.
  3. 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.
  4. 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.

Explanation

Correct Answer

B:

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. This pairing is justified because continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Incorrect Answers

A:

This action and check address the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling” instead of the stated acceptance requirement. The matching action is to run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Its confirming test is to trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

C:

This action and check address the distinct objective “Apply GitOps reconciliation with a version-controlled desired state” instead of the stated acceptance requirement. The matching action is to run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Its confirming test is to trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

D:

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 run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Its confirming test is to trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Question 756

An insurance developer believes passing unit tests automatically updates all live services without a delivery step. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods.
  2. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage.
  3. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller.
  4. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement.

Explanation

Correct Answer

B:

The situation is that an insurance developer believes passing unit tests automatically updates all live services without a delivery step. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. This resolves the issue because continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments. To verify, trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Incorrect Answers

A:

This option addresses the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, not the immediate requirement. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. For the stated case, continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

C:

This option addresses the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”, not the immediate requirement. 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. For the stated case, continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

D:

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, continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Question 757

An insurance developer believes passing unit tests automatically updates all live services without a delivery step. Which causal explanation supports the intended design choice?

  1. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.
  2. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.
  3. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.
  4. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Explanation

Correct Answer

B:

The situation is that an insurance developer believes passing unit tests automatically updates all live services without a delivery step. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments. It supports this action: Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. To confirm, trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Incorrect Answers

A:

That statement explains the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” rather than the cause in this case. The deciding mechanism here is that continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

C:

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 continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

D:

That statement explains the distinct objective “Design a release rollback trigger from measurable service signals” rather than the cause in this case. The deciding mechanism here is that continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Question 758

An insurance developer believes passing unit tests automatically updates all live services without a delivery step. Which test provides the strongest evidence of a correct implementation?

  1. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  2. Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.
  3. Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
  4. Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

Explanation

Correct Answer

B:

The situation is that an insurance developer believes passing unit tests automatically updates all live services without a delivery step. Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records. This is the relevant test because continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Define secure release governance with staged approvals and policy verification”, but not the required result. For this case, trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

C:

This check would help evaluate the distinct objective “Use annotations for tool metadata rather than workload selection”, but not the required result. For this case, trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

D:

This check would help evaluate the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”, but not the required result. For this case, trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Question 759

An insurance developer believes passing unit tests automatically updates all live services without a delivery step. A shortcut is proposed: “Rebuild production containers from unreviewed dependency versions instead of promoting the same tested image artifact.” Which technical consequence follows most closely?

  1. New Pods can remain Pending even when the controller increases desired replica count.
  2. A resource can remain Pending indefinitely even while its desired configuration is stored correctly.
  3. The production binary can differ from the validated image even though the release version label matches.
  4. The change is repeatedly reverted, making incident response and audit history inconsistent.

Explanation

Correct Answer

C:

The situation is that an insurance developer believes passing unit tests automatically updates all live services without a delivery step. The production binary can differ from the validated image even though the release version label matches. The shortcut creates this risk because continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Incorrect Answers

A:

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 production binary can differ from the validated image even though the release version label matches.

B:

That outcome concerns the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”; it is not the most direct consequence of this shortcut. The relevant consequence is that the production binary can differ from the validated image even though the release version label matches.

D:

That outcome concerns the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”; it is not the most direct consequence of this shortcut. The relevant consequence is that the production binary can differ from the validated image even though the release version label matches.

Question 760

An insurance developer believes passing unit tests automatically updates all live services without a delivery step. Which combined solution and independent check are most directly justified?

  1. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Acceptance evidence: Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  2. 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.
  3. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Acceptance evidence: Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
  4. 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.

Explanation

Correct Answer

B:

The situation is that an insurance developer believes passing unit tests automatically updates all live services without a delivery step. 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. This pairing is justified because continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Incorrect Answers

A:

This action and check address the distinct objective “Define secure release governance with staged approvals and policy verification” instead of the stated acceptance requirement. The matching action is to run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Its confirming test is to trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

C:

This action and check address the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” instead of the stated acceptance requirement. The matching action is to run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Its confirming test is to trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

D:

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 run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Its confirming test is to trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests