xhibit":false,"isExhibitQuestion":false,"questionPairs":null,"hasMatchingPairs":false,"isMatchingQuestion":false,"relatedQuestions":[],"breadcrumbItems":null,"nextQuestionUrl":null,"previousQuestionUrl":null,"domainPracticeUrl":null,"certificationUrl":null,"domainUrl":null,"hasAnswerOptions":true,"updatedAt":"2026-06-11T16:07:47.853+00:00","questionType":"multiple_choice"},{"id":"6aaf8e62-8093-49f4-884c-e7db90f4b466","slug":"what-is-the-dns-name-for-a-service-named-api-in-the-defau-jm7b6","certificationSlug":"cncf-cka","examCode":"CKA","examName":"Certified Kubernetes Administrator CKA","questionText":"What is the DNS name for a Service named 'api' in the 'default' namespace?","difficulty":"medium","domain":"Services and Networking","domainSlug":"cka-services-networking","topic":"","questionNumber":0,"totalQuestions":0,"options":[{"key":"A","isCorrect":true,"text":"api.default.svc.cluster.local","explanation":"The Kubernetes DNS schema for a Service is ..svc.cluster.local. Since the Service is named 'api' and created in the default namespace, the fully qualified domain name becomes api.default.svc.cluster.local. This FQDN resolves to the Service's ClusterIP and enables reliable cluster-wide service discovery.","masteryContext":""},{"key":"B","isCorrect":false,"text":"default.api.svc.cluster.local","explanation":"This reverses the expected resource and namespace ordering. In Kubernetes, the Service name is the leftmost label, followed by the namespace, so the correct form is service.namespace, not namespace.service. A query for default.api.svc.cluster.local would be interpreted as a Service named 'default' in the namespace 'api', which does not match the intended resources and would fail DNS resolution.","masteryContext":""},{"key":"C","isCorrect":false,"text":"api.svc.default.cluster.local","explanation":"Here the 'svc' component is incorrectly inserted between the service name and the namespace. The valid structure is always ..svc, with 'svc' appearing after the namespace, not before it. Placing 'svc' between api and default breaks the canonical hierarchy, so this name neither matches the service nor conforms to Kubernetes DNS naming rules.","masteryContext":""},{"key":"D","isCorrect":false,"text":"api.default.cluster.local","explanation":"This omits the 'svc' subdomain, which is a mandatory portion of the service DNS FQDN. The sequence '..cluster.local' is not a standard record type; services live under the '.svc' subdomain. Without 'svc', the DNS name is incomplete, and CoreDNS will not return the ClusterIP record for the api service.","masteryContext":""}],"correctOptionKey":"A","correctOptions":["A"],"correctAnswerText":"","isMultiSelect":false,"mainExplanation":"The correct DNS name for a Service in Kubernetes follows the pattern `..svc.cluster.local`. For a Service named 'api' in the 'default' namespace, this resolves to `api.default.svc.cluster.local`. The `svc` subdomain is a fixed part of the cluster domain, and `cluster.local` is the default cluster domain suffix configured in kubelet and CoreDNS.","examTrap":"The trap here is that candidates often forget the `svc` subdomain or reverse the service/namespace order, because they may confuse the DNS format with other Kubernetes naming conventions (e.g., pod DNS or headless service records) or assume the namespace comes first.","examTip":null,"technicalDeepDive":"In Kubernetes, CoreDNS implements the cluster's internal DNS and relies on the FQDN structure ..svc.cluster.local to expose service discovery. Each service receives an A record containing its ClusterIP, and a query against that FQDN returns the IP for reliable load-balanced access. A common misconception is that 'svc' is optional or can be placed anywhere, but it is a fixed label in the DNS hierarchy that distinguishes service records from pod records, which use 'pod' instead. This naming convention also applies to headless services, where the DNS returns individual pod IPs rather than