- A
kubectl expose pod postgres-pod --type=LoadBalancer --port=5432
Why wrong: Exposing the Pod as a LoadBalancer creates a public external IP — the opposite of what's needed. Port-forward provides local-only access.
- B
kubectl port-forward svc/postgres-service 5432:5432
`kubectl port-forward` tunnels traffic from localhost:5432 to the cluster service's port 5432 — accessible only from the developer's machine, with no network changes.
- C
kubectl tunnel --local=5432 --remote=postgres-service:5432
Why wrong: `kubectl tunnel` is not a valid kubectl command. Use `kubectl port-forward`.
- D
gcloud container ssh postgres-pod --port-forward=5432:5432
Why wrong: `gcloud container ssh` is not a valid command for port forwarding — use `kubectl port-forward`.
How to Forward Local Port to a GKE Service with kubectl
This ACE practice question tests your understanding of ace exam topics. 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 developer needs to forward traffic from their local port 5432 to a PostgreSQL service running in GKE on port 5432, to test database queries locally without exposing the database externally. Which kubectl command achieves this?
Quick Answer
The correct command is `kubectl port-forward svc/postgres-service 5432:5432`. This works because `kubectl port-forward` creates a secure, direct TCP tunnel from your local machine’s port 5432 to the specified service’s port 5432 inside the GKE cluster, allowing you to interact with the PostgreSQL database as if it were running locally without ever exposing it to the internet. On the Google Associate Cloud Engineer exam, this question tests your understanding of secure, temporary access patterns for debugging and development—a common scenario where candidates mistakenly choose `kubectl expose` or a LoadBalancer, which would create a public endpoint. The key trap is remembering that `port-forward` targets services (using `svc/`) or pods, not deployments directly, and the syntax is `local-port:service-port`. Memory tip: think “tunnel, not expose”—if the goal is local testing without external access, always reach for `port-forward`.
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
kubectl port-forward svc/postgres-service 5432:5432
Option B is correct because `kubectl port-forward` creates a local tunnel from port 5432 on the developer's machine to the specified service's port 5432 inside the GKE cluster. This allows the developer to connect to the PostgreSQL service as if it were running locally, without exposing it to the internet via a LoadBalancer or Ingress.
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.
- ✗
kubectl expose pod postgres-pod --type=LoadBalancer --port=5432
Why it's wrong here
Exposing the Pod as a LoadBalancer creates a public external IP — the opposite of what's needed. Port-forward provides local-only access.
- ✓
kubectl port-forward svc/postgres-service 5432:5432
Why this is correct
`kubectl port-forward` tunnels traffic from localhost:5432 to the cluster service's port 5432 — accessible only from the developer's machine, with no network changes.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
kubectl tunnel --local=5432 --remote=postgres-service:5432
Why it's wrong here
`kubectl tunnel` is not a valid kubectl command. Use `kubectl port-forward`.
- ✗
gcloud container ssh postgres-pod --port-forward=5432:5432
Why it's wrong here
`gcloud container ssh` is not a valid command for port forwarding — use `kubectl port-forward`.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between exposing a service externally (LoadBalancer) and creating a local tunnel (port-forward), and candidates may mistakenly choose a LoadBalancer option thinking it is required for connectivity, ignoring the 'without exposing externally' constraint.
Trap categories for this question
Command / output trap
`kubectl tunnel` is not a valid kubectl command. Use `kubectl port-forward`.
Detailed technical explanation
How to think about this question
Under the hood, `kubectl port-forward` establishes a WebSocket connection between the client and the Kubernetes API server, which then proxies TCP traffic to the target pod or service. This avoids the need for a NodePort or LoadBalancer, making it ideal for debugging and testing in development environments. A subtle behavior is that the port-forward session is tied to the terminal; if the terminal is closed, the tunnel is torn down, so tools like `nohup` or `kubectl port-forward &` are often used to keep it alive.
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.
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.
Configuring Access and Security practice questions
Practise ACE questions linked to Configuring Access and Security.
Planning and Configuring a Cloud Solution practice questions
Practise ACE questions linked to Planning and Configuring a Cloud Solution.
Ensuring Successful Operation of a Cloud Solution practice questions
Practise ACE questions linked to Ensuring Successful Operation of a Cloud Solution.
Deploying and Implementing a Cloud Solution practice questions
Practise ACE questions linked to Deploying and Implementing a Cloud Solution.
Setting Up a Cloud Solution Environment practice questions
Practise ACE questions linked to Setting Up a Cloud Solution Environment.
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?
Read the scenario before looking for a memorised answer.
What is the correct answer to this question?
The correct answer is: kubectl port-forward svc/postgres-service 5432:5432 — Option B is correct because `kubectl port-forward` creates a local tunnel from port 5432 on the developer's machine to the specified service's port 5432 inside the GKE cluster. This allows the developer to connect to the PostgreSQL service as if it were running locally, without exposing it to the internet via a LoadBalancer or Ingress.
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 →
Keep practising
More ACE practice questions
- A team's Cloud Build pipeline must: (1) run unit tests, (2) build a Docker image only if tests pass, (3) push the image…
- A team needs a database backup job to run every day at 2 AM UTC. The job calls an HTTP endpoint to trigger the backup. T…
- A team wants to receive an email alert when the average CPU utilization of VMs in a managed instance group exceeds 80% f…
- A Go service is consuming significantly more CPU than expected. The team suspects an inefficient function but doesn't kn…
- A network team is creating a new VPC and must decide between auto mode and custom mode. Why would they choose custom mod…
- A company organizes its GCP projects by business unit — Finance, Engineering, and Sales. Which resource is best suited t…
Last reviewed: Jun 30, 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.