How is CloudGuard for Azure licensed in BYOL (Bring your own license) mode?

Question

Options

• APer usage
• BPer Socket
• CPer vCore
• DPer Gateway

• A
  4% (2)
• B
  7% (4)
• C
  87% (48)
• D
  2% (1)

Explanation

CloudGuard for Azure in BYOL mode is licensed per vCore because Azure's virtualized infrastructure allocates compute resources as virtual cores - so Check Point ties license consumption directly to the vCores assigned to the gateway VM, allowing the license to scale with the VM size chosen.

Why the distractors are wrong:

• A (Per usage) describes the PAYG (Pay-As-You-Go) marketplace model, not BYOL - BYOL means you bring a pre-purchased license, not pay dynamically.
• B (Per Socket) is an on-premises licensing model for physical CPUs; Azure VMs have no physical sockets to count.
• D (Per Gateway) would be a flat per-instance model, but Check Point's BYOL pricing reflects VM sizing granularity, not just instance count.

Memory tip: In the cloud, "cores are currency" - BYOL Azure licensing follows the virtual compute unit (vCore), just like most Azure services bill by core count. If you remember that Azure = vCores, you'll never confuse it with the physical-world "Per Socket" model.

No community discussion yet for this question.