How to Restrict SSH and HTTPS Management Access to a Trusted Subnet
A help desk ticket reports that a user cannot access the firewall's web management interface (HTTPS) from the management network. The management interface is on a dedicated MGMT network. Which setting must be enabled on the firewall to allow this access?
⚠ Common exam trap
Many exam-takers confuse management access control with service routes or dataplane features, assuming that being on the same MGMT network is sufficient, but the firewall explicitly blocks all management protocol access by default unless the source IP is permitted.
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
✓
Under Device > Setup > Management, add the user's IP or subnet to 'Permitted IP Addresses' for HTTPS.
The firewall's management interface enforces an access control list for HTTPS (and other management protocols) under Device > Setup > Management. By default, no IP addresses are permitted, so even if the user is on the same MGMT network, the firewall will drop HTTPS requests unless the user's IP or subnet is explicitly added to the 'Permitted IP Addresses' list. This setting is a fundamental security measure to restrict management access to trusted sources only.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable IKE on the management interface.
Why it's wrong here
IKE negotiates IPsec VPN tunnels and has no bearing on HTTPS access to the web management interface. It tempts when management access traverses an IPsec tunnel, but the user is on the directly connected MGMT network, so no tunnel negotiation is involved.
- ✗
Enable User-ID on the management interface.
Why it's wrong here
User-ID maps source IP addresses to usernames for policy enforcement; it does not open HTTPS access to the management interface. It tempts because User-ID is commonly enabled for management-plane policy, yet the reported symptom is simple connectivity, not identity-based authorisation.
- ✗
Configure a service route to redirect management traffic to a dataplane interface.
Why it's wrong here
A service route moves management-plane traffic onto a dataplane interface, which is unnecessary when the user already sits on the dedicated MGMT network. It is tempting for reaching management services across other interfaces, but here the correct setting permits HTTPS on the management interface itself.
- ✓
Under Device > Setup > Management, add the user's IP or subnet to 'Permitted IP Addresses' for HTTPS.
Why this is correct
Adding the user's subnet to Permitted IP Addresses under Device > Setup > Management restricts HTTPS management access to explicitly listed sources, satisfying the dedicated MGMT network constraint. Without this entry, the firewall silently drops management-plane traffic from unlisted addresses, so the help desk user is denied despite correct routing and policy.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 319 original PCNSE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.