While editing an existing Kubernetes Admission Controller policy in Falcon Cloud Security, what change would likely cause a disruption in cluster operations?

Question

Options

• ADeleting an unused Admission Controller policy.
• BChanging the policy to enforce runtime application behavior monitoring.
• CAdding a policy that restricts access to Kubernetes Secrets.
• DModifying the policy to block deployment of containers without defined resource limits.

• A
  12% (7)
• B
  20% (12)
• C
  7% (4)
• D
  62% (37)

Explanation

Option A: Deleting an unused policy has no immediate effect on cluster operations, as it is not actively being enforced. Option B: Admission Controllers do not enforce runtime behavior; this is typically handled by runtime security tools like Kubernetes security policies or host monitoring agents. Option C: Restricting access to Secrets is a valid and recommended security practice but would not directly cause operational disruptions unless misconfigured, such as blocking necessary application Secrets. Option D: Blocking containers without resource limits may disrupt operations if existing deployments do not comply with this new requirement, potentially affecting CI/CD pipelines or existing automation scripts.

No community discussion yet for this question.