In the aggregate model, how are bandwidth allocations and interface tags applied beginning in Prisma Access 1.8?

Question

Options

• ALicense bandwidth is allocated to a CloudGenix controller; interface tags are set with a compute
• BLicense bandwidth is allocated to a compute region; interface tags are set with a CloudGenix
• CLicense bandwidth is allocated to a compute region; interface tags are set with a Prisma Access
• DLicense bandwidth is allocated to a Prisma Access location; interface tags are set with a compute

• A
  8% (2)
• B
  16% (4)
• C
  72% (18)
• D
  4% (1)

Explanation

In Prisma Access 1.8's aggregate model, license bandwidth is allocated at the compute region level (not at individual locations), and interface tags are configured using a Prisma Access location - making C the only option that correctly pairs both concepts. Option A is wrong on both counts, introducing CloudGenix (a separate SD-WAN product) as the controller for both functions. Option B reverses the tag-setting mechanism by attributing it to CloudGenix instead of Prisma Access. Option D confuses the allocation unit - bandwidth is pooled across a compute region, not pinned to a single Prisma Access location.

Memory tip: Think "Region gets the Resources (bandwidth), Prisma Access gets the Pins (interface tags)" - both alliterations match the correct pairing in option C.

No community discussion yet for this question.