Question 180
As part of architectural change control for this problem: TLS-rich ecommerce traffic is sized from average network Mbps without considering peak new handshakes. Which preventive check should be required?
Explanation
Correct Answer
Review seasonal handshake bursts and decryption error rates before peak season. This lowers the risk linked to: TLS connections per second and cryptographic work can dominate even at moderate average bandwidth. Verification should show: Peak synthetic TLS load meets new-session and latency objectives without inspection gaps.
Incorrect Answers
Maintain workload-realistic sizing tests for the approved platform. This safeguard addresses another situation: A mixed traffic profile contains small encrypted requests with high connection churn, but the firewall model was selected using large-packet benchmark rates. It is less directly relevant than the control for: TLS connections per second and cryptographic work can dominate even at moderate average bandwidth.
Retest performance whenever new inspection profiles or decryption policies are enabled. This safeguard addresses another situation: A design adds DLP and advanced threat inspection to decrypted traffic but keeps the same capacity margin as an uninspected baseline. It is less directly relevant than the control for: TLS connections per second and cryptographic work can dominate even at moderate average bandwidth.
Reassess service growth, interface speeds and environmental limits annually. This safeguard addresses another situation: A data center considers a new PA-Series generation solely because its raw advertised throughput is higher. It is less directly relevant than the control for: TLS connections per second and cryptographic work can dominate even at moderate average bandwidth.