Check Point Certified Multi-Domain Security Management Specialist - R81 (CCMS) Free Sample Questions

The MDS is responsible for compiling and installing security policies directly to gateways, while the DMS acts only as a centralized repository for audit logs.

The MDS provides the overarching administrative environment and global resources, whereas the DMS functions as an independent virtual Security Management Server for a specific subsidiary.

The DMS provides the global management framework across all subsidiaries, while the MDS instances are deployed locally at each subsidiary to enforce routing rules.

The MDS and DMS are identical components used interchangeably; the terminology only changes based on whether the appliance is physical or virtual.

The migrate-export-domain Management API (mgmt_cli -d "System Data" migrate-export-domain)

mds_backup

migrate_server

cma_migrate

Log into the Global Domain on MDS-B, promote MDS-B to Primary Active, reassign the Global Policy to the Payments domain, and push the policy to the European gateways.

Connect SmartConsole to the Standby Payments DMS on MDS-B, open Menu > Management High Availability and click Actions > Set Active, then add the rule and install the policy.

SSH into MDS-B, run the 'mds_promote -d Payments' command to force the Secondary DMS to become primary, restart the FWM process, and connect SmartConsole.

Connect to the European gateways via SSH and use 'fw fetch local' to pull the cached policy from the Secondary DMS, bypassing SmartConsole entirely.

It is not possible to install policies when the Primary DMS is down. The administrator must wait for MDS-A to recover before any rules can be modified.

Create a new Domain object in the SmartConsole connected to the MDS.

Configure an IP address for the Domain Management Server (DMS).

Assign a dedicated physical NIC on the MDS appliance exclusively for the new DMS.

Define a Trusted Client for the Domain to allow SmartConsole connections.

Run the 'cpconfig' utility on the MDS to allocate memory to the new Domain.

True

False

A Domain Log Server only stores audit logs for administrators, while the MLM stores traffic logs generated by the Security Gateways.

A Multi-Domain Log Server (MLM) can host multiple virtual log servers for different domains on a single appliance, whereas a standard Domain Log Server is a dedicated standalone appliance for a single domain.

An MLM automatically forwards all logs to SmartEvent, while a Domain Log Server requires manual configuration to enable event correlation.

The MLM is installed automatically as part of the Global Domain, whereas Domain Log Servers must be licensed and purchased separately.

The Secondary MDS has run out of disk space and cannot accept new database revisions.

During a network partition, the Standby (Global) Domain Server was made Active while the other was still Active, and changes were made on both, so more than one server is Active.

The FWD process on the Secondary MDS has stopped responding, preventing SIC communication.

The Global Policy was deployed with overlapping IP space across two different domains.

set_domain

mdsenv

chcontext

vsys_change

The MDS uses a hypervisor to create full Virtual Machines for each DMS, requiring dedicated, isolated RAM per domain.

Each Domain Management Server (DMS) runs as a separate set of processes (like FWM and FWD) sharing the underlying Gaia OS kernel and physical resources.

The Global Domain reserves 50% of all physical resources exclusively, leaving the remainder to be divided equally among local domains.

Resource allocation is entirely managed by the connected Security Gateways, which offload processing power back to the MDS.

Global Domain synchronization is handled by the fwd process and occurs out-of-band over a dedicated UDP broadcast channel.

Synchronization at the MDS level automatically includes the synchronization of all local Domain Management Server (DMS) databases simultaneously.

The Global Domain database synchronizes independently between the Primary and Secondary MDS, acting essentially as its own internal management server for HA purposes.

Global Domain changes are not synchronized; they must be manually exported and imported to the Secondary MDS after every change.