KCSA · Domain 6: Compliance and Security Frameworks · 10% of the exam
Task 6.4: Automation and Tooling
Automating security checks: policy as code, scanners in CI, admission policies and continuous compliance in the cluster.
Study it
Automation and tooling
Lesson coming
Sample questions
Try each one before opening the answer. Every option is explained, with the CNCF documentation page that proves it.
Question 1 · choose 1
A company wants to write its policies once and evaluate them in several places: Kubernetes admission, authorization checks inside its own microservices and checks in CI. Which CNCF project is described as a general-purpose policy engine suited to that?
AFalco
BOpen Policy Agent (OPA)
Ccert-manager
DNotary Project
Show the answer and why
AFalco
Incorrect
Falco is a runtime threat detection engine; it detects suspicious behavior rather than evaluating policies for services and pipelines.
BOpen Policy Agent (OPA)
Correct
CNCF describes OPA as an open source, general-purpose policy engine, so it is not limited to one system such as Kubernetes admission.
Ccert-manager
Incorrect
cert-manager provisions and manages TLS certificates in Kubernetes; it is not a policy engine.
DNotary Project
Incorrect
Notary Project is a CLI tool to sign and verify artifacts, not a policy engine.
Policy as code lets the same rules be applied automatically wherever decisions are made. OPA is the CNCF project described as a general-purpose policy engine, which suits policies shared by admission control, service authorization and CI checks.
Which project does the Kubernetes security checklist mention as making it easier to manage and use seccomp profiles in clusters?
Acert-manager
BThe Konnectivity service proxy
CSecurity Profiles Operator
Dkube-proxy
Show the answer and why
Acert-manager
Incorrect
cert-manager manages TLS certificates.
BThe Konnectivity service proxy
Incorrect
Konnectivity proxies control plane to node traffic.
CSecurity Profiles Operator
Correct
The checklist says the Kubernetes Security Profiles Operator is a project that facilitates the management and use of seccomp in clusters.
Dkube-proxy
Incorrect
kube-proxy implements Services on nodes.
Managing seccomp profiles on every node by hand does not scale. The checklist points to the Security Profiles Operator to automate distributing and applying them.
Root cause analysis shows that a security misconfiguration, such as a wrong firewall rule, is likely to recur. What does the CNCF Cloud Native Security Whitepaper recommend?
AAdd the fix to a wiki page so that operators remember it
BReview the rule manually once a year
CWrite an automated test that prevents the regression
DDisable the firewall to avoid misconfigurations
Show the answer and why
AAdd the fix to a wiki page so that operators remember it
Incorrect
Documentation alone does not catch the defect when it comes back.
BReview the rule manually once a year
Incorrect
A yearly review leaves long gaps; an automated test runs with every change.
CWrite an automated test that prevents the regression
Correct
The whitepaper says developers should write an automated test to prevent regression of the defect when it has a reasonable chance of recurring.
DDisable the firewall to avoid misconfigurations
Incorrect
Removing the control is not a fix.
Automated security tests in the pipeline turn a one-time fix into a lasting control: if a later change reintroduces the misconfiguration, the test fails and the team gets feedback before merging.