Which two statements apply to features of aggregate bandwidth allocation in Prisma Access for remote networks? (Choose two.)

Question

Options

• AAdministrator can allocate up to 120% of the total bandwidth purchased for aggregate locations to
• BAdministrator must assign a minimum of 50 MB to any compute location that will support remote
• CAdministrator is not required to allocate all purchased bandwidth to compute locations for the
• DBandwidth that is allocated to a compute location is statically and evenly distributed across

• A
  77% (30)
• B
  8% (3)
• D
  15% (6)

Explanation

Prisma Access aggregate bandwidth allocation gives administrators intentional flexibility: they can over-subscribe by allocating up to 120% of total purchased bandwidth across compute locations (A), which is useful when not all locations are expected to hit peak usage simultaneously. Additionally, administrators have the freedom to leave bandwidth unallocated-there is no requirement to distribute every purchased megabit to a compute location (C), making incremental rollouts practical.

Option B is wrong because the stated minimum of 50 Mbps is incorrect-Prisma Access enforces a minimum of 300 Mbps per compute location, making B both factually wrong on the number and misleading in its framing.

Option D is wrong because allocated bandwidth is not statically or evenly distributed across remote network connections; Prisma Access dynamically shares capacity across connections within a compute location rather than carving it into fixed equal slices.

Memory tip: Think of aggregate bandwidth like a hotel overbooking policy-you can sell more rooms than you have (120% over-subscription = A), and you don't have to fill every room on opening day (partial allocation = C). Static/even splitting (D) is the opposite of the dynamic pooling model Prisma Access uses.

No community discussion yet for this question.