156-541 Sample Questions & Answers

Multi-Domain Installation and Configuration · Component functions and interaction

• A

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

• B

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

• C

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

• D

  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.

Multi-Domain Installation and Configuration · Implementing Multi-Domain Management High Availability

• A

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

• B

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

• C

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

• D

  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.

Multi-Domain Troubleshooting · MDS configuration changes and debugging

• A

  vsys_change

• B

  chcontext

• C

  set_domain

• D

  mdsenv

Multi-Domain Installation and Configuration · MDSM installation and configuration

• A

  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.

• B

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

• C

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

• D

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

Multi-Domain Installation and Configuration · Implementing Multi-Domain Management High Availability

• A

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

• B

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

• C

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

• D

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

Multi-Domain Installation and Configuration · Implementing Multi-Domain Management High Availability

• A

  View the security policy, network objects, and logs in a read-only capacity.

• B

  Create new network objects to prepare for policy updates once the Primary DMS returns.

• C

  Install an existing, unmodified policy to the Security Gateways managed by the domain.

• D

  Revoke and reissue the SIC certificates for all managed gateways.

Multi-Domain Installation and Configuration · Migrating an SMS to a Domain Management Server

• A

  The free disk space must be at least 5 times the size of the exported database file.

• B

  Create the target Domain and Domain Management Server in SmartConsole before running migrate-import-domain.

• C

  Delete all global objects from the Global Domain so they cannot conflict with imported objects.

• D

  Run 'cp_merge override' on the MDS so the SMS objects overwrite existing global objects.

Multi-Domain Installation and Configuration · Implementing Multi-Domain Management High Availability

• A

  The MDS-level configuration (Administrators, GUI clients, Domain definitions).

• B

  The Global Domain database (Global policies and objects).

• C

  Gaia OS routing tables and interface IP configurations.

• D

  Core dump files generated by crashed processes.

• E

  Traffic logs generated by all Security Gateways.

Global Domain Global Policy Management · Global Policy in a distributed network

• A

  To create and manage objects, policies, and settings that can be shared and enforced across multiple local domains.

• B

  To aggregate all traffic logs from every Domain Log Server into a single searchable database.

• C

  To act as the default catch-all domain for any gateways that lose communication with their assigned DMS.

• D

  To provide a web-based portal for end-users to authenticate to the VPN.

Global Domain Global Policy Management · Global Policy in a distributed network

• A

  Global rules are merged directly into the local layer, replacing any local rules that have the same source and destination.

• B

  Global rules are placed above and/or below a single placeholder (Domain Layer) that holds the local Domain rules; the position of the placeholder, set in the Global Domain, determines the enforcement order.

• C

  Global Policy layers completely override and disable local policy layers to ensure strict corporate compliance.

• D

  The local domain administrator must manually drag and drop the global rules into their preferred positions within the local layer.