Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CrowdStrike CCCS-203b Exam - Topic 4 Question 14 Discussion

You want to block privileged containers from being executed in your Kubernetes cluster.What sensor type should you deploy?
D) Kubernetes Admission Controller To block privileged containers before they are executed, CrowdStrike recommends deploying the Kubernetes Admission Controller. This component operates at admission time, intercepting Kubernetes API requests and enforcing security policies before workloads are allowed to run. Privileged containers represent a significant security risk because they can bypass isolation boundaries and access host resources. The Kubernetes Admission Controller can enforce policies that explicitly deny deployments using privileged flags, hostPath mounts, or other high-risk configurations. Other options do not provide enforcement. Runtime sensors and agents can detect or alert on risky behavior after execution, but they cannot prevent the workload from starting. Image assessment evaluates image content but does not enforce Kubernetes runtime constraints. Therefore, to proactively block privileged containers, the correct and CrowdStrike-recommended solution is the Kubernetes Admission Controller.
A) Kubernetes Protection Agent
B) Kubernetes Sensor
C) Kubernetes Image Assessment at Runtime

CrowdStrike CCCS-203b Exam - Topic 4 Question 14 Discussion

Actual exam question for CrowdStrike's CCCS-203b exam
Question #: 14
Topic #: 4
[All CCCS-203b Questions]

You want to block privileged containers from being executed in your Kubernetes cluster.

What sensor type should you deploy?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Wilson
4 days ago
Yup, blocking those risky configs is a must!
upvoted 0 times
...
Johanna
9 days ago
Wait, are we sure the Admission Controller is foolproof?
upvoted 0 times
...
Latrice
14 days ago
Makes sense, can't have those privileged containers running wild.
upvoted 0 times
...
Ronna
19 days ago
I thought the Kubernetes Protection Agent was the way to go?
upvoted 0 times
...
Latricia
24 days ago
Definitely the Kubernetes Admission Controller!
upvoted 0 times
...
Ruthann
30 days ago
I thought the Kubernetes Protection Agent might be relevant, but now I’m leaning towards the Admission Controller based on what I studied.
upvoted 0 times
...
Loren
1 month ago
I practiced a similar question, and I believe the Admission Controller was highlighted as the best option for preventing privileged containers.
upvoted 0 times
...
Hyun
1 month ago
I’m not entirely sure, but I remember something about the Admission Controller being crucial for blocking certain configurations.
upvoted 0 times
...
Matthew
2 months ago
I think the Kubernetes Admission Controller is the right choice since it can enforce policies before the containers run.
upvoted 0 times
...

Save Cancel