After deploying the CrowdStrike Container Sensor on your Kubernetes cluster, you notice that it is only monitoring a subset of your containers. Which of the following is the most likely cause of…

Question

Options

• AThe containers were created using privileged mode.
• BThe CrowdStrike Container Sensor pod is not running on every node in the cluster.
• CNetwork policies within the Kubernetes cluster are blocking outbound traffic from the sensor.
• DThe CrowdStrike Falcon Console account does not have the appropriate role permissions to view

• A
  15% (2)
• B
  54% (7)
• C
  23% (3)
• D
  8% (1)

Explanation

Option A: The CrowdStrike Container Sensor is designed to monitor both privileged and unprivileged containers. Privileged mode is not a factor that would prevent the sensor from monitoring containers. Option B: For the CrowdStrike Container Sensor to monitor all containers, it must be deployed on every node in the Kubernetes cluster where containers are running. This ensures that the sensor can collect data from all workloads on those nodes. If the sensor pod is not deployed on certain nodes, containers on those nodes will not be monitored. Option C: Network policies might prevent telemetry data from reaching the CrowdStrike Falcon Console, but this would result in missing data for all containers, not just a subset. Option D: Permissions in the Falcon Console govern what data can be viewed, but they do not impact what the sensor itself monitors.

No community discussion yet for this question.