The answer is the need for a single anycast IP address worldwide, along with SSL termination location and backend protocol requirements. A global external HTTP(S) load balancer uses a single anycast IP to route traffic to the nearest Google Front End, where SSL is terminated at the edge, decrypting traffic close to the user and forwarding plaintext HTTP to the backend. In contrast, a regional external HTTP(S) load balancer terminates SSL at the backend itself, meaning encrypted traffic must travel to the specific regional instance before decryption, which increases latency and backend processing load. On the Google Professional Cloud Network Engineer exam, this distinction tests your understanding of how traffic flow and security boundaries shift between global edge termination and regional backend termination. A common trap is assuming both handle SSL the same way; remember that global terminates at the edge, regional terminates at the backend. Memory tip: “Global at the edge, regional at the hedge” — the hedge being your backend instance.
PCNE Configuring network services Practice Question
This PCNE practice question tests your understanding of configuring network services. 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.
Which THREE factors should be considered when choosing between a global external HTTP(S) load balancer and a regional external HTTP(S) load balancer? (Choose 3.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
SSL termination at the edge (global) vs. at the backend (regional).
Regional external HTTP(S) load balancers terminate SSL at the backend (the backend service or instance), meaning the encrypted traffic must travel to the backend before decryption. Global external HTTP(S) load balancers terminate SSL at the edge (Google Front End), decrypting traffic at the closest point of presence and forwarding plaintext HTTP to the backend. This architectural difference impacts security, latency, and backend processing requirements, making it a key factor in choosing between the two.
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.
✗
Support for multiple backend types (Compute Engine, GKE, serverless).
Why it's wrong here
Both support multiple backend types.
✓
SSL termination at the edge (global) vs. at the backend (regional).
Why this is correct
Global terminates SSL at the edge; regional terminates at the backend.
Related concept
Read the scenario before looking for a memorised answer.
Read the scenario before looking for a memorised answer.
✓
Need for a single anycast IP address worldwide.
Why this is correct
Global load balancer provides a single anycast IP; regional uses regional IP.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that SSL termination location is the same for both load balancer types, but the key distinction is that global terminates at the edge (GFE) and regional terminates at the backend, which directly affects security and performance decisions.
Detailed technical explanation
How to think about this question
Global external HTTP(S) load balancers use Google's global anycast IP and terminate SSL at the edge via Google Front Ends (GFEs), which support TLS 1.3 and certificate management. Regional external HTTP(S) load balancers use a regional IP and require SSL termination at the backend, meaning the backend must handle decryption and certificate management, which can increase CPU overhead and require careful key management. In a real-world scenario, a global load balancer is preferred for latency-sensitive applications with users worldwide, while a regional load balancer is chosen for compliance or when backend SSL termination is required.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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.
Configuring network services — This question tests Configuring network services — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: SSL termination at the edge (global) vs. at the backend (regional). — Regional external HTTP(S) load balancers terminate SSL at the backend (the backend service or instance), meaning the encrypted traffic must travel to the backend before decryption. Global external HTTP(S) load balancers terminate SSL at the edge (Google Front End), decrypting traffic at the closest point of presence and forwarding plaintext HTTP to the backend. This architectural difference impacts security, latency, and backend processing requirements, making it a key factor in choosing between the two.
What should I do if I get this PCNE 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 PCNE 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 PCNE 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.