PCNSA Device Management and Services Practice Question
After enabling password complexity on a Palo Alto firewall, an administrator is unable to access the management web interface remotely. The administrator can still access the console locally. What is the most likely cause?
⚠ Common exam trap
A common mix-up: candidates assume password complexity only affects future password changes, not the current password, and overlook the commit failure and configuration rollback that can disable remote management access.
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 administrator's account is locked due to too many failed login attempts.
The most likely cause is account lockout due to multiple failed login attempts from remote access. When an administrator attempts to access the web interface with incorrect credentials, the firewall locks the account after a configured number of failures. However, local console access may still work if the account lockout policy does not apply to console sessions or if the console uses a different authentication mechanism. Therefore, option B is the most plausible explanation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Password complexity automatically disables HTTPS management.
Why it's wrong here
Password complexity does not automatically disable HTTPS management. This is incorrect.
- ✓
The administrator's account is locked due to too many failed login attempts.
Why this is correct
The account is locked due to too many failed login attempts. This is the most likely cause because the remote web interface is inaccessible but local console still works, as console authentication may be unaffected by lockout settings.
- ✗
The password does not meet the new complexity requirements, causing the commit to fail and revert the management configuration.
Why it's wrong here
Enabling password complexity does not cause a commit failure or revert management configuration. This is factually incorrect.
- ✗
HTTPS management is automatically disabled when password complexity is enabled.
Why it's wrong here
HTTPS management is not automatically disabled when password complexity is enabled. This is incorrect.
Go deeper
Related to this question
About these practice questions
This PCNSA question is part of Courseiva's 516-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 PCNSA 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 PCNSA exam.