New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Palo Alto Networks PSE-Strata-Pro-24 Exam - Topic 3 Question 16 Discussion

Actual exam question for Palo Alto Networks's PSE-Strata-Pro-24 exam
Question #: 16
Topic #: 3
[All PSE-Strata-Pro-24 Questions]

Which three known variables can assist with sizing an NGFW appliance? (Choose three.)

Show Suggested Answer Hide Answer
Suggested Answer: A, B, D

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.


Palo Alto Networks documentation on Firewall Sizing Guidelines

Knowledge Base article on Performance and Capacity Sizing

Contribute your Thoughts:

0/2000 characters
Cammy
2 months ago
Totally agree with A, B, and D!
upvoted 0 times
...
Jerlene
2 months ago
Wait, is telemetry really a factor?
upvoted 0 times
...
Graciela
2 months ago
A and B are must-haves for sizing!
upvoted 0 times
...
Kristofer
3 months ago
Definitely A, B, and D!
upvoted 0 times
...
Judy
3 months ago
I thought packet replication was important too?
upvoted 0 times
...
Caprice
3 months ago
I'm a bit confused about telemetry enabled—does that really factor into sizing an NGFW?
upvoted 0 times
...
Zana
3 months ago
App-ID firewall throughput sounds familiar; I think we practiced a question like this in class.
upvoted 0 times
...
Carmela
4 months ago
I think max sessions is definitely one of the variables, but I can't recall if packet replication is relevant.
upvoted 0 times
...
Hayley
4 months ago
I remember connections per second being important for sizing, but I'm not sure about the other two.
upvoted 0 times
...
Bonita
4 months ago
This is a classic NGFW sizing question. Connections per second, max sessions, and App-ID throughput are the key variables I'd focus on. Easy points if you know your stuff.
upvoted 0 times
...
Carin
4 months ago
Wait, what's the difference between connections per second and max sessions? I want to make sure I understand these concepts before selecting the answers.
upvoted 0 times
...
Nohemi
4 months ago
Okay, let's see here. Connections per second, max sessions, and App-ID throughput seem like the obvious choices. I'll mark those and move on.
upvoted 0 times
...
Viola
5 months ago
Hmm, not sure about packet replication - does that really factor into NGFW sizing? I'll double-check the options and go with the most relevant ones.
upvoted 0 times
...
Clemencia
5 months ago
This looks like a straightforward question on NGFW sizing. I'll focus on the key variables like connections per second, max sessions, and App-ID throughput.
upvoted 0 times
...
Dorothy
5 months ago
I believe E could also be important. Telemetry enabled can provide valuable data for sizing the NGFW appliance.
upvoted 0 times
...
Gennie
5 months ago
Hmm, I'd go with A, B, and D. Can't go wrong with the classics. Although I did hear a rumor that E stands for 'Eating Tacos', which would be a pretty cool feature.
upvoted 0 times
...
Mozell
5 months ago
I agree with Gilma. Connections per second, max sessions, and App-ID firewall throughput are crucial for sizing.
upvoted 0 times
...
Marshall
5 months ago
C? Really? Packet replication? That's just silly. A, B, and D are the obvious answers.
upvoted 0 times
...
Matilda
5 months ago
I think A, B, and E are the right choices. Telemetry can provide valuable insights for sizing.
upvoted 0 times
Roselle
1 month ago
I’d go with A, B, and C for sure.
upvoted 0 times
...
Margot
2 months ago
A, B, and E make sense for sizing. Telemetry is key!
upvoted 0 times
...
Lura
2 months ago
I think A, B, and D are the best options.
upvoted 0 times
...
Samira
2 months ago
I agree with A and B, but E seems less relevant.
upvoted 0 times
...
...
Gilma
5 months ago
I think A, B, and D are the variables that can assist with sizing an NGFW appliance.
upvoted 0 times
...
Fletcher
6 months ago
Definitely A, B, and D. These are the key performance metrics to size an NGFW appliance.
upvoted 0 times
Carline
5 months ago
D) App-ID firewall throughput
upvoted 0 times
...
Sherill
5 months ago
B) Max sessions
upvoted 0 times
...
Reita
5 months ago
A) Connections per second
upvoted 0 times
...
...

Save Cancel