- A
Cloud DNS private zone configured for the cluster's namespace
Why wrong: Cloud DNS private zones are GCP-level DNS — they're not the source of in-cluster `svc.cluster.local` resolution, which is handled by the cluster's CoreDNS.
- B
Kubernetes cluster DNS (CoreDNS) resolving Service names within the cluster
CoreDNS (the default in-cluster DNS server) automatically creates records for every Service in the format `[service].[namespace].svc.cluster.local`, enabling service-to-service discovery.
- C
Anthos Service Mesh — required for service-to-service DNS
Why wrong: Anthos Service Mesh adds observability, traffic management, and mTLS — in-cluster DNS resolution works without it, built into standard Kubernetes.
- D
A custom /etc/hosts entry on each Pod
Why wrong: Manually managing /etc/hosts in Pods is impractical and doesn't scale — Kubernetes CoreDNS handles this automatically.
Quick Answer
The answer is Kubernetes cluster DNS, typically implemented by CoreDNS, which resolves Service names like `service-b.production.svc.cluster.local` to the corresponding ClusterIP. This internal DNS service discovery mechanism works because CoreDNS runs as a Deployment in the kube-system namespace and automatically creates DNS records for every Service based on its name and namespace, allowing Pods to discover each other without public DNS. On the Google Associate Cloud Engineer exam, this concept tests your understanding of how GKE handles cluster-local networking, often appearing in scenarios where microservices need to communicate reliably across namespaces. A common trap is confusing this with external DNS or Cloud DNS, but remember that the `svc.cluster.local` suffix is the key indicator of Kubernetes internal DNS. Memory tip: think of CoreDNS as the cluster’s phonebook—it knows every Service’s name and IP, so Pods never need to leave the cluster to find each other.
Google ACE Planning and configuring a cloud solution Practice Question
This ACE practice question tests your understanding of planning and configuring a cloud solution. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Microservices in a GKE cluster need to discover each other by name without using public DNS. Service A calls Service B at `http://service-b.production.svc.cluster.local`. Which GCP/Kubernetes feature provides this internal DNS resolution?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Kubernetes cluster DNS (CoreDNS) resolving Service names within the cluster
Kubernetes cluster DNS, typically implemented by CoreDNS, is the built-in mechanism that resolves Service names like `service-b.production.svc.cluster.local` to the corresponding ClusterIP. This allows Pods to discover each other by name without relying on external or public DNS. CoreDNS runs as a Deployment in the kube-system namespace and automatically creates DNS records for every Service based on its name and namespace.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Cloud DNS private zone configured for the cluster's namespace
Why it's wrong here
Cloud DNS private zones are GCP-level DNS — they're not the source of in-cluster `svc.cluster.local` resolution, which is handled by the cluster's CoreDNS.
- ✓
Kubernetes cluster DNS (CoreDNS) resolving Service names within the cluster
Why this is correct
CoreDNS (the default in-cluster DNS server) automatically creates records for every Service in the format `[service].[namespace].svc.cluster.local`, enabling service-to-service discovery.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Anthos Service Mesh — required for service-to-service DNS
Why it's wrong here
Anthos Service Mesh adds observability, traffic management, and mTLS — in-cluster DNS resolution works without it, built into standard Kubernetes.
- ✗
A custom /etc/hosts entry on each Pod
Why it's wrong here
Manually managing /etc/hosts in Pods is impractical and doesn't scale — Kubernetes CoreDNS handles this automatically.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse Cloud DNS (a GCP-managed DNS service for VPCs) with Kubernetes cluster DNS, or assume that a service mesh like Anthos is necessary for internal service discovery, when in fact CoreDNS provides this capability out of the box in any standard GKE cluster.
Detailed technical explanation
How to think about this question
CoreDNS uses the `kubernetes` plugin to watch the Kubernetes API for Services and Endpoints, creating A/AAAA records for each Service in the format `<service>.<namespace>.svc.cluster.local`. For headless Services, CoreDNS returns the Pod IPs directly, enabling stateful workloads like databases to discover individual Pods. A subtle behavior is that CoreDNS also supports SRV records for named ports, which can be queried for load-balanced access to specific port names.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Planning and configuring a cloud solution — study guide chapter
Learn the concepts, then practise the questions
- →
Planning and configuring a cloud solution practice questions
Targeted practice on this topic area only
- →
All ACE questions
500 questions across all exam domains
- →
Google Associate Cloud Engineer study guide
Full concept coverage aligned to exam objectives
- →
ACE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related ACE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Setting up a cloud solution environment practice questions
Practise ACE questions linked to Setting up a cloud solution environment.
Planning and configuring a cloud solution practice questions
Practise ACE questions linked to Planning and configuring a cloud solution.
Deploying and implementing a cloud solution practice questions
Practise ACE questions linked to Deploying and implementing a cloud solution.
Ensuring successful operation of a cloud solution practice questions
Practise ACE questions linked to Ensuring successful operation of a cloud solution.
Configuring access and security practice questions
Practise ACE questions linked to Configuring access and security.
ACE fundamentals practice questions
Practise ACE questions linked to ACE fundamentals.
ACE scenario practice questions
Practise ACE questions linked to ACE scenario.
ACE troubleshooting practice questions
Practise ACE questions linked to ACE troubleshooting.
Practice this exam
Start a free ACE practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this ACE question test?
Planning and configuring a cloud solution — This question tests Planning and configuring a cloud solution — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Kubernetes cluster DNS (CoreDNS) resolving Service names within the cluster — Kubernetes cluster DNS, typically implemented by CoreDNS, is the built-in mechanism that resolves Service names like `service-b.production.svc.cluster.local` to the corresponding ClusterIP. This allows Pods to discover each other by name without relying on external or public DNS. CoreDNS runs as a Deployment in the kube-system namespace and automatically creates DNS records for every Service based on its name and namespace.
What should I do if I get this ACE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.