The intended answer isB, but the technically exact directory is usually written as$FWDIR/state/__tmp/FW1
/with a double underscore. The temporary policy directory is used when policy files are transferred to the Security Gateway before they are committed as the local installed policy. Option A, $FWDIR/state/local
/FW1, is the committed/local policy directory, not the transfer staging directory. Option C is wrong because the directory is FW1, not FW-1. Option D is wrong because $CPDIR is not the firewall policy state path used for this transfer. So use optionBfor the exam, but remember the precise technical path is__tmp, not _tmp.
========

The correct answer isA. ElasticXL automatically configures the Sync network to192.0.2.0/24. Check Point's R82 ElasticXL important notes state this directly. The Sync interfaces of all ElasticXL Cluster Members in the same cluster must connect to the same Layer 2 broadcast domain, usually a dedicated Layer 2 switch or VLAN. The Sync interface must not be configured as a VLAN trunk, and only one ElasticXL Cluster is supported in the same Layer 2 broadcast domain. Option B, 192.168.2.0/24, is a private RFC1918-style address but not the ElasticXL default. Option C, 192.0.0.0/24, is not the documented Sync network. Option D is also not correct. The OCR in the uploaded file mangles the address, but the official value is unambiguous:
ElasticXL Sync network = 192.0.2.0/24. Reference topic:ElasticXL Important Notes / Sync network automatic configuration.
========

The correct answer isD. An in-place upgrade means the existing Check Point computer is upgraded on the same machine while keeping the current configuration and database. In R82 terminology, CPUSE is used for local upgrades on supported Security Management Servers, Log Servers, Security Gateways, VSX Gateways, and related Gaia-based systems. Check Point's R82 Installation and Upgrade Guide includes separate CPUSE procedures for upgrading Security Management/Log Servers and Security Gateways, and the Release Notes describe CPUSE upgrade as a supported method that keeps the current configuration and database. Option A is too narrow because cluster members are not the only supported targets. Option B is wrong because Security Gateways can also be upgraded with CPUSE. Option C is also too narrow because upgrade support is not limited only to Management HA Primary and Secondary servers. In-place upgrade must still respect supported upgrade paths, prerequisites, backups, and production change planning, but the method is not restricted to only one device type. Reference topic:Upgrade with CPUSE / Supported Upgrade Methods.

The correct answer isD. Collision Mode means more than one Management Server is configured asActive. In this condition, the Active servers donotsynchronize with each other, even if network connectivity exists. The administrator must manually resolve the conflict by changing one Active server back to Standby from SmartConsole's Management High Availability window. When one server becomes Standby, synchronization starts and the data on that Standby server is overwritten by the remaining Active server's data. That is why this must be handled deliberately; blindly rebooting both servers or restarting Check Point services does not resolve the logical HA conflict. Option B is dangerous because Check Point explicitly says two Active servers cannot sync with each other. Option C is also wrong because daemon restarts do not decide which database is authoritative. The operational correction is to manually return the environment to a single-Active model and allow synchronization from the authoritative Active Management Server. Reference topic:High Availability Troubleshooting / Collision or HA Conflict.
========

The correct answer isA. In ElasticXL, the default Sync network is192.0.2.0/24. This network is automatically assigned for synchronization communication between ElasticXL Cluster members. Option B is a private RFC1918-style network but is not the ElasticXL default. Option C is incorrect because the third octet is wrong. Option D is also not used as the default ElasticXL Sync network. For the exam, memorize it exactly:
ElasticXL Sync default network = 192.0.2.0/24.
========