- A
clientConfig: service: name: webhook-svc namespace: webhook path: /validate port: 443
This correctly references the service within the cluster.
- B
clientConfig: url: https://10.96.0.1:443/validate
Why wrong: Using hardcoded IP is not recommended due to changes; service DNS is preferred.
- C
clientConfig: url: https://webhook-svc.webhook.svc:443/validate
Why wrong: Using 'url' is possible but not the preferred method; also, the URL scheme should be 'https'.
- D
clientConfig: service: name: webhook-svc namespace: webhook path: /validate caBundle: <base64>
Why wrong: Missing the 'port' field; default is 443 but explicit is better; also caBundle is required but not shown.
Question 676 of 997
ValidatingWebhookConfiguration clientConfig: Service Reference Configuration
This CKS practice question tests your understanding of minimize microservice vulnerabilities. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
You need to set up a ValidatingWebhookConfiguration to deny pods that run as root. The webhook server is deployed in the 'webhook' namespace with service 'webhook-svc' on port 443. Which of the following is a correct snippet for the webhook configuration?
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
✓
clientConfig: service: name: webhook-svc namespace: webhook path: /validate port: 443
Option A is correct because it properly defines a service reference with the required fields: name, namespace, and path. The port field is explicitly set to 443, matching the webhook server's listening port. In Kubernetes, when using a service reference and the webhook server's certificate is signed by the cluster's CA (which is typical for in-cluster services), the caBundle field may be omitted as the API server can use its own CA bundle to verify the connection. Thus, the configuration in A is complete and valid for this scenario.
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.
- ✓
clientConfig: service: name: webhook-svc namespace: webhook path: /validate port: 443
Why this is correct
This correctly references the service within the cluster.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
clientConfig: url: https://10.96.0.1:443/validate
Why it's wrong here
Using hardcoded IP is not recommended due to changes; service DNS is preferred.
- ✗
clientConfig: url: https://webhook-svc.webhook.svc:443/validate
Why it's wrong here
Using 'url' is possible but not the preferred method; also, the URL scheme should be 'https'.
- ✗
clientConfig: service: name: webhook-svc namespace: webhook path: /validate caBundle: <base64>
Why it's wrong here
Missing the 'port' field; default is 443 but explicit is better; also caBundle is required but not shown.
Common exam traps
Common exam trap: answer the scenario, not the keyword
A common pitfall is assuming that a `caBundle` is always mandatory when using a `service` reference. In fact, if the webhook server's certificate is signed by the cluster's CA (as is typical for in-cluster services), the API server can use its own CA bundle, making `caBundle` optional. Another trap is using a raw IP or service DNS name in the `url` field instead of a proper `service` reference, or omitting the `port` field when using a `service` reference.
Trap categories for this question
Command / output trap
Missing the 'port' field; default is 443 but explicit is better; also caBundle is required but not shown.
Detailed technical explanation
How to think about this question
Under the hood, the Kubernetes API server resolves the service reference to the pod IPs via the service's endpoints, and the `caBundle` must contain the base64-encoded CA certificate that signed the webhook server's TLS certificate; without it, the API server cannot establish a trusted HTTPS connection. In real-world scenarios, misconfiguring the `caBundle` or omitting the port can lead to silent failures where the webhook is not called, potentially allowing privileged pods to run undetected.
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 security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
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.
- →
Minimize Microservice Vulnerabilities — study guide chapter
Learn the concepts, then practise the questions
- →
Minimize Microservice Vulnerabilities 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?
Minimize Microservice Vulnerabilities — This question tests Minimize Microservice Vulnerabilities — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: clientConfig: service: name: webhook-svc namespace: webhook path: /validate port: 443 — Option A is correct because it properly defines a service reference with the required fields: name, namespace, and path. The port field is explicitly set to 443, matching the webhook server's listening port. In Kubernetes, when using a service reference and the webhook server's certificate is signed by the cluster's CA (which is typical for in-cluster services), the caBundle field may be omitted as the API server can use its own CA bundle to verify the connection. Thus, the configuration in A is complete and valid for this scenario.
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 →
Same concept, more angles
1 more ways this is tested on CKS
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are deploying a ValidatingWebhookConfiguration. The webhook server is running in the 'webhook' namespace, service name 'svc', port 443. Which clientConfig should you specify?
hard- ✓ A.clientConfig: service: namespace: webhook name: svc path: /validate
- B.clientConfig: url: https://webhook.svc.cluster.local:443/validate
- C.clientConfig: service: namespace: webhook name: webhook path: /validate
- D.clientConfig: service: namespace: default name: svc path: /validate
Why A: Option A is correct because a ValidatingWebhookConfiguration's clientConfig must reference the Kubernetes service that fronts the webhook server, specifying the service's namespace, name, and the path to the validation endpoint. Since the webhook server runs in the 'webhook' namespace with service name 'svc' on port 443, the service reference must use namespace: webhook and name: svc, with path: /validate. Kubernetes automatically resolves the service to its cluster-internal DNS name and uses the service's HTTPS port (443) when a service reference is provided.
Keep practising
More CKS practice questions
- Which flag is used to restrict the kubelet's ability to modify node status and pods?
- A Falco rule has priority `WARNING` and output: `Sensitive file opened (user=%user.name command=%proc.cmdline file=%fd.n…
- Falco detects a shell being opened inside a container. Which Falco rule field is used to specify the syscall condition f…
- A security audit reveals that a ServiceAccount named 'monitor' has a ClusterRoleBinding to the cluster-admin role. What…
- Match each Kubernetes security component to its description.
- Match each Kubernetes certificate type to its usage.
Last reviewed: Jul 4, 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.