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 57

Question 560

A university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. What pair of supported action and practical verification should be approved?

  1. 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.
  2. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Acceptance evidence: Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.
  3. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Acceptance evidence: Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
  4. Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Acceptance evidence: With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.

Explanation

Correct Answer

B:

The situation is that a university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Acceptance evidence: Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed. This pairing is justified because networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Incorrect Answers

A:

This action and check address the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts” instead of the stated acceptance requirement. The matching action is to combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

C:

This action and check address the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” instead of the stated acceptance requirement. The matching action is to combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

D:

This action and check address the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” instead of the stated acceptance requirement. The matching action is to combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Question 561

A municipal platform validates vendor containers before moving them into production. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience.
  2. Require approved image registries, signature or digest verification and patch ownership when admitting production container images.
  3. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers.
  4. Use a ClusterRole for cluster-scoped resources or reusable rule definitions, recognizing that a RoleBinding to a ClusterRole grants those rules only in one namespace for namespaced resources.

Explanation

Correct Answer

B:

Require approved image registries, signature or digest verification and patch ownership when admitting production container images. This resolves the issue because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. To verify, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Incorrect Answers

A:

This option addresses the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, not the immediate requirement. TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute. For the stated case, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

C:

This option addresses the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, not the immediate requirement. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. For the stated case, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

D:

This option addresses the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, not the immediate requirement. ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole. For the stated case, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Question 562

A municipal platform validates vendor containers before moving them into production. Which platform mechanism explains why the suitable approach works?

  1. TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
  2. A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
  3. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
  4. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.

Explanation

Correct Answer

C:

Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. It supports this action: Require approved image registries, signature or digest verification and patch ownership when admitting production container images. To confirm, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Incorrect Answers

A:

That statement explains the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” rather than the cause in this case. The deciding mechanism here is that image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

B:

That statement explains the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” rather than the cause in this case. The deciding mechanism here is that image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

D:

That statement explains the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” rather than the cause in this case. The deciding mechanism here is that image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Question 563

A municipal platform validates vendor containers before moving them into production. Which controlled observation would best validate the intended improvement?

  1. Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  2. Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
  3. Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
  4. Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

Explanation

Correct Answer

B:

Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results. This is the relevant test because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

C:

This check would help evaluate the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

D:

This check would help evaluate the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Question 564

A municipal platform validates vendor containers before moving them into production. An engineer proposes: “Permit unsigned images from any public registry because container isolation makes supply-chain review unnecessary.” What adverse outcome would be most direct?

  1. Teams can share unintended network and resource access while administrators believe the naming boundary is protective.
  2. The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.
  3. An untrusted dependency or replaced tag can run within otherwise well-configured Pods.
  4. The route remains nonfunctional because nothing reconciles it into an application traffic proxy.

Explanation

Correct Answer

C:

An untrusted dependency or replaced tag can run within otherwise well-configured Pods. The shortcut creates this risk because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Incorrect Answers

A:

That outcome concerns the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.

B:

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 an untrusted dependency or replaced tag can run within otherwise well-configured Pods.

D:

That outcome concerns the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.

Question 565

A municipal platform validates vendor containers before moving them into production. What pair of supported action and practical verification should be approved?

  1. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Acceptance evidence: Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  2. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Acceptance evidence: Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  3. Require approved image registries, signature or digest verification and patch ownership when admitting production container images. Acceptance evidence: Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
  4. Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Acceptance evidence: With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.

Explanation

Correct Answer

C:

Require approved image registries, signature or digest verification and patch ownership when admitting production container images. Acceptance evidence: Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results. This pairing is justified because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Incorrect Answers

A:

This action and check address the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

B:

This action and check address the distinct objective “Use Pods as the shared network and storage execution unit” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

D:

This action and check address the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Question 566

A hospital discovers that a third-party image tag was changed after its release approval. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code.
  2. Require approved image registries, signature or digest verification and patch ownership when admitting production container images.
  3. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate.
  4. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected.

Explanation

Correct Answer

B:

The situation is that a hospital discovers that a third-party image tag was changed after its release approval. Require approved image registries, signature or digest verification and patch ownership when admitting production container images. This resolves the issue because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. To verify, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Incorrect Answers

A:

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, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

C:

This option addresses the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, not the immediate requirement. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. For the stated case, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

D:

This option addresses the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, not the immediate requirement. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. For the stated case, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Question 567

A hospital discovers that a third-party image tag was changed after its release approval. Which causal explanation supports the intended design choice?

  1. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
  2. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
  3. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.
  4. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Explanation

Correct Answer

B:

The situation is that a hospital discovers that a third-party image tag was changed after its release approval. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. It supports this action: Require approved image registries, signature or digest verification and patch ownership when admitting production container images. To confirm, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Incorrect Answers

A:

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 image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

C:

That statement explains the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations” rather than the cause in this case. The deciding mechanism here is that image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

D:

That statement explains the distinct objective “Explain desired state versus observed status in Kubernetes objects” rather than the cause in this case. The deciding mechanism here is that image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Question 568

A hospital discovers that a third-party image tag was changed after its release approval. Which test provides the strongest evidence of a correct implementation?

  1. Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  2. Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  3. Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
  4. Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Explanation

Correct Answer

D:

The situation is that a hospital discovers that a third-party image tag was changed after its release approval. Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results. This is the relevant test because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Incorrect Answers

A:

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, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

B:

This check would help evaluate the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

C:

This check would help evaluate the distinct objective “Distinguish preferred node affinity from required scheduling rules”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Question 569

A hospital discovers that a third-party image tag was changed after its release approval. A shortcut is proposed: “Permit unsigned images from any public registry because container isolation makes supply-chain review unnecessary.” Which technical consequence follows most closely?

  1. Clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
  2. An untrusted dependency or replaced tag can run within otherwise well-configured Pods.
  3. Teams can share unintended network and resource access while administrators believe the naming boundary is protective.
  4. A single node failure can take down all replicas despite a desired count greater than one.

Explanation

Correct Answer

B:

The situation is that a hospital discovers that a third-party image tag was changed after its release approval. An untrusted dependency or replaced tag can run within otherwise well-configured Pods. The shortcut creates this risk because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Incorrect Answers

A:

That outcome concerns the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.

C:

The situation is that a hospital discovers that a third-party image tag was changed after its release approval. That outcome concerns the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.

D:

That outcome concerns the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.

Question 570

A hospital discovers that a third-party image tag was changed after its release approval. Which combined solution and independent check are most directly justified?

  1. Require approved image registries, signature or digest verification and patch ownership when admitting production container images. Acceptance evidence: Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
  2. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Acceptance evidence: Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
  3. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Acceptance evidence: Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
  4. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Acceptance evidence: Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Explanation

Correct Answer

A:

The situation is that a hospital discovers that a third-party image tag was changed after its release approval. Require approved image registries, signature or digest verification and patch ownership when admitting production container images. Acceptance evidence: Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results. This pairing is justified because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Incorrect Answers

B:

This action and check address the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

C:

This action and check address the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

D:

This action and check address the distinct objective “Use annotations for tool metadata rather than workload selection” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests