PCNSE Securing Traffic and App-ID Practice Question
A security engineer is troubleshooting why a web application is not being identified correctly. The firewall shows the session as 'ssl' instead of the specific application. The engineer has verified that the traffic is using TLS 1.3. What is the most likely reason for the misidentification?
⚠ Common exam trap
The trap here is assuming that App-ID can identify applications inside encrypted traffic without decryption, but encryption hides the application signatures, so only ssl is identified.
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
✓
SSL decryption is not configured for the traffic.
SSL decryption is required to inspect encrypted traffic and identify the application inside. Without decryption, the firewall can only classify the session as ssl based on the protocol, not the specific application. This is particularly relevant for TLS 1.3, where more of the handshake is encrypted, making decryption even more critical for accurate App-ID.
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 application uses a non-standard port.
Why it's wrong here
App-ID can identify applications on non-standard ports if the traffic is not encrypted. However, if the traffic is encrypted, the port is irrelevant because the firewall cannot see the application data. The use of a non-standard port alone would not cause misidentification as ssl; the encryption is the primary factor.
- ✗
The security policy does not allow the application.
Why it's wrong here
If the security policy did not allow the application, the traffic would be blocked, not misidentified. The session would show as denied. The fact that it is allowed but identified as ssl indicates that the firewall cannot see inside the encrypted traffic to identify the application, not a policy issue.
- ✓
SSL decryption is not configured for the traffic.
Why this is correct
Without SSL decryption, the firewall cannot inspect the encrypted payload and can only identify the traffic as ssl based on the port or protocol. To identify the specific application inside TLS, the firewall must decrypt the traffic. This is especially true for TLS 1.3, where more of the handshake is encrypted, making it harder to identify the application without decryption.
- ✗
The firewall does not support TLS 1.3 inspection.
Why it's wrong here
Palo Alto Networks firewalls support TLS 1.3, including decryption and inspection. However, TLS 1.3 introduces changes like encrypted handshake certificates, which can affect identification if not properly decrypted. The issue is not lack of support but rather the absence of decryption, leading to inability to see the application data.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PCNSE question from scratch — 319 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Palo Alto Networks exam blueprint
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.