1V0-71.21 · Question #20
Which statement is FALSE regarding Kubernetes Services?
The correct answer is B. All services require selectors to function properly. Option B is false because Kubernetes Services do not always require selectors - ExternalName services use DNS CNAME aliasing instead of selectors, and you can create a Service without a selector by manually defining its Endpoints object to route to any IP address, including…
Question
Which statement is FALSE regarding Kubernetes Services?
Options
- AA service can be pointed to another service.
- BAll services require selectors to function properly.
- CServices expose applications running on a pod or set of pods.
- DServices enable communication between pods running on different nodes.
How the community answered
(35 responses)- A3% (1)
- B91% (32)
- C6% (2)
Explanation
Option B is false because Kubernetes Services do not always require selectors - ExternalName services use DNS CNAME aliasing instead of selectors, and you can create a Service without a selector by manually defining its Endpoints object to route to any IP address, including external ones.
Why the distractors are true (and therefore wrong answers):
- A is true - a Service can point to another Service, most commonly via
ExternalName, which returns a CNAME for another DNS name (including another Service's DNS entry). - C is true - the core purpose of a Service is to expose a stable endpoint to one or more pods, abstracting away their ephemeral IPs.
- D is true - Services use
kube-proxyand the cluster's networking layer to route traffic across nodes, enabling pods on different nodes to communicate seamlessly.
Memory tip: Remember "SANS" - Services Are Not always Selector-dependent. If you can name even one selector-less type (ExternalName), you'll immediately spot any "all services require selectors" claim as false.
Topics
Community Discussion
7
Ingrid P.Dec 17, 2025B is your answer, and it is worth burning into a card because the exception trips people up on test day. Selectors are common but not required, and the canonical counterexample is the ExternalName service type, which maps a service name to an external DNS name and uses no selector at all. You can also create a selector-less service and wire it to an Endpoints object by hand, which is useful when you need to route traffic to something outside the cluster. A, C, and D are all true statements, so eliminate them fast and move on. The card I keep for this one reads "name two Kubernetes service types or configurations that require no selector" on the front, and "ExternalName, manual Endpoints object" on the back. That framing forces active recall of the mechanism rather than just the vocabulary, and it keeps the review interval honest because vague recognition cards inflate faster than they should.
Viktor S.Dec 18, 2025ExternalName is the clean counterexample but worth noting it skips kube-proxy entirely and resolves via CoreDNS CNAME, so it behaves differently enough from the manual Endpoints path that lumping them on one card might blur exactly the detail the exam is testing.
Fatima Z.Nov 23, 2025Services talk to PODS only, never peers, A is your false flag.
Ingrid P.Nov 23, 2025Fatima, actually B is correct here. A Service's label selector matches Pod labels directly, so traffic goes to the Pods themselves, which is exactly what option A describes, making B the false flag in this question.
Viktor S.Dec 7, 2025Option B is the false one, and the reason exposes a gap that trips up a lot of people who just memorized "services need selectors." Do you know what kind of service lets you skip the selector entirely and wire traffic to an external endpoint or another namespace manually?
Toby R.Dec 29, 2025A is wrong, services pointing to other services is not a real pattern, B is the false one.
Ingrid P.Dec 31, 2025Toby, the answer is B, services referencing other services is absolutely a recognized pattern in service-oriented and microservices architecture, so A holds up fine. B contains the inaccurate claim, which is exactly what makes it the keyed answer here.