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 81

Question 800

A college course service needs automated release gates beyond successful container startup. Which combined solution and independent check are most directly justified?

  1. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. Acceptance evidence: Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
  2. 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.
  3. 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.
  4. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Acceptance evidence: In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Explanation

Correct Answer

B:

The situation is that a college course service needs automated release gates beyond successful container startup. 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. This pairing is justified because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Incorrect Answers

A:

This action and check address the distinct objective “Explain metrics, logs and traces as complementary observability signals” instead of the stated acceptance requirement. The matching action is to define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

C:

The situation is that a college course service needs automated release gates beyond successful container startup. 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 define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

D:

This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Question 801

A civic information portal scales up during tax season with CPU-based workload metrics. Which engineering approach is the most appropriate for this cloud-native case?

  1. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement.
  2. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas.
  3. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application.
  4. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing.

Explanation

Correct Answer

B:

Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. This resolves the issue because HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself. To verify, generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

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, HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

C:

This option addresses the distinct objective “Define secure release governance with staged approvals and policy verification”, not the immediate requirement. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production. For the stated case, HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

D:

This option addresses the distinct objective “Investigate readiness failures separately from liveness-related restarts”, not the immediate requirement. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. For the stated case, HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Question 802

A civic information portal scales up during tax season with CPU-based workload metrics. What infrastructure principle makes the correct treatment effective?

  1. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.
  2. HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.
  3. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
  4. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Explanation

Correct Answer

B:

HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself. It supports this action: Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. To confirm, generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Incorrect Answers

A:

That statement explains the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” rather than the cause in this case. The deciding mechanism here is that HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

C:

That statement explains the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” rather than the cause in this case. The deciding mechanism here is that HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

D:

That statement explains the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” rather than the cause in this case. The deciding mechanism here is that HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Question 803

A civic information portal scales up during tax season with CPU-based workload metrics. What verification result would most convincingly distinguish a working solution from a claim?

  1. Set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
  2. Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.
  3. Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  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

C:

Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits. This is the relevant test because HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, but not the required result. For this case, generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

B:

This check would help evaluate the distinct objective “Configure Deployment rolling updates with availability safeguards”, but not the required result. For this case, generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

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, generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Question 804

A civic information portal scales up during tax season with CPU-based workload metrics. The change review contains this proposal: “Set the HPA maximum to 50 in a cluster with no additional node capacity and declare scaling guaranteed.” What risk matters most?

  1. The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.
  2. The change is repeatedly reverted, making incident response and audit history inconsistent.
  3. New Pods can remain Pending even when the controller increases desired replica count.
  4. The application never becomes operational because packaging metadata is confused with cluster reconciliation.

Explanation

Correct Answer

C:

New Pods can remain Pending even when the controller increases desired replica count. The shortcut creates this risk because HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use SLI and SLO measures to focus reliability objectives”; it is not the most direct consequence of this shortcut. The relevant consequence is that new Pods can remain Pending even when the controller increases desired replica count.

B:

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 new Pods can remain Pending even when the controller increases desired replica count.

D:

That outcome concerns the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”; it is not the most direct consequence of this shortcut. The relevant consequence is that new Pods can remain Pending even when the controller increases desired replica count.

Question 805

A civic information portal scales up during tax season with CPU-based workload metrics. Which implementation together with matching acceptance evidence best meets this case?

  1. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Acceptance evidence: Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
  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. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. Acceptance evidence: Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  4. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Acceptance evidence: Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Explanation

Correct Answer

D:

Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Acceptance evidence: Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits. This pairing is justified because HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Incorrect Answers

A:

This action and check address the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” instead of the stated acceptance requirement. The matching action is to configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Its confirming test is to generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

B:

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 configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Its confirming test is to generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

C:

This action and check address the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers” instead of the stated acceptance requirement. The matching action is to configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Its confirming test is to generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Question 806

A retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. Which engineering approach is the most appropriate for this cloud-native case?

  1. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team.
  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 an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas.
  4. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism.

Explanation

Correct Answer

C:

The situation is that a retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. This resolves the issue because HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself. To verify, generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Incorrect Answers

A:

This option addresses the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, not the immediate requirement. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. For the stated case, HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

B:

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, HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

D:

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, HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Question 807

A retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. What infrastructure principle makes the correct treatment effective?

  1. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.
  2. 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.
  3. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
  4. HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Explanation

Correct Answer

D:

The situation is that a retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself. It supports this action: Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. To confirm, generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Incorrect Answers

A:

The situation is that a retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. That statement explains the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” rather than the cause in this case. The deciding mechanism here is that HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

B:

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 HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

C:

That statement explains the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” rather than the cause in this case. The deciding mechanism here is that HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Question 808

A retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. What verification result would most convincingly distinguish a working solution from a claim?

  1. Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.
  2. Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.
  3. Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
  4. Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Explanation

Correct Answer

D:

The situation is that a retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits. This is the relevant test because HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Incorrect Answers

A:

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, generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

B:

This check would help evaluate the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”, but not the required result. For this case, generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

C:

This check would help evaluate the distinct objective “Distinguish a container image from a running container and its writable layer”, but not the required result. For this case, generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Question 809

A retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. The change review contains this proposal: “Set the HPA maximum to 50 in a cluster with no additional node capacity and declare scaling guaranteed.” What risk matters most?

  1. Untrusted images or privileged settings can enter production without an auditable approval decision.
  2. Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
  3. New Pods can remain Pending even when the controller increases desired replica count.
  4. Compromised credentials can perform widespread cluster changes without attribution or least privilege.

Explanation

Correct Answer

C:

The situation is that a retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. New Pods can remain Pending even when the controller increases desired replica count. The shortcut creates this risk because HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Incorrect Answers

A:

That outcome concerns the distinct objective “Define secure release governance with staged approvals and policy verification”; it is not the most direct consequence of this shortcut. The relevant consequence is that new Pods can remain Pending even when the controller increases desired replica count.

B:

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 new Pods can remain Pending even when the controller increases desired replica count.

D:

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 new Pods can remain Pending even when the controller increases desired replica count.

Question 810

A retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. Which implementation together with matching acceptance evidence best meets this case?

  1. 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.
  2. 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.
  3. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. Acceptance evidence: Deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.
  4. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Acceptance evidence: Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Explanation

Correct Answer

D:

The situation is that a retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Acceptance evidence: Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits. This pairing is justified because HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Incorrect Answers

A:

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 configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Its confirming test is to generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

B:

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 configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Its confirming test is to generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

C:

This action and check address the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” instead of the stated acceptance requirement. The matching action is to configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Its confirming test is to generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests