CKAD Prefix Practice Question
Which THREE of the following are valid Ingress pathTypes in Kubernetes networking.k8s.io/v1?
⚠ Common exam trap
Candidates often mistakenly believe that only `Prefix` and `Exact` are valid in networking.k8s.io/v1, but `ImplementationSpecific` is also a standard pathType in the stable v1 API.
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
✓
Prefix
In Kubernetes networking.k8s.io/v1, the valid Ingress pathTypes are `Prefix`, `Exact`, and `ImplementationSpecific`. `Prefix` matches URL paths based on a prefix (e.g., `/api` matches `/api/v1`), `Exact` matches the path exactly (e.g., `/api` only matches `/api`), and `ImplementationSpecific` allows the ingress controller to define its own path matching logic. All three are defined in the v1 API.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Prefix
Why this is correct
Prefix is a valid Ingress pathType that matches URL paths by whole path segments, not by raw string prefix. For example, a Prefix rule for /foo will match both /foo and /foo/bar, but it will not match /foobar because the match is evaluated on element boundaries separated by slashes. This makes Prefix the standard way to implement wildcard-style routing for a subtree of paths.
- ✓
Exact
Why this is correct
Exact is a valid Ingress pathType that requires the incoming URL path to match the specified path literally, with no extra trailing segments. A rule with path /foo and pathType Exact will match only /foo and not /foo/bar, making it useful for pinning a single route and avoiding overlapping broader Prefix rules. It is one of the three allowed values in the networking.k8s.io/v1 Ingress API.
- ✗
Wildcard
Why it's wrong here
Wildcard is not a valid pathType in Kubernetes Ingress. The pathType field is an enum restricted to Prefix, Exact, or ImplementationSpecific, so any other value is rejected by the API server during validation. Although wildcard patterns like * are allowed in the host field (for example *.example.com), Kubernetes does not define a Wildcard pathType; to get wildcard-like path behavior, you must use Prefix.
- ✗
Suffix
Why it's wrong here
Suffix is not a valid pathType in the Kubernetes Ingress API. The schema for networking.k8s.io/v1 Ingress only permits Prefix, Exact, and ImplementationSpecific, so a Suffix pathType would fail validation and can never be persisted to etcd. Suffix-style matching is not part of the API contract and can only be attempted through ImplementationSpecific if a particular ingress controller chooses to support it, but it is not a standard value.
- ✓
ImplementationSpecific
Why this is correct
ImplementationSpecific is a valid pathType in networking.k8s.io/v1, but it delegates the exact matching semantics to the ingress controller. Different controllers may interpret this pathType differently, such as treating it as a prefix, an exact match, or using their own regex-based patterns, so using it makes your Ingress rules less portable across clusters. It is designed for controllers that need custom path matching beyond the standardized Prefix and Exact rules, with no API-guaranteed behavior.
Go deeper
Related to this question
About these practice questions
This CKAD question is part of Courseiva's 826-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CKAD 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 CKAD exam.