The Cortex Data Lake sizing calculator for Prisma Access requires which three values as inputs? (Choose three.)

Question

Options

• Athroughput of remote networks purchased
• Bcloud-managed or Panorama-managed deployment
• Cretention period for the logs to be stored
• Dnumber of log-forwarding destinations
• Enumber of mobile users purchased

• A
  90% (28)
• B
  6% (2)
• D
  3% (1)

Explanation

When sizing Cortex Data Lake for Prisma Access, the calculator needs to know how much traffic is flowing (throughput of remote networks, option A), how long logs must be kept (retention period, option C), and how many mobile users are licensed (option E) - together these determine total log volume and storage duration.

Why the distractors are wrong:

• B (cloud-managed vs. Panorama-managed): The management plane choice doesn't affect how much log data is generated or how long it's stored - it's an architectural preference, not a sizing input.
• D (number of log-forwarding destinations): Where logs are sent is irrelevant to how much storage Cortex Data Lake itself requires; the volume of logs stays the same regardless of how many destinations receive them.

Memory tip: Think "Who, How Much, How Long" - who is connecting (mobile users), how much traffic they generate (remote network throughput), and how long you need to keep the evidence (retention period). These three factors directly drive storage capacity, making them the natural inputs to any sizing calculator.

No community discussion yet for this question.