PCNSE Core Concepts and Architecture Practice Question
A security engineer wants to identify applications in SSL/TLS encrypted traffic without decrypting the payload. Which method can be used?
⚠ Common exam trap
Many exam-takers assume application identification in encrypted traffic always requires decryption, overlooking that metadata from the TLS handshake can be used for identification without breaking encryption.
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
✓
Use App-ID's encrypted traffic detection capabilities
App-ID's encrypted traffic detection capabilities allow the firewall to identify applications within SSL/TLS encrypted flows without decrypting the payload. It uses techniques such as server name indication (SNI) inspection, certificate field analysis, and JA3/JA3S fingerprinting to match traffic to known applications, even when the content is encrypted.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Deploy a network tap to capture traffic
Why it's wrong here
A network tap captures ciphertext, so application identification remains impossible without decryption or metadata analysis. It is tempting because passive capture avoids interfering with traffic, and would be correct for analysing unencrypted protocols or troubleshooting packet-level issues.
- ✓
Use App-ID's encrypted traffic detection capabilities
Why this is correct
App-ID inspects TLS handshake metadata — server name indication, certificate fields and JA3 fingerprints — plus packet patterns, identifying the application without decrypting payload. This satisfies the requirement to classify encrypted traffic while preserving privacy and avoiding decryption overhead.
- ✗
Configure the firewall to trust all certificates
Why it's wrong here
Trusting all certificates disables validation and yields no application identification data from the encrypted session. It is tempting because it removes certificate errors blocking inspection, and would be correct only for lab testing where certificate validation is deliberately bypassed.
- ✗
Implement SSL Forward Proxy decryption
Why it's wrong here
SSL Forward Proxy decryption terminates and inspects the payload, directly contradicting the requirement to avoid decryption. It is tempting because it gives full application visibility, and would be correct when policy permits decryption and privacy or legal constraints do not prohibit it.
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 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.