Correct Answer: Check the status and logs of the CoreDNS pods and Service in the kube-system namespace
DNS resolution inside a Kubernetes cluster is managed by a cluster-dns service (typically CoreDNS). If external or internal domain names fail to resolve but IP communication works,...
Correct Answer
Check the status and logs of the CoreDNS pods and Service in the kube-system namespace
Why This Answer Is Correct
DNS resolution inside a Kubernetes cluster is managed by a cluster-dns service (typically CoreDNS). If external or internal domain names fail to resolve but IP communication works, CoreDNS is the primary component to inspect.
This question evaluates your knowledge of Kubernetes Networking — a core concept tested in cloud certification exams. Understanding Kubernetes Networking is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
If a developer wants an application to be accessible via standard HTTP/HTTPS hostnames and paths (e.g., myapp.com/api), what object should be deployed?
By default, pods in a Kubernetes cluster can communicate with any other pod in any namespace. You want to restrict traffic so that the 'backend' pods only accept connections from 'frontend' pods. Which resource should you configure?
You want to configure an Ingress controller to route HTTP traffic to two different backend services based on the URL path: traffic to '/api' should go to 'api-service', and all other traffic should go to 'web-service'. How should you define this routing logic in the Ingress resource spec?
You have a frontend service that communicates with a backend service. To minimize network latency and inter-zone bandwidth costs, you want the frontend pod to only route traffic to backend pods running on the exact same node, returning a connection error if no local backend pod is available. Which Service spec field should you configure?