PCNSE Manage, Monitor and Operate Practice Question
Exhibit
Refer to the exhibit. set shared gateway "Corp-Gateway" authentication method "client-certificate" set shared gateway "Corp-Gateway" client-config dns-server "8.8.8.8" set shared gateway "Corp-Gateway" client-config ip-pool "10.250.0.1-10.250.0.254" set shared gateway "Corp-Gateway" tunnel-config ipsec-crypto "AES256-SHA256-DH5"
A GlobalProtect gateway is configured as shown. Remote users report that they can connect to the gateway but cannot authenticate. The users are using the GlobalProtect client with certificate authentication. What is the most likely cause?
⚠ Common exam trap
Candidates often assume the connection success (tunnel established) means authentication should work, but certificate authentication requires a separate trust validation step that fails if the root CA is not imported on the gateway.
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 does not have a root CA certificate imported for validating client certificates.
For certificate-based authentication, the GlobalProtect gateway must trust the certificate presented by the client. This requires the gateway to have the root CA certificate that issued the client certificate imported into its trusted CA list. Without this root CA, the gateway cannot validate the client's certificate chain, causing authentication to fail even though the initial connection (e.g., IPSec tunnel establishment) succeeds.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The IPSec crypto profile is too strong for the clients.
Why it's wrong here
Crypto profile mismatch would cause tunnel failure, not authentication failure within an established connection.
- ✗
The IP pool is exhausted.
Why it's wrong here
IP pool exhaustion would prevent client from obtaining an IP, but authentication would still succeed.
- ✗
The DNS server is misconfigured, causing authentication failure.
Why it's wrong here
DNS server is used by clients for name resolution, not for authentication.
- ✓
The gateway does not have a root CA certificate imported for validating client certificates.
Why this is correct
Client certificate validation requires the gateway to trust the issuing CA.
Visual reference
Quick reference
VPN Protocol Comparison
| Protocol | Port | Encryption | Authentication | Use Case |
|---|---|---|---|---|
| IKEv2 / IPsec | UDP 500 / 4500 | AES-256 | Certificates / PSK | Site-to-site & remote access |
| SSL / TLS VPN | TCP 443 | TLS 1.3 | Certificates / MFA | Clientless remote access |
| L2TP / IPsec | UDP 1701 | AES (IPsec) | PSK / Certificates | Legacy remote access |
| WireGuard | UDP 51820 | ChaCha20 | Public keys | Modern high-performance VPN |
| PPTP | TCP 1723 | MPPE (weak) | MS-CHAPv2 | Legacy — avoid in production |
PPTP is considered insecure. IKEv2/IPsec and SSL VPN are the current recommended options.
Go deeper
Related to this question
About these practice questions
This PCNSE question is part of Courseiva's 504-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.