When configuring a new Virtual System for your VSX Gateway configuration, what should you do first?

Question

Options

• AOpen the Admin CMA SmartDashboard and create a new Virtual System object
• BOpen the Global SmartDashboard and create a new Virtual System object
• COpen the Admin CMA SmartDashboard and create a new CMA object to be used as the Virtual
• DCreate a new Customer and CMA, to be used as the Virtual System's Management Server
• EAdd a new Virtual System to the Main Customer, so that the Admin CMA can be used as the

• A
  7% (3)
• B
  2% (1)
• C
  15% (6)
• D
  73% (30)
• E
  2% (1)

Explanation

D is correct because in a Check Point Multi-Domain Security Management (MDSM) environment, a Virtual System requires a dedicated management domain before it can exist as a managed object. Creating the Customer (domain) and its associated CMA (Customer Management Add-on) first establishes the management infrastructure - the CMA becomes the management server that will own and control the Virtual System's policy.

Why the distractors fail:

• A & C are wrong because the Admin CMA SmartDashboard is a shared administrative tool, not the right place to create a new Virtual System object or a new CMA - CMAs are provisioned at the MDS level, not from within another CMA.
• B is wrong because the Global SmartDashboard is used for global policies and objects, not for provisioning new Virtual Systems within a specific customer domain.
• E is wrong because assigning a Virtual System to the Main Customer and using the Admin CMA as its manager conflates administrative infrastructure with per-customer management - each VS needs its own dedicated CMA/Customer pair.

Memory tip: Think "house before furniture" - you must build the management house (Customer + CMA) before you can place the Virtual System object inside it. The CMA is the management server; without it, there's nowhere for the VS to live.

No community discussion yet for this question.