Which three known variables can assist with sizing an NGFW appliance?

When sizing a Palo Alto Networks NGFW appliance, it's crucial to consider variables that affect its performance and capacity. These include the network's traffic characteristics, application requirements, and expected workloads. Below is the analysis of each option:

Option A: Connections per second

Connections per second (CPS) is a critical metric for determining how many new sessions the firewall can handle per second. High CPS requirements are common in environments with high traffic turnover, such as web servers or applications with frequent session terminations and creations.

This is an important sizing variable.

Option B: Max sessions

Max sessions represent the total number of concurrent sessions the firewall can support. For environments with a large number of users or devices, this metric is critical to prevent session exhaustion.

This is an important sizing variable.

Option C: Packet replication

Packet replication is used in certain configurations, such as TAP mode or port mirroring for traffic inspection. While it impacts performance, it is not a primary variable for firewall sizing as it is a specific use case.

This is not a key variable for sizing.

Option D: App-ID firewall throughput

App-ID throughput measures the firewall's ability to inspect traffic and apply policies based on application signatures. It directly impacts the performance of traffic inspection under real-world conditions.

This is an important sizing variable.

Option E: Telemetry enabled

While telemetry provides data for monitoring and analysis, enabling it does not significantly impact the sizing of the firewall. It is not a core variable for determining firewall performance or capacity.

This is not a key variable for sizing.

References:

Palo Alto Networks documentation on Firewall Sizing Guidelines

Knowledge Base article on Performance and Capacity Sizing