Console is running in a Kubernetes cluster, and you need to deploy Defenders on nodes within this cluster. Which option shows the steps to deploy the Defenders in Kubernetes using the default Console

Question

Options

• AFrom the deployment page in Console, choose pod name for Console identifier, generate
• BFrom the deployment page configure the cloud credential in Console and allow cloud discovery to
• CFrom the deployment page in Console, choose twistlock-console for Console identifier, generate
• DFrom the deployment page in Console, choose twistlock-console for Console identifier, and run

• A
  3% (1)
• B
  3% (1)
• C
  92% (33)
• D
  3% (1)

Explanation

When Prisma Cloud (Twistlock) Console is deployed in Kubernetes, the default Kubernetes service name created for it is 'twistlock-console'. When deploying Defenders within the same cluster, you must specify this service name as the Console identifier so Defenders know how to reach Console internally via the cluster's DNS. Option C correctly identifies 'twistlock-console' as the Console identifier and instructs you to generate the DaemonSet deployment YAML from the Console UI. Options A (pod name) is incorrect because pod names are ephemeral and not a stable identifier; options B and D describe incorrect or incomplete workflows.

No community discussion yet for this question.