McAfee Secure

Exam Code: NetSec-Architect

Exam Name: Palo Alto Networks Network Security Architect

Certification Provider: Palo Alto Networks

Corresponding Certification: Palo Alto Networks Certified Network Security Architect

Palo Alto Networks NetSec-Architect Questions & Answers

Study with Up-To-Date REAL Exam Questions and Answers from the ACTUAL Test

45 Questions & Answers with Testing Engine

"Palo Alto Networks Network Security Architect Exam", also known as NetSec-Architect exam, is a Palo Alto Networks certification exam.

Pass your tests with the always up-to-date NetSec-Architect Exam Engine. Your NetSec-Architect training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Palo Alto Networks NetSec-Architect Practice Test 102

Question 1010

Original unofficial Palo Alto Networks NetSec-Architect scenario: An AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Which test result best demonstrates that the design meets its requirement?

  1. A benchmark shows expected packet processing and recovery behavior under the selected supported configuration.
  2. A short-lived TLS workload at expected peak shows no unacceptable handshake failures or latency.
  3. A staged scientific workload meets performance requirements while unauthorized intercluster paths are denied.
  4. A stress test of adjacent workloads does not violate the firewall’s critical processing SLO.

Explanation

Correct Answer

D:

Original fictional security architecture situation: An AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Governing principle: Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size. The most defensible design response is: Define reserved compute and memory resource allocations suitable for the supported AHV deployment. Validation: A stress test of adjacent workloads does not violate the firewall’s critical processing SLO. Sustained assurance: Monitor resource contention and enforce host placement policy

Incorrect Answers

A:

The suggested “A benchmark shows expected packet processing and recovery behavior under the selected supported configuration.” tests a different architectural concern: design vm-series across esxi, kvm and ahv with resource and acceleration choices. Here, an AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.

B:

The proposed design “A short-lived TLS workload at expected peak shows no unacceptable handshake failures or latency.” addresses this related architecture topic: evaluate ssl decryption inspection and performance tradeoffs. The actual security gap is that an AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.

C:

“A staged scientific workload meets performance requirements while unauthorized intercluster paths are denied.” concerns the separate design topic: assess private-cloud edge, core and east-west microsegmentation capacity. It would not fix the described weakness: an AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.

Question 1011

Original unofficial Palo Alto Networks NetSec-Architect scenario: An AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Which architectural principle best explains the risk or behavior?

  1. Virtual switching mode affects CPU overhead, throughput and portability.
  2. Cryptographic session setup can become the limiting resource before raw bandwidth is exhausted.
  3. Inspection placement must account for internal workload throughput and permitted data dependencies.
  4. Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.

Explanation

Correct Answer

D:

Original fictional security architecture situation: An AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Governing principle: Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size. The most defensible design response is: Define reserved compute and memory resource allocations suitable for the supported AHV deployment. Validation: A stress test of adjacent workloads does not violate the firewall’s critical processing SLO. Sustained assurance: Monitor resource contention and enforce host placement policy

Incorrect Answers

A:

The proposed design “Virtual switching mode affects CPU overhead, throughput and portability.” addresses this related architecture topic: design vm-series across esxi, kvm and ahv with resource and acceleration choices. The actual security gap is that an AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.

B:

“Cryptographic session setup can become the limiting resource before raw bandwidth is exhausted.” concerns the separate design topic: evaluate ssl decryption inspection and performance tradeoffs. It would not fix the described weakness: an AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.

C:

This alternative is linked to the architecture category: assess private-cloud edge, core and east-west microsegmentation capacity. The actual problem is that an AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load; the controlling distinction is: virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.

Question 1012

Original unofficial Palo Alto Networks NetSec-Architect scenario: An AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Which continuing assurance practice best prevents recurrence?

  1. Test live migration and HA constraints before enabling acceleration.
  2. Capacity-plan using representative application traffic profiles.
  3. Monitor resource contention and enforce host placement policy.
  4. Review microsegmentation scale against storage and compute expansion.

Explanation

Correct Answer

C:

Original fictional security architecture situation: An AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Governing principle: Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size. The most defensible design response is: Define reserved compute and memory resource allocations suitable for the supported AHV deployment. Validation: A stress test of adjacent workloads does not violate the firewall’s critical processing SLO. Sustained assurance: Monitor resource contention and enforce host placement policy

Incorrect Answers

A:

“Test live migration and HA constraints before enabling acceleration.” concerns the separate design topic: design vm-series across esxi, kvm and ahv with resource and acceleration choices. It would not fix the described weakness: an AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.

B:

This alternative is linked to the architecture category: evaluate ssl decryption inspection and performance tradeoffs. The actual problem is that an AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load; the controlling distinction is: virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.

D:

The proposed design “Review microsegmentation scale against storage and compute expansion.” addresses this related architecture topic: assess private-cloud edge, core and east-west microsegmentation capacity. The actual security gap is that an AHV cluster schedules VM-Series firewalls onto hosts without the required reserved resources and the data plane degrades during noisy-neighbor load. Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.

Question 1013

Original unofficial Palo Alto Networks NetSec-Architect scenario: A customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Which architectural decision best addresses the requirement?

  1. Define reserved compute and memory resource allocations suitable for the supported AHV deployment.
  2. Compare passthrough acceleration and mobility requirements, selecting a supported architecture with tested recovery operations.
  3. Size candidate hardware using representative inspected throughput, TLS sessions, application profiles and future headroom.
  4. Separate edge and east-west inspection roles and size the latter for measured inter-tier flows.

Explanation

Correct Answer

B:

Original fictional security architecture situation: A customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Governing principle: Hardware binding can trade virtual-machine portability for lower packet overhead. The most defensible design response is: Compare passthrough acceleration and mobility requirements, selecting a supported architecture with tested recovery operations. Validation: The approved design meets packet performance goals without depending on unsupported migration behavior. Sustained assurance: Retest failover and maintenance workflows after changing virtual NIC architecture

Incorrect Answers

A:

This alternative is linked to the architecture category: design vm-series across esxi, kvm and ahv with resource and acceleration choices. The actual problem is that a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM; the controlling distinction is: hardware binding can trade virtual-machine portability for lower packet overhead.

C:

The proposed design “Size candidate hardware using representative inspected throughput, TLS sessions, application profiles and future headroom.” addresses this related architecture topic: evaluate new pa-series hardware deployment and scoping trends. The actual security gap is that a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Hardware binding can trade virtual-machine portability for lower packet overhead.

D:

“Separate edge and east-west inspection roles and size the latter for measured inter-tier flows.” concerns the separate design topic: assess private-cloud edge, core and east-west microsegmentation capacity. It would not fix the described weakness: a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Hardware binding can trade virtual-machine portability for lower packet overhead.

Question 1014

Original unofficial Palo Alto Networks NetSec-Architect scenario: A customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Which test result best demonstrates that the design meets its requirement?

  1. A stress test of adjacent workloads does not violate the firewall’s critical processing SLO.
  2. The approved design meets packet performance goals without depending on unsupported migration behavior.
  3. A hardware pilot meets peak application and threat-inspection service objectives.
  4. A representative internal database flow is inspected without exceeding edge throughput and latency budgets.

Explanation

Correct Answer

B:

Original fictional security architecture situation: A customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Governing principle: Hardware binding can trade virtual-machine portability for lower packet overhead. The most defensible design response is: Compare passthrough acceleration and mobility requirements, selecting a supported architecture with tested recovery operations. Validation: The approved design meets packet performance goals without depending on unsupported migration behavior. Sustained assurance: Retest failover and maintenance workflows after changing virtual NIC architecture

Incorrect Answers

A:

The suggested “A stress test of adjacent workloads does not violate the firewall’s critical processing SLO.” tests a different architectural concern: design vm-series across esxi, kvm and ahv with resource and acceleration choices. Here, a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Hardware binding can trade virtual-machine portability for lower packet overhead.

C:

“A hardware pilot meets peak application and threat-inspection service objectives.” concerns the separate design topic: evaluate new pa-series hardware deployment and scoping trends. It would not fix the described weakness: a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Hardware binding can trade virtual-machine portability for lower packet overhead.

D:

This alternative is linked to the architecture category: assess private-cloud edge, core and east-west microsegmentation capacity. The actual problem is that a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM; the controlling distinction is: hardware binding can trade virtual-machine portability for lower packet overhead.

Question 1015

Original unofficial Palo Alto Networks NetSec-Architect scenario: A customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Which architectural principle best explains the risk or behavior?

  1. Hardware binding can trade virtual-machine portability for lower packet overhead.
  2. Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.
  3. Physical port capacity is not a reliable proxy for effective inspected traffic capacity.
  4. East-west traffic volume and service topology can differ materially from external ingress/egress.

Explanation

Correct Answer

A:

Original fictional security architecture situation: A customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Governing principle: Hardware binding can trade virtual-machine portability for lower packet overhead. The most defensible design response is: Compare passthrough acceleration and mobility requirements, selecting a supported architecture with tested recovery operations. Validation: The approved design meets packet performance goals without depending on unsupported migration behavior. Sustained assurance: Retest failover and maintenance workflows after changing virtual NIC architecture

Incorrect Answers

B:

“Virtualized enforcement depends on guaranteed hypervisor resources, not only a nominal instance size.” concerns the separate design topic: design vm-series across esxi, kvm and ahv with resource and acceleration choices. It would not fix the described weakness: a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Hardware binding can trade virtual-machine portability for lower packet overhead.

C:

This alternative is linked to the architecture category: evaluate new pa-series hardware deployment and scoping trends. The actual problem is that a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM; the controlling distinction is: hardware binding can trade virtual-machine portability for lower packet overhead.

D:

The suggested “East-west traffic volume and service topology can differ materially from external ingress/egress.” tests a different architectural concern: assess private-cloud edge, core and east-west microsegmentation capacity. Here, a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Hardware binding can trade virtual-machine portability for lower packet overhead.

Question 1016

Original unofficial Palo Alto Networks NetSec-Architect scenario: A customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Which continuing assurance practice best prevents recurrence?

  1. Monitor resource contention and enforce host placement policy.
  2. Revisit sizing forecasts as encrypted traffic share increases.
  3. Measure per-tier traffic and revise firewall capacity after workload growth.
  4. Retest failover and maintenance workflows after changing virtual NIC architecture.

Explanation

Correct Answer

D:

Original fictional security architecture situation: A customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Governing principle: Hardware binding can trade virtual-machine portability for lower packet overhead. The most defensible design response is: Compare passthrough acceleration and mobility requirements, selecting a supported architecture with tested recovery operations. Validation: The approved design meets packet performance goals without depending on unsupported migration behavior. Sustained assurance: Retest failover and maintenance workflows after changing virtual NIC architecture

Incorrect Answers

A:

“Monitor resource contention and enforce host placement policy.” concerns the separate design topic: design vm-series across esxi, kvm and ahv with resource and acceleration choices. It would not fix the described weakness: a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Hardware binding can trade virtual-machine portability for lower packet overhead.

B:

This alternative is linked to the architecture category: evaluate new pa-series hardware deployment and scoping trends. The actual problem is that a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM; the controlling distinction is: hardware binding can trade virtual-machine portability for lower packet overhead.

C:

The suggested “Measure per-tier traffic and revise firewall capacity after workload growth.” tests a different architectural concern: assess private-cloud edge, core and east-west microsegmentation capacity. Here, a customer proposes direct hardware NIC passthrough to reduce latency but also requires frequent live migration of its firewall VM. Hardware binding can trade virtual-machine portability for lower packet overhead.

Question 1017

Original unofficial Palo Alto Networks NetSec-Architect scenario: A private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. Which architectural decision best addresses the requirement?

  1. Design justified SSL decryption inclusion/exclusion policy with alternate threat and access protections for exempt apps.
  2. Plan active usable inspection headroom and failover reserve for the projected encrypted traffic load.
  3. Benchmark realistic cipher suites, handshake rate, concurrency and small-packet inspected throughput.
  4. Recalculate capacity using measured decrypted session mixes, cryptographic algorithms and session churn.

Explanation

Correct Answer

D:

Original fictional security architecture situation: A private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. Governing principle: TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks. The most defensible design response is: Recalculate capacity using measured decrypted session mixes, cryptographic algorithms and session churn. Validation: A representative encrypted load test remains within throughput and CPU headroom targets. Sustained assurance: Track decrypted traffic share and session rates as applications evolve

Incorrect Answers

A:

This alternative is linked to the architecture category: evaluate ssl decryption inspection and performance tradeoffs. The actual problem is that a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled; the controlling distinction is: TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

B:

The suggested “Plan active usable inspection headroom and failover reserve for the projected encrypted traffic load.” tests a different architectural concern: evaluate ssl inspection sizing and deployment requirements. Here, a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

C:

The proposed design “Benchmark realistic cipher suites, handshake rate, concurrency and small-packet inspected throughput.” addresses this related architecture topic: evaluate ssl inspection sizing and deployment requirements. The actual security gap is that a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

Question 1018

Original unofficial Palo Alto Networks NetSec-Architect scenario: A private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. Which test result best demonstrates that the design meets its requirement?

  1. Documented clinical apps function through the chosen path and sanctioned test traffic remains appropriately monitored.
  2. During a staged node failure the remaining cluster retains required inspected throughput without unsafe bypass.
  3. A peak synthetic TLS workload meets session establishment and latency targets with required inspection enabled.
  4. A representative encrypted load test remains within throughput and CPU headroom targets.

Explanation

Correct Answer

D:

Original fictional security architecture situation: A private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. Governing principle: TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks. The most defensible design response is: Recalculate capacity using measured decrypted session mixes, cryptographic algorithms and session churn. Validation: A representative encrypted load test remains within throughput and CPU headroom targets. Sustained assurance: Track decrypted traffic share and session rates as applications evolve

Incorrect Answers

A:

The suggested “Documented clinical apps function through the chosen path and sanctioned test traffic remains appropriately monitored.” tests a different architectural concern: evaluate ssl decryption inspection and performance tradeoffs. Here, a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

B:

The proposed design “During a staged node failure the remaining cluster retains required inspected throughput without unsafe bypass.” addresses this related architecture topic: evaluate ssl inspection sizing and deployment requirements. The actual security gap is that a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

C:

“A peak synthetic TLS workload meets session establishment and latency targets with required inspection enabled.” concerns the separate design topic: evaluate ssl inspection sizing and deployment requirements. It would not fix the described weakness: a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

Question 1019

Original unofficial Palo Alto Networks NetSec-Architect scenario: A private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. Which architectural principle best explains the risk or behavior?

  1. Inspection benefit must be balanced against protocol incompatibility and regulated content handling.
  2. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.
  3. Standby resources cannot be counted as routine growth capacity if needed for high-availability recovery.
  4. SSL inspection performance is affected by workload shape as well as aggregate bandwidth.

Explanation

Correct Answer

B:

Original fictional security architecture situation: A private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. Governing principle: TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks. The most defensible design response is: Recalculate capacity using measured decrypted session mixes, cryptographic algorithms and session churn. Validation: A representative encrypted load test remains within throughput and CPU headroom targets. Sustained assurance: Track decrypted traffic share and session rates as applications evolve

Incorrect Answers

A:

The proposed design “Inspection benefit must be balanced against protocol incompatibility and regulated content handling.” addresses this related architecture topic: evaluate ssl decryption inspection and performance tradeoffs. The actual security gap is that a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

C:

This alternative is linked to the architecture category: evaluate ssl inspection sizing and deployment requirements. The actual problem is that a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled; the controlling distinction is: TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

D:

The suggested “SSL inspection performance is affected by workload shape as well as aggregate bandwidth.” tests a different architectural concern: evaluate ssl inspection sizing and deployment requirements. Here, a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

Question 1020

Original unofficial Palo Alto Networks NetSec-Architect scenario: A private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. Which continuing assurance practice best prevents recurrence?

  1. Review exceptional no-decrypt rules and owners on a fixed schedule.
  2. Track decrypted traffic share and session rates as applications evolve.
  3. Forecast steady-state and degraded-state SSL inspection utilization separately.
  4. Maintain representative encrypted traffic test profiles for refresh planning.

Explanation

Correct Answer

B:

Original fictional security architecture situation: A private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. Governing principle: TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks. The most defensible design response is: Recalculate capacity using measured decrypted session mixes, cryptographic algorithms and session churn. Validation: A representative encrypted load test remains within throughput and CPU headroom targets. Sustained assurance: Track decrypted traffic share and session rates as applications evolve

Incorrect Answers

A:

“Review exceptional no-decrypt rules and owners on a fixed schedule.” concerns the separate design topic: evaluate ssl decryption inspection and performance tradeoffs. It would not fix the described weakness: a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

C:

The suggested “Forecast steady-state and degraded-state SSL inspection utilization separately.” tests a different architectural concern: evaluate ssl inspection sizing and deployment requirements. Here, a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

D:

The proposed design “Maintain representative encrypted traffic test profiles for refresh planning.” addresses this related architecture topic: evaluate ssl inspection sizing and deployment requirements. The actual security gap is that a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.

Palo Alto Networks Network Security Architect (NetSec-Architect) Practice Tests