- A
Change the load balancer to a regional load balancer and deploy additional instance groups in other regions.
Correct. Changing to a regional load balancer and deploying additional instance groups in other regions reduces latency and allows users in Asia to reach a local backend. This ensures global performance and availability.
- B
Enable Cloud CDN on the backend service to cache content closer to users.
Why wrong: Incorrect. Cloud CDN caches static content at edge locations, but it does not address connectivity issues or high latency for dynamic content. The application may not be cacheable, and CDN does not change the backend location.
- C
Configure a DNS A record for the load balancer's IP address with a low TTL.
Why wrong: Incorrect. Configuring a DNS A record with a low TTL does not affect the load balancer's routing or backend location. It only controls how quickly DNS changes propagate.
- D
Ensure the backend service's 'Enable Global Access' checkbox is selected in the instance group's network settings.
Why wrong: Incorrect. The 'Enable Global Access' checkbox is a setting for Internal Load Balancers, not for Global External HTTP(S) Load Balancers. It is not applicable here.
Fix Global Load Balancer Connectivity with Enable Global Access
This PCNE practice question tests your understanding of global external http(s) load balancer. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. A key principle to apply: global External HTTP(S) Load Balancer. 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 company has deployed a Global External HTTP(S) Load Balancer with a backend service that points to an instance group in us-central1. The load balancer's frontend uses a reserved static external IP address. Users in Europe report high latency, while users in Asia cannot reach the application at all. The application works fine when accessed directly via the instance group's internal IPs from within us-central1. Which action should be taken to resolve the issue?
Quick Answer
The correct answer is to ensure the backend service's 'Enable Global Access' checkbox is selected in the instance group's network settings. This setting is required because a Global External HTTP(S) Load Balancer uses a global anycast IP, and without it, the load balancer can only forward traffic to backends within the same region as its frontend, effectively breaking cross-region connectivity. On the Google Professional Cloud Network Engineer exam, this scenario tests your understanding of how global load balancing interacts with VPC network configurations—a common trap is assuming that a global load balancer automatically reaches any instance group, when in fact the backend’s network must explicitly allow global access. The high latency for European users and total failure for Asian users are classic symptoms of this misconfiguration. To remember: think of “Enable Global Access” as the permission slip that lets the load balancer’s anycast IP travel across regions to reach your instances.
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
Change the load balancer to a regional load balancer and deploy additional instance groups in other regions.
The Global External HTTP(S) Load Balancer distributes traffic to backends across regions, but if the backend is only in us-central1, users far away experience high latency and, in some cases, cannot reach the application due to network distance or peering issues. The recommended solution is to use regional load balancers with backend instance groups in each region where users are located. This ensures low latency and high availability globally.
Key principle: Global External HTTP(S) Load Balancer
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Change the load balancer to a regional load balancer and deploy additional instance groups in other regions.
Why this is correct
Correct. Changing to a regional load balancer and deploying additional instance groups in other regions reduces latency and allows users in Asia to reach a local backend. This ensures global performance and availability.
Related concept
Global External HTTP(S) Load Balancer
- ✗
Enable Cloud CDN on the backend service to cache content closer to users.
Why it's wrong here
Incorrect. Cloud CDN caches static content at edge locations, but it does not address connectivity issues or high latency for dynamic content. The application may not be cacheable, and CDN does not change the backend location.
- ✗
Configure a DNS A record for the load balancer's IP address with a low TTL.
Why it's wrong here
Incorrect. Configuring a DNS A record with a low TTL does not affect the load balancer's routing or backend location. It only controls how quickly DNS changes propagate.
- ✗
Ensure the backend service's 'Enable Global Access' checkbox is selected in the instance group's network settings.
Why it's wrong here
Incorrect. The 'Enable Global Access' checkbox is a setting for Internal Load Balancers, not for Global External HTTP(S) Load Balancers. It is not applicable here.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Candidates may assume a global load balancer automatically provides low latency to all users, but if the backend is only in one region, latency is high and some regions may have connectivity issues. The proper fix is to use regional load balancers with backends in each region, not just a single global load balancer.
Detailed technical explanation
How to think about this question
The Global External HTTP(S) Load Balancer uses a single anycast IP address that is advertised from multiple Google Cloud edge locations worldwide. The 'Enable Global Access' setting on the instance group's network configuration allows the load balancer to forward traffic to backend instances in any region, not just the region where the load balancer's frontend is configured. Without this setting, the load balancer's forwarding rule is restricted to the same region as the backend, breaking cross-region traffic.
KKey Concepts to Remember
- Global External HTTP(S) Load Balancer
- Regional Load Balancer
- Backend Service
- Latency Optimization
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
Global External HTTP(S) Load Balancer
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Visual reference
What to study next
Got this wrong? Here's your next step.
Review global External HTTP(S) Load Balancer, then practise related PCNE questions on the same topic to reinforce the concept.
Related practice questions
Related PCNE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Configuring Network Services practice questions
Practise PCNE questions linked to Configuring Network Services.
Implementing Hybrid Interconnectivity practice questions
Practise PCNE questions linked to Implementing Hybrid Interconnectivity.
Managing, Monitoring, and Optimising Network Operations practice questions
Practise PCNE questions linked to Managing, Monitoring, and Optimising Network Operations.
Designing, Planning, and Prototyping a GCP Network practice questions
Practise PCNE questions linked to Designing, Planning, and Prototyping a GCP Network.
Implementing VPC Instances practice questions
Practise PCNE questions linked to Implementing VPC Instances.
Implementing network security practice questions
Practise PCNE questions linked to Implementing network security.
Implementing a Virtual Private Cloud practice questions
Practise PCNE questions linked to Implementing a Virtual Private Cloud.
PCNE fundamentals practice questions
Practise PCNE questions linked to PCNE fundamentals.
PCNE scenario practice questions
Practise PCNE questions linked to PCNE scenario.
PCNE troubleshooting practice questions
Practise PCNE questions linked to PCNE troubleshooting.
Practice this exam
Start a free PCNE 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 PCNE question test?
Global External HTTP(S) Load Balancer
What is the correct answer to this question?
The correct answer is: Change the load balancer to a regional load balancer and deploy additional instance groups in other regions. — The Global External HTTP(S) Load Balancer distributes traffic to backends across regions, but if the backend is only in us-central1, users far away experience high latency and, in some cases, cannot reach the application due to network distance or peering issues. The recommended solution is to use regional load balancers with backend instance groups in each region where users are located. This ensures low latency and high availability globally.
What should I do if I get this PCNE question wrong?
Review global External HTTP(S) Load Balancer, then practise related PCNE questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Global External HTTP(S) Load Balancer
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 →
Same concept, more angles
2 more ways this is tested on PCNE
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company is deploying a global HTTP load balancer with a backend service that spans multiple regions. The backend instances are in a managed instance group. They want to use Cloud CDN to cache content. What is the minimal set of configurations required on the backend bucket or instance group to enable Cloud CDN?
hard- A.Configure Identity-Aware Proxy (IAP) on the backend service to allow cache
- B.Use the gcloud compute backend-services update command with the --enable-cdn flag on the load balancer itself
- ✓ C.Enable Cloud CDN on the backend service and ensure that the load balancer's frontend uses HTTP or HTTPS protocol
- D.Create a Cloud Storage bucket with public access and set it as the backend
Why C: Cloud CDN must be enabled on the backend service of the HTTP(S) load balancer, and the frontend must use HTTP or HTTPS because Cloud CDN only supports HTTP(S) protocols. This is the minimal configuration; no changes to the backend bucket or instance group are required beyond ensuring the backend service is correctly associated with the load balancer.
Variation 2. A company has an external HTTP(S) load balancer with a backend service pointing to an instance group in us-east1. They enable Cloud CDN to improve performance for global users. After enabling, they observe that users in Asia still experience high latency. They verify that the backend instances respond with Cache-Control headers that allow caching. What is the most likely reason for the high latency?
easy- A.The cache TTL is too short.
- B.Cloud CDN is not enabled on the correct backend.
- ✓ C.The load balancer is a regional load balancer, not a global one.
- D.The backend instances are in us-east1, too far from Asia.
Why C: Option C is correct because an external HTTP(S) load balancer that is regional (e.g., a regional external HTTP(S) load balancer) cannot serve traffic globally with low latency; it is confined to a single region. Cloud CDN caches content at edge locations, but if the load balancer itself is regional, the cache points are also regional, so users in Asia still route to us-east1 for cache misses or even for cache hits if the edge is not globally distributed. Only a global external HTTP(S) load balancer (with a global anycast IP) can leverage Cloud CDN's global edge cache locations to serve users from the nearest point of presence.
Keep practising
More PCNE practice questions
- An organization is migrating to Google Cloud and requires connectivity between their on-premises network and VPC. They p…
- A company is migrating on-premises DNS to Google Cloud. They have a hybrid network using Cloud VPN and want to resolve o…
- A network engineer is configuring a Cloud Router for BGP peering with an on-premises router over a VPN tunnel. The on-pr…
- A company uses Cloud NAT to allow private instances to reach the internet. They notice that egress traffic from Compute…
- You are setting up Partner Interconnect with a service provider that offers both Layer 2 and Layer 3 options. Your on-pr…
- Match each VPC networking concept to its definition.
Last reviewed: Jun 11, 2026
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.