GlobalProtect Location Awareness: Fix Outdated Database Causing Wrong Gateway Assignment
An organization uses GlobalProtect with multiple gateways for different regions. Users in the Asia region are connecting to the wrong gateway. What is the most likely cause?
⚠ Common exam trap
It's easy for candidates to confuse gateway priority (which controls load balancing within a region) with gateway selection rules (which control which region's gateway a user connects to), leading them to incorrectly choose Option B.
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
✓
The gateway selection rules on the portal do not match the users' source IP ranges.
GlobalProtect gateway selection is primarily determined by the gateway selection rules configured on the portal. These rules evaluate the user's source IP address against defined IP ranges (or countries) to assign the appropriate gateway. If the rules do not match the users' source IP ranges in the Asia region, the portal will either fail to assign a gateway or assign a default gateway, causing users to connect to the wrong gateway.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Users are manually selecting the wrong gateway from the client.
Why it's wrong here
Manual gateway selection is possible, but GlobalProtect clients normally connect to the gateway returned by the portal's gateway list, so a region-wide pattern points to configuration rather than individual user choices. Manual selection matters when users must override automatic gateway assignment deliberately.
- ✗
The gateways are not configured with priority settings.
Why it's wrong here
Gateway priority orders which gateway a client prefers when several are offered, but it does not decide which gateways the portal advertises to a given region; that comes from the portal agent's gateway configuration and source-region matching. Priority is correct when ranking multiple gateways already presented to the same client.
- ✓
The gateway selection rules on the portal do not match the users' source IP ranges.
Why this is correct
Gateway selection rules on the portal map source IP ranges to preferred gateways, so mismatched ranges send Asian users to the wrong region. The portal agent config evaluates these rules before the client connects, making the source-IP match the deciding factor here.
- ✗
The DNS resolution for the portal returns multiple IPs in round-robin.
Why it's wrong here
Round-robin DNS affects how the portal hostname resolves, not which gateway the client subsequently selects; gateway choice follows the portal's gateway list and client region settings. Round-robin is correct when distributing portal connection load across multiple portal instances.
Go deeper
Related to this question
About these practice questions
This PCNSE question is part of Courseiva's 319-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PCNSE practice question is part of Courseiva's free Palo Alto Networks 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 PCNSE exam.