3.7 Explain the Deployment of Kubernetes Connectors CLOUD-SECURITY-ENGINEER Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   Which of the following is a common method for installing a Kubernetes connector in Prisma Cloud?

   • AUsing the Kubernetes dashboard to upload the connector binary.
   • BUsing the Prisma Cloud API to push the connector directly to the cluster.
   • CUsing the kubectl apply command with a YAML manifest.
   • DUsing the Azure CLI to deploy the connector as an Azure resource.
   Reveal Solution Discussion Select an answer first
2. 7expert · medium

   A Kubernetes connector is deployed in a cluster that uses a NetworkPolicy to restrict egress traffic. The connector's pod is running, but it cannot connect to the API server. The team has verified that the API server is reachable from other pods in the same namespace. What is the most likely cause?

   • AThe NetworkPolicy does not allow egress traffic from the connector's pod to the API server's IP and port.
   • BThe API server endpoint is configured with the wrong port.
   • CThe connector's service account token is invalid.
   • DThe connector's pod is not running in the same namespace as the NetworkPolicy.
   Reveal Solution Discussion Select an answer first
4. 8expert · medium

   A team is deploying a Kubernetes connector to a cluster that is behind a corporate firewall. The firewall only allows outbound traffic on port 443 to a specific proxy. The connector's Helm chart is configured to use the proxy for outbound traffic. However, the connector still fails to connect to the API server. What is the most likely cause?

   • AThe connector's pod is not running in the same namespace as the proxy.
   • BThe connector is using the wrong service account token.
   • CThe proxy is not configured to allow traffic to the API server's IP and port.
   • DThe connector is configured with the wrong API server port (e.g., 8080 instead of 6443).
   Reveal Solution Discussion Select an answer first
5. 9expert · medium

   A Kubernetes connector is configured to use a service account token for authentication. The token is valid and the RBAC permissions are correct. However, the connector fails to connect with a `401 Unauthorized` error. The team has verified that the token works when used with `kubectl`. What is the most likely cause?

   • AThe connector's pod is not running in the same namespace as the service account.
   • BThe connector is sending the token in the wrong HTTP header.
   • CThe connector is using the wrong API server endpoint (e.g., HTTP instead of HTTPS).
   • DThe connector is configured with the wrong cluster name in its kubeconfig.
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   Which command can be used to check the status of a Kubernetes connector's pods?

   • Akubectl get nodes
   • Bkubectl get pods -n <namespace>
   • Ckubectl get services -n <namespace>
   • Dkubectl get configmaps -n <namespace>
   Reveal Solution Discussion Select an answer first