Question 1080
Original unofficial Palo Alto Networks NetSec-Architect scenario: A retailer selects new PA-Series hardware based solely on interface count without evaluating encrypted traffic mix and inspection subscriptions. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A retailer selects new PA-Series hardware based solely on interface count without evaluating encrypted traffic mix and inspection subscriptions. Governing principle: Physical port capacity is not a reliable proxy for effective inspected traffic capacity. The most defensible design response is: Size candidate hardware using representative inspected throughput, TLS sessions, application profiles and future headroom. Validation: A hardware pilot meets peak application and threat-inspection service objectives. Sustained assurance: Revisit sizing forecasts as encrypted traffic share increases
Incorrect Answers
“Use a site-specific installation and resilience checklist.” concerns the separate design topic: evaluate new pa-series hardware deployment and scoping trends. It would not fix the described weakness: a retailer selects new PA-Series hardware based solely on interface count without evaluating encrypted traffic mix and inspection subscriptions. Physical port capacity is not a reliable proxy for effective inspected traffic capacity.
This alternative is linked to the architecture category: evaluate ssl inspection sizing and deployment requirements. The actual problem is that a retailer selects new PA-Series hardware based solely on interface count without evaluating encrypted traffic mix and inspection subscriptions; the controlling distinction is: physical port capacity is not a reliable proxy for effective inspected traffic capacity.
The suggested “Track decrypted traffic share and session rates as applications evolve.” tests a different architectural concern: evaluate ssl decryption inspection and performance tradeoffs. Here, a retailer selects new PA-Series hardware based solely on interface count without evaluating encrypted traffic mix and inspection subscriptions. Physical port capacity is not a reliable proxy for effective inspected traffic capacity.