McAfee Secure

CNCF CKA Bundle

Exam Code: CKA

Exam Name Certified Kubernetes Administrator

Certification Provider: CNCF

Corresponding Certification: CKA

CNCF CKA Bundle $44.99
CKA Sample 1 CKA Sample 2 CKA Sample 3 CKA Sample 4 CKA Sample 5 CKA Sample 6 CKA Sample 7 CKA Sample 8 CKA Sample 9 CKA Sample 10

100% CNCF CKA Guaranteed Success With Testking Training Materials

Get Real CKA Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    CKA Questions & Answers

    58 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual CKA exam while allowing you to hone and measure every aspect of your test-taking ability.

  • CKA Video Course

    CKA Training Course

    138 Video Lectures

    CKA Video Course is developed by CNCF Professionals to help you pass the CKA exam.

    Description

    This course will improve your knowledge and skills required to pass Certified Kubernetes Administrator exam.
  • Study Guide

    CKA Study Guide

    268 PDF Pages

    Developed by industry experts, this 268-page guide spells out in painstaking detail all of the information you need to ace CKA exam.

Certified Kubernetes Administrator (CKA) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    58 Questions

    $124.99
  • CKA Video Course

    Training Course

    138 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    268 PDF Pages

    $29.99

CNCF CKA Practice Test 70

Question 690

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing Ingress metrics-ingress in namespace observability needs its TLS host and precreated Secret references applied from reviewed file ./ingress/metrics-api-tls.yaml. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. Services select matching Pods; an unmatched selector can leave EndpointSlices without usable backends despite healthy Pods.
  2. Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates.
  3. A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing.
  4. LoadBalancer Services request external routing from a supported infrastructure controller; a bare cluster does not guarantee an external address.

Explanation

Correct Answer

B:

Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. This explains the stated condition. The corresponding action is: Run kubectl -n observability apply -f ./ingress/metrics-api-tls.yaml after checking secret type and host match. The direct acceptance evidence is: Run kubectl -n observability describe ingress metrics-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test.

Incorrect Answers

A:

Services select matching Pods; an unmatched selector can leave EndpointSlices without usable backends despite healthy Pods. That explanation applies to a different technical failure. Here the controlling principle is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates.

C:

This principle describes a separate cause: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The reported condition is governed by: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The two mechanisms should not be conflated.

D:

LoadBalancer Services request external routing from a supported infrastructure controller; a bare cluster does not guarantee an external address. That explanation applies to a different technical failure. Here the controlling principle is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates.

Question 691

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing Ingress metrics-ingress in namespace observability needs its TLS host and precreated Secret references applied from reviewed file ./ingress/metrics-api-tls.yaml. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n observability get httproute metrics-route -o yaml and inspect parent acceptance and resolved-reference conditions.
  2. Run kubectl -n observability get service metrics-svc and inspect external address assignment plus ready EndpointSlices.
  3. Run kubectl -n observability describe ingress metrics-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test.
  4. Run kubectl -n observability describe networkpolicy metrics-api-deny-egress and test expected blocked destinations.

Explanation

Correct Answer

C:

Run kubectl -n observability describe ingress metrics-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The intended action is: Run kubectl -n observability apply -f ./ingress/metrics-api-tls.yaml after checking secret type and host match.

Incorrect Answers

A:

That test belongs to another control with this basis: Gateway API HTTPRoutes express matching and backend behavior while Gateway resources own compatible listeners. In the current case, the governing reason is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The direct verification is “Run kubectl -n observability describe ingress metrics-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test”.

B:

This observation would test a different technical dependency: LoadBalancer Services request external routing from a supported infrastructure controller; a bare cluster does not guarantee an external address. The current issue is governed by: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. Its decisive check is “Run kubectl -n observability describe ingress metrics-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test”.

D:

That test belongs to another control with this basis: An egress-isolating NetworkPolicy can block Pod outbound connections; DNS and required dependencies need explicit allowances. In the current case, the governing reason is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The direct verification is “Run kubectl -n observability describe ingress metrics-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test”.

Question 692

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing Ingress metrics-ingress in namespace observability needs its TLS host and precreated Secret references applied from reviewed file ./ingress/metrics-api-tls.yaml. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Audit controller capability and exposed service access policies before enabling public ingress.
  2. Prefer short-lived diagnostic tunnels and avoid treating port-forward as a production ingress path.
  3. Test security policies from allowed and denied sources rather than trusting YAML alone.
  4. Track TLS Secret renewal and enforce appropriate ingress-controller security policies.

Explanation

Correct Answer

D:

Track TLS Secret renewal and enforce appropriate ingress-controller security policies. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n observability apply -f ./ingress/metrics-api-tls.yaml after checking secret type and host match. The relevant mechanism is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates.

Incorrect Answers

A:

This routine guards against another mechanism: LoadBalancer Services request external routing from a supported infrastructure controller; a bare cluster does not guarantee an external address. The recurring exposure in the current case is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The matching preventive check is “Track TLS Secret renewal and enforce appropriate ingress-controller security policies”.

B:

The suggested review tracks a different technical risk: Port-forwarding creates a client-side tunnel to a selected backend and does not change the Service type or network exposure. Here the sustained control must address: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. Choose “Track TLS Secret renewal and enforce appropriate ingress-controller security policies”.

C:

That safeguard is relevant to: A selecting NetworkPolicy with ingress isolation and no allow rules denies new ingress to selected Pods except protocol-specific policy behavior; it does not itself control egress. The current failure instead follows from: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. Its prevention measure is “Track TLS Secret renewal and enforce appropriate ingress-controller security policies”.

Question 693

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An existing Ingress dispatch-ingress in namespace fulfillment needs its TLS host and precreated Secret references applied from reviewed file ./ingress/dispatch-api-tls.yaml. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl -n fulfillment apply -f ./gateway/dispatch-api-route.yaml after confirming parentRefs, hostnames and backendRefs.
  2. Run kubectl -n fulfillment apply -f ./ingress/dispatch-api-tls.yaml after checking secret type and host match.
  3. Run kubectl -n ledger apply -f ./policies/invoice-api-deny-ingress.yaml after validating selectors and the CNI's policy enforcement support.
  4. Run kubectl -n fulfillment expose deployment dispatch-api --name=dispatch-svc --type=NodePort --port=9090 --target-port=9000.

Explanation

Correct Answer

B:

Run kubectl -n fulfillment apply -f ./ingress/dispatch-api-tls.yaml after checking secret type and host match. This is the appropriate command-line action or first safe diagnostic. The technical reason is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. Validate the result with: Run kubectl -n fulfillment describe ingress dispatch-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

The proposed action belongs to the mechanism: Gateway API HTTPRoutes express matching and backend behavior while Gateway resources own compatible listeners. Here the stated fault follows a different mechanism: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The corrective choice is “Run kubectl -n fulfillment apply -f ./ingress/dispatch-api-tls.yaml after checking secret type and host match”.

C:

This alternative is a response to another technical cause: A selecting NetworkPolicy with ingress isolation and no allow rules denies new ingress to selected Pods except protocol-specific policy behavior; it does not itself control egress. The reported case instead depends on: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The action that directly addresses it is “Run kubectl -n fulfillment apply -f ./ingress/dispatch-api-tls.yaml after checking secret type and host match”.

D:

The proposed action belongs to the mechanism: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Here the stated fault follows a different mechanism: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The corrective choice is “Run kubectl -n fulfillment apply -f ./ingress/dispatch-api-tls.yaml after checking secret type and host match”.

Question 694

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An existing Ingress dispatch-ingress in namespace fulfillment needs its TLS host and precreated Secret references applied from reviewed file ./ingress/dispatch-api-tls.yaml. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. A selecting NetworkPolicy with ingress isolation and no allow rules denies new ingress to selected Pods except protocol-specific policy behavior; it does not itself control egress.
  2. Port-forwarding creates a client-side tunnel to a selected backend and does not change the Service type or network exposure.
  3. Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates.
  4. A namespaceSelector in a NetworkPolicy ingress peer matches namespace labels; it differs from matching arbitrary Pod labels across namespaces.

Explanation

Correct Answer

C:

Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. This explains the stated condition. The corresponding action is: Run kubectl -n fulfillment apply -f ./ingress/dispatch-api-tls.yaml after checking secret type and host match. The direct acceptance evidence is: Run kubectl -n fulfillment describe ingress dispatch-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test.

Incorrect Answers

A:

The offered statement is true for this other mechanism: A selecting NetworkPolicy with ingress isolation and no allow rules denies new ingress to selected Pods except protocol-specific policy behavior; it does not itself control egress. It does not explain the facts described here, which follow from: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates.

B:

This principle describes a separate cause: Port-forwarding creates a client-side tunnel to a selected backend and does not change the Service type or network exposure. The reported condition is governed by: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The two mechanisms should not be conflated.

D:

The offered statement is true for this other mechanism: A namespaceSelector in a NetworkPolicy ingress peer matches namespace labels; it differs from matching arbitrary Pod labels across namespaces. It does not explain the facts described here, which follow from: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates.

Question 695

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An existing Ingress dispatch-ingress in namespace fulfillment needs its TLS host and precreated Secret references applied from reviewed file ./ingress/dispatch-api-tls.yaml. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run an in-Pod nslookup dispatch-svc.fulfillment.svc.cluster.local and confirm name resolution under isolation.
  2. Run kubectl -n fulfillment get networkpolicy dispatch-api-deny-ingress -o yaml and perform an authorized denied-connection probe.
  3. Run kubectl -n fulfillment describe networkpolicy dispatch-api-deny-egress and test expected blocked destinations.
  4. Run kubectl -n fulfillment describe ingress dispatch-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test.

Explanation

Correct Answer

D:

Run kubectl -n fulfillment describe ingress dispatch-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The intended action is: Run kubectl -n fulfillment apply -f ./ingress/dispatch-api-tls.yaml after checking secret type and host match.

Incorrect Answers

A:

This observation would test a different technical dependency: NetworkPolicy egress rules are additive and DNS lookup requires permitted traffic to the DNS server, not only a correct Service record. The current issue is governed by: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. Its decisive check is “Run kubectl -n fulfillment describe ingress dispatch-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test”.

B:

The alternative verifies a different condition: A selecting NetworkPolicy with ingress isolation and no allow rules denies new ingress to selected Pods except protocol-specific policy behavior; it does not itself control egress. The current case instead depends on: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. Confirm that “Run kubectl -n fulfillment describe ingress dispatch-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test”.

C:

That test belongs to another control with this basis: An egress-isolating NetworkPolicy can block Pod outbound connections; DNS and required dependencies need explicit allowances. In the current case, the governing reason is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The direct verification is “Run kubectl -n fulfillment describe ingress dispatch-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test”.

Question 696

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An existing Ingress dispatch-ingress in namespace fulfillment needs its TLS host and precreated Secret references applied from reviewed file ./ingress/dispatch-api-tls.yaml. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Track TLS Secret renewal and enforce appropriate ingress-controller security policies.
  2. Check exposed Service port mappings against actual container listeners and named ports before releases.
  3. Review ingress class ownership and avoid exposing test applications outside intended environments.
  4. Manage Service selectors and target ports alongside the Deployment labels and container listening port.

Explanation

Correct Answer

A:

Track TLS Secret renewal and enforce appropriate ingress-controller security policies. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n fulfillment apply -f ./ingress/dispatch-api-tls.yaml after checking secret type and host match. The relevant mechanism is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates.

Incorrect Answers

B:

That safeguard is relevant to: The Service port is what clients connect to, while targetPort must reach the actual backend listener. The current failure instead follows from: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. Its prevention measure is “Track TLS Secret renewal and enforce appropriate ingress-controller security policies”.

C:

This routine guards against another mechanism: An Ingress resource declares HTTP host/path routing but requires an actual installed Ingress controller. The recurring exposure in the current case is: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The matching preventive check is “Track TLS Secret renewal and enforce appropriate ingress-controller security policies”.

D:

The suggested review tracks a different technical risk: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. Here the sustained control must address: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. Choose “Track TLS Secret renewal and enforce appropriate ingress-controller security policies”.

Question 697

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: Gateway API CRDs and a suitable controller already exist; create reviewed Gateway internal-gw in ledger from ./gateway/invoice-api-gateway.yaml. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl -n ledger apply -f ./policies/invoice-api-deny-egress.yaml after reviewing impact on DNS and observability.
  2. Run kubectl -n ledger apply -f ./policies/invoice-api-cross-namespace.yaml after confirming its namespaceSelector and TCP port 80.
  3. Run kubectl -n ledger apply -f ./gateway/invoice-api-gateway.yaml after confirming GatewayClass and listener settings.
  4. Run kubectl -n ledger get endpointslices -l kubernetes.io/service-name=invoice-svc -o wide.

Explanation

Correct Answer

C:

Run kubectl -n ledger apply -f ./gateway/invoice-api-gateway.yaml after confirming GatewayClass and listener settings. This is the appropriate command-line action or first safe diagnostic. The technical reason is: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. Validate the result with: Run kubectl -n ledger get gateway internal-gw -o yaml and inspect Accepted and Programmed conditions. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

The offered action targets: An egress-isolating NetworkPolicy can block Pod outbound connections; DNS and required dependencies need explicit allowances. The case facts point instead to: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. Implement “Run kubectl -n ledger apply -f ./gateway/invoice-api-gateway.yaml after confirming GatewayClass and listener settings” to address that specific condition.

B:

This alternative is a response to another technical cause: A namespaceSelector in a NetworkPolicy ingress peer matches namespace labels; it differs from matching arbitrary Pod labels across namespaces. The reported case instead depends on: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. The action that directly addresses it is “Run kubectl -n ledger apply -f ./gateway/invoice-api-gateway.yaml after confirming GatewayClass and listener settings”.

D:

The offered action targets: EndpointSlices represent Service backend addresses and readiness; Service existence alone does not prove endpoints exist. The case facts point instead to: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. Implement “Run kubectl -n ledger apply -f ./gateway/invoice-api-gateway.yaml after confirming GatewayClass and listener settings” to address that specific condition.

Question 698

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: Gateway API CRDs and a suitable controller already exist; create reviewed Gateway internal-gw in ledger from ./gateway/invoice-api-gateway.yaml. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. Cluster DNS should resolve Service names inside its configured domain; host-side DNS results do not prove in-cluster resolution.
  2. A selecting NetworkPolicy with ingress isolation and no allow rules denies new ingress to selected Pods except protocol-specific policy behavior; it does not itself control egress.
  3. An ingress rule with a podSelector selects source Pods in its own namespace unless combined with other peer selectors.
  4. Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support.

Explanation

Correct Answer

D:

Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. This explains the stated condition. The corresponding action is: Run kubectl -n ledger apply -f ./gateway/invoice-api-gateway.yaml after confirming GatewayClass and listener settings. The direct acceptance evidence is: Run kubectl -n ledger get gateway internal-gw -o yaml and inspect Accepted and Programmed conditions.

Incorrect Answers

A:

This principle describes a separate cause: Cluster DNS should resolve Service names inside its configured domain; host-side DNS results do not prove in-cluster resolution. The reported condition is governed by: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. The two mechanisms should not be conflated.

B:

A selecting NetworkPolicy with ingress isolation and no allow rules denies new ingress to selected Pods except protocol-specific policy behavior; it does not itself control egress. That explanation applies to a different technical failure. Here the controlling principle is: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support.

C:

The offered statement is true for this other mechanism: An ingress rule with a podSelector selects source Pods in its own namespace unless combined with other peer selectors. It does not explain the facts described here, which follow from: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support.

Question 699

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: Gateway API CRDs and a suitable controller already exist; create reviewed Gateway internal-gw in ledger from ./gateway/invoice-api-gateway.yaml. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n ledger get gateway internal-gw -o yaml and inspect Accepted and Programmed conditions.
  2. Run kubectl -n ledger describe ingress invoice-ingress and verify its TLS mapping, then perform a certificate-validating HTTPS test.
  3. Run kubectl -n ledger get service invoice-svc and inspect external address assignment plus ready EndpointSlices.
  4. Run kubectl -n fulfillment get httproute dispatch-route -o yaml and inspect parent acceptance and resolved-reference conditions.

Explanation

Correct Answer

A:

Run kubectl -n ledger get gateway internal-gw -o yaml and inspect Accepted and Programmed conditions. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. The intended action is: Run kubectl -n ledger apply -f ./gateway/invoice-api-gateway.yaml after confirming GatewayClass and listener settings.

Incorrect Answers

B:

That test belongs to another control with this basis: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. In the current case, the governing reason is: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. The direct verification is “Run kubectl -n ledger get gateway internal-gw -o yaml and inspect Accepted and Programmed conditions”.

C:

This observation would test a different technical dependency: LoadBalancer Services request external routing from a supported infrastructure controller; a bare cluster does not guarantee an external address. The current issue is governed by: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. Its decisive check is “Run kubectl -n ledger get gateway internal-gw -o yaml and inspect Accepted and Programmed conditions”.

D:

The alternative verifies a different condition: Gateway API HTTPRoutes express matching and backend behavior while Gateway resources own compatible listeners. The current case instead depends on: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. Confirm that “Run kubectl -n ledger get gateway internal-gw -o yaml and inspect Accepted and Programmed conditions”.

Question 700

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: Gateway API CRDs and a suitable controller already exist; create reviewed Gateway internal-gw in ledger from ./gateway/invoice-api-gateway.yaml. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Treat cross-namespace route attachment and backend references as controlled trust boundaries.
  2. Check gateway class/controller compatibility and delegate route attachment privileges deliberately.
  3. Track TLS Secret renewal and enforce appropriate ingress-controller security policies.
  4. Prefer short-lived diagnostic tunnels and avoid treating port-forward as a production ingress path.

Explanation

Correct Answer

B:

Check gateway class/controller compatibility and delegate route attachment privileges deliberately. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n ledger apply -f ./gateway/invoice-api-gateway.yaml after confirming GatewayClass and listener settings. The relevant mechanism is: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support.

Incorrect Answers

A:

That safeguard is relevant to: Gateway API HTTPRoutes express matching and backend behavior while Gateway resources own compatible listeners. The current failure instead follows from: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. Its prevention measure is “Check gateway class/controller compatibility and delegate route attachment privileges deliberately”.

C:

The suggested review tracks a different technical risk: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. Here the sustained control must address: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. Choose “Check gateway class/controller compatibility and delegate route attachment privileges deliberately”.

D:

That safeguard is relevant to: Port-forwarding creates a client-side tunnel to a selected backend and does not change the Service type or network exposure. The current failure instead follows from: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. Its prevention measure is “Check gateway class/controller compatibility and delegate route attachment privileges deliberately”.