The answer is a ClusterIP Service for the backend. This is correct because a ClusterIP Service assigns a stable, internal IP address and a DNS name—such as `backend.default.svc.cluster.local`—that is resolvable only from within the GKE cluster, enabling name-based service discovery without exposing the backend to external traffic. On the Google Associate Cloud Engineer exam, this concept tests your understanding of Kubernetes networking fundamentals, specifically how CoreDNS resolves Service names for inter-Pod communication. A common trap is confusing ClusterIP with NodePort or LoadBalancer, which both expose services externally. Remember the key distinction: ClusterIP is internal-only, making it the default and safest choice for backend-to-frontend communication. Memory tip: think “ClusterIP = Cluster Internal Private,” so if it should stay inside the cluster, ClusterIP is your pick.
Google ACE Deploying and implementing a cloud solution Practice Question
This ACE practice question tests your understanding of deploying and implementing 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.
A platform team is deploying a multi-tier application on GKE: a frontend Deployment, a backend Deployment, and a Redis StatefulSet. The backend must be reachable by name from the frontend, but not from outside the cluster. Which Kubernetes resource enables internal name-based service discovery?
Why wrong: NodePort exposes the service on a port of every node's IP — it's reachable from outside the cluster, not just internally.
B
A ClusterIP Service for the backend
ClusterIP Services get a stable cluster-internal IP and DNS name. Pods within the cluster resolve the service by name; it's not reachable from outside.
C
A LoadBalancer Service for the backend
Why wrong: LoadBalancer provisions an external cloud load balancer — exposing the backend publicly, which violates the requirement.
D
A Kubernetes Ingress resource for the backend
Why wrong: Ingress routes external HTTP/HTTPS traffic into the cluster — it doesn't provide internal service-to-service discovery.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A ClusterIP Service for the backend
A ClusterIP Service exposes the backend Pods on a stable, internal IP address that is only reachable from within the GKE cluster. The frontend can resolve the backend by the Service's DNS name (e.g., `backend.default.svc.cluster.local`) using the cluster's internal DNS (CoreDNS), enabling name-based service discovery without exposing the backend to external traffic.
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.
✗
A NodePort Service for the backend
Why it's wrong here
NodePort exposes the service on a port of every node's IP — it's reachable from outside the cluster, not just internally.
✓
A ClusterIP Service for the backend
Why this is correct
ClusterIP Services get a stable cluster-internal IP and DNS name. Pods within the cluster resolve the service by name; it's not reachable from outside.
Related concept
Read the scenario before looking for a memorised answer.
✗
A LoadBalancer Service for the backend
Why it's wrong here
LoadBalancer provisions an external cloud load balancer — exposing the backend publicly, which violates the requirement.
✗
A Kubernetes Ingress resource for the backend
Why it's wrong here
Ingress routes external HTTP/HTTPS traffic into the cluster — it doesn't provide internal service-to-service discovery.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that Ingress is used for internal service discovery, but Ingress is an external-facing layer-7 routing resource that requires a Service (typically ClusterIP or NodePort) to route traffic, and it does not provide internal DNS-based name resolution by itself.
Detailed technical explanation
How to think about this question
Under the hood, a ClusterIP Service creates a virtual IP (VIP) backed by iptables or IPVS rules on each node, load-balancing traffic to the backend Pods. The Service's DNS name is registered in the cluster's DNS (CoreDNS) via the Kubernetes DNS add-on, allowing the frontend to use standard DNS resolution (A/AAAA records) for service discovery. In real-world scenarios, this pattern is essential for microservices communication where internal services must remain isolated from external access, and it avoids the overhead and security risks of exposing internal endpoints.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this ACE question in full detail.
Deploying and implementing a cloud solution — This question tests Deploying and implementing a cloud solution — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: A ClusterIP Service for the backend — A ClusterIP Service exposes the backend Pods on a stable, internal IP address that is only reachable from within the GKE cluster. The frontend can resolve the backend by the Service's DNS name (e.g., `backend.default.svc.cluster.local`) using the cluster's internal DNS (CoreDNS), enabling name-based service discovery without exposing the backend to external traffic.
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 →
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.
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.