CCCS-203B · Question #147
A security team is deploying CrowdStrike Falcon Cloud Workload Protection to secure containerized workloads. During a security audit, they discover that despite deploying the agent correctly, some con
The correct answer is D. The Falcon Sensor was installed on the host but not configured for container visibility.. Option A: While hardware requirements can affect sensor performance, they do not selectively disable monitoring for specific containers. Option B: While internet connectivity is required for full functionality (such as telemetry reporting and policy updates), the sensor can still
Question
A security team is deploying CrowdStrike Falcon Cloud Workload Protection to secure containerized workloads. During a security audit, they discover that despite deploying the agent correctly, some containers are running without being monitored. Which of the following is the most likely misconfiguration causing this issue?
Options
- AThe host machine does not meet the minimum hardware requirements for Falcon Sensor
- BThe Kubernetes cluster lacks internet connectivity to communicate with the Falcon Cloud.
- CThe Falcon Sensor version does not support containerized environments.
- DThe Falcon Sensor was installed on the host but not configured for container visibility.
How the community answered
(36 responses)- A8% (3)
- B3% (1)
- C11% (4)
- D78% (28)
Explanation
Option A: While hardware requirements can affect sensor performance, they do not selectively disable monitoring for specific containers. Option B: While internet connectivity is required for full functionality (such as telemetry reporting and policy updates), the sensor can still provide local runtime protection based on pre-configured Option C: While older versions may have limited support, CrowdStrike Falcon does support containerized workloads. If the sensor was deployed recently, it is likely a configuration issue rather than an unsupported environment. Option D: CrowdStrike Falcon uses kernel-level hooks to monitor container activity, but proper configuration is required to ensure visibility into containerized workloads. If the agent is installed on the host but not set up for container monitoring, it might not attach correctly to containerized environments, leaving workloads unprotected.
Topics
Community Discussion
No community discussion yet for this question.