An API Ingress must match only the literal path /v1/status and must not match /v1/status/details. Which pathType should the rule use?
Select an answer to reveal the explanation.
Short Explanation
Exact is a locked door for one hallway; Prefix is a whole wing. For only /v1/status and not /v1/status/details, use pathType Exact. Prefix would gladly walk further down the path.
Full Explanation
When an API Ingress must match only the literal path /v1/status and must not match /v1/status/details, use pathType Exact with path /v1/status. Exact matches that path only and does not include longer child paths. Municipal status endpoints that must not accidentally capture nested detail routes rely on Exact rather than Prefix. Choosing pathType is as important as choosing the path string itself on modern Ingress APIs.
ImplementationSpecific with path / does not force Exact matching for /v1/status; ImplementationSpecific defers semantics to the controller, and path / is far too broad for a single status resource. Prefix with path /v1/status also matches nested paths under that prefix, including /v1/status/details, which violates the requirement. Prefix with path / matches essentially all paths and is not limited to a single segment named status.
Exam caveat: Prefix versus Exact is a frequent CKAD trap—Prefix /foo matches /foo/bar, while Exact /foo does not. Always set pathType explicitly in YAML rather than hoping controller defaults do what you mean. Operational check: create an Exact rule for /v1/status, request /v1/status (should match) and /v1/status/details (should not match this rule), and document pathType in the city API Ingress manifest review. Prefer explicit pathType on every rule for exam clarity and controller portability across nginx, Traefik, or cloud controllers.