- A
Implement network policies to restrict egress from pods to the registry.
Why wrong: Network policies control pod traffic, not image provenance.
- B
Grant registry write access only to the CI system's service account.
Why wrong: This reduces risk but does not prevent the CI itself from being compromised.
- C
Use a static analysis tool to check the Dockerfile before building.
Why wrong: This only checks the build instructions, not the built image.
- D
Use a unique registry path and restrict access via firewall rules.
Why wrong: Firewall rules do not prevent tampered images from being pushed if credentials are compromised.
- E
Generate signed attestations with in-toto during the CI pipeline and verify them using an admission webhook like Kyverno.
Attestations provide non-repudiation and can be verified at admission time.
CKS Supply Chain Security Practice Question
This CKS practice question tests your understanding of supply chain security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An organization uses a private container registry and wants to ensure that only images built from a specific CI/CD pipeline are deployed. Which combination of measures provides the strongest guarantee?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Generate signed attestations with in-toto during the CI pipeline and verify them using an admission webhook like Kyverno.
Option E is correct because it implements a complete chain of custody for container images. In-toto generates signed attestations that record every step of the CI/CD pipeline (e.g., source code checkout, build, test), and an admission webhook like Kyverno verifies these attestations before allowing a pod to run. This ensures that only images that passed the exact, attested pipeline are deployed, providing the strongest guarantee against unauthorized or tampered images.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Implement network policies to restrict egress from pods to the registry.
Why it's wrong here
Network policies control pod traffic, not image provenance.
- ✗
Grant registry write access only to the CI system's service account.
Why it's wrong here
This reduces risk but does not prevent the CI itself from being compromised.
- ✗
Use a static analysis tool to check the Dockerfile before building.
Why it's wrong here
This only checks the build instructions, not the built image.
- ✗
Use a unique registry path and restrict access via firewall rules.
Why it's wrong here
Firewall rules do not prevent tampered images from being pushed if credentials are compromised.
- ✓
Generate signed attestations with in-toto during the CI pipeline and verify them using an admission webhook like Kyverno.
Why this is correct
Attestations provide non-repudiation and can be verified at admission time.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the distinction between access control measures (network policies, RBAC, firewalls) and cryptographic provenance verification; candidates mistakenly think restricting registry access or network egress is sufficient, but the exam emphasizes that only signed attestations with admission control can guarantee the image was built by the intended pipeline.
Detailed technical explanation
How to think about this question
In-toto works by creating a signed link metadata file for each step in the supply chain (e.g., 'step.update' layout), which includes the command run, materials used, and resulting products. Kyverno, as an admission webhook, can use the 'verifyImages' rule to check that the image's attestation matches a trusted public key and that the attestation's predicate (e.g., SLSA Provenance) confirms the pipeline identity. This approach is rooted in the SLSA (Supply-chain Levels for Software Artifacts) framework, specifically achieving SLSA Level 2 or higher by providing non-forgeable provenance.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Supply Chain Security — study guide chapter
Learn the concepts, then practise the questions
- →
Supply Chain Security practice questions
Targeted practice on this topic area only
- →
All CKS questions
997 questions across all exam domains
- →
Certified Kubernetes Security Specialist CKS study guide
Full concept coverage aligned to exam objectives
- →
CKS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CKS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Monitoring Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring Logging and Runtime Security.
Cluster Setup and Hardening practice questions
Practise CKS questions linked to Cluster Setup and Hardening.
System Hardening practice questions
Practise CKS questions linked to System Hardening.
Minimize Microservice Vulnerabilities practice questions
Practise CKS questions linked to Minimize Microservice Vulnerabilities.
Supply Chain Security practice questions
Practise CKS questions linked to Supply Chain Security.
Monitoring, Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring, Logging and Runtime Security.
Cluster Setup practice questions
Practise CKS questions linked to Cluster Setup.
Cluster Hardening practice questions
Practise CKS questions linked to Cluster Hardening.
CKS fundamentals practice questions
Practise CKS questions linked to CKS fundamentals.
CKS scenario practice questions
Practise CKS questions linked to CKS scenario.
CKS troubleshooting practice questions
Practise CKS questions linked to CKS troubleshooting.
Practice this exam
Start a free CKS practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CKS question test?
Supply Chain Security — This question tests Supply Chain Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Generate signed attestations with in-toto during the CI pipeline and verify them using an admission webhook like Kyverno. — Option E is correct because it implements a complete chain of custody for container images. In-toto generates signed attestations that record every step of the CI/CD pipeline (e.g., source code checkout, build, test), and an admission webhook like Kyverno verifies these attestations before allowing a pod to run. This ensures that only images that passed the exact, attested pipeline are deployed, providing the strongest guarantee against unauthorized or tampered images.
What should I do if I get this CKS question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 30, 2026
This CKS practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CKS exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.