Bird
0
0

Which YAML snippet correctly defines a headless service in Kubernetes?

easy📝 Syntax Q3 of 15
Kubernetes - Services
Which YAML snippet correctly defines a headless service in Kubernetes?
AapiVersion: v1 kind: Service metadata: name: my-headless spec: clusterIP: None selector: app: myapp ports: - port: 80
BapiVersion: v1 kind: Service metadata: name: my-service spec: clusterIP: 10.0.0.1 selector: app: myapp ports: - port: 80
CapiVersion: v1 kind: Service metadata: name: my-service spec: type: LoadBalancer selector: app: myapp ports: - port: 80
DapiVersion: v1 kind: Service metadata: name: my-service spec: externalIPs: - 192.168.1.1 selector: app: myapp ports: - port: 80
Step-by-Step Solution
Solution:
  1. Step 1: Check clusterIP field for headless service

    Setting clusterIP: None is required to create a headless service.
  2. Step 2: Verify YAML correctness

    apiVersion: v1 kind: Service metadata: name: my-headless spec: clusterIP: None selector: app: myapp ports: - port: 80 correctly sets clusterIP: None with selector and ports.
  3. Final Answer:

    YAML with clusterIP: None defines headless service -> Option A
  4. Quick Check:

    clusterIP None in YAML = headless service [OK]
Quick Trick: clusterIP None in YAML means headless service [OK]
Common Mistakes:
  • Using clusterIP with an IP disables headless behavior
  • Confusing LoadBalancer type with headless service
  • Using externalIPs instead of clusterIP None

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes