Free 156-315.81 Exam Braindumps
Check Point Certified Security Expert R81 Questions 246–250 (page: 51)

Updated On: 10-Feb-2026

Please choose the path to monitor the compliance status of the Check Point R81.20 based management.

  1. Gateways & Servers --> Compliance View
  2. Compliance blade not available under R81.20
  3. Logs & Monitor --> New Tab --> Open compliance View
  4. Security & Policies --> New Tab --> Compliance View

Answer(s): C

Explanation:

The path to monitor the compliance status of the Check Point R81.20 based management is Logs & Monitor > New Tab > Open compliance View. Compliance View is a feature that allows administrators to monitor and assess the compliance level of their Check Point products and security policies based on best practices and industry standards. Compliance View provides a dashboard that shows the overall compliance status, compliance score, compliance trends, compliance issues, compliance reports, and compliance blades for different security aspects, such as data protection, threat prevention, identity awareness, etc. To access Compliance View in R81.20 SmartConsole, administrators need to go to Logs & Monitor > New Tab > Open compliance View. The other options are either incorrect or not available in R81.20.



When using CPSTAT, what is the default port used by the AMON server?

  1. 18191
  2. 18192
  3. 18194
  4. 18190

Answer(s): B

Explanation:

The default port used by the AMON server when using CPSTAT is 18192. CPSTAT is a command-line tool that allows administrators to monitor various statistics and status information about Check Point products and components, such as CPU usage, memory usage, policy installation, cluster state, etc. CPSTAT uses AMON (Advanced Monitoring) protocol to communicate with AMON server, which is a daemon that runs on Security Gateways or Management Servers and collects and provides AMON data. By default, AMON server listens on TCP port 18192 for incoming CPSTAT requests.



What must you do first if "fwm sic_reset" could not be completed?

  1. Cpstop then find keyword "certificate" in objects_5_0.C and delete the section
  2. Reinitialize SIC on the security gateway then run "fw unloadlocal"
  3. Reset SIC from Smart Dashboard
  4. Change internal CA via cpconfig

Answer(s): D

Explanation:

The first thing that must be done if "fwm sic_reset" could not be completed is to change internal CA via cpconfig. Fwm sic_reset is a command that allows administrators to reset Secure Internal Communication (SIC) between Security Management Server and Security Gateways or other Check Point modules. SIC is a mechanism that ensures secure and authenticated communication between Check Point components by using certificates issued by an internal Certificate Authority (ICA). If fwm sic_reset fails, it means that there is a problem with the ICA or the certificates that prevents SIC from being reset. To resolve this problem, administrators need to change internal CA via cpconfig, which is a command that allows administrators to configure various settings on Security Gateways or Management Servers, including the ICA. Changing internal CA via cpconfig will create a new ICA with a new certificate, and allow SIC to be reset with the new certificate.



Check Point security components are divided into the following components:

  1. GUI Client, Security Gateway, WebUI Interface
  2. GUI Client, Security Management, Security Gateway
  3. Security Gateway, WebUI Interface, Consolidated Security Logs
  4. Security Management, Security Gateway, Consolidate Security Logs

Answer(s): B

Explanation:

Check Point security components are divided into the following components: GUI Client, Security Management, Security Gateway. GUI Client is the graphical user interface that allows administrators to configure, manage, and monitor Check Point products and security policies. Security Management is the server that stores and enforces the security policies and provides logging and reporting functions. Security Gateway is the device that inspects and filters network traffic according to the security policies.



You have a Geo-Protection policy blocking Australia and a number of other countries. Your network now requires a Check Point Firewall to be installed in Sydney, Australia.

What must you do to get SIC to work?

  1. Remove Geo-Protection, as the IP-to-country database is updated externally, and you have no control of this.
  2. Create a rule at the top in the Sydney firewall to allow control traffic from your network
  3. Nothing - Check Point control connections function regardless of Geo-Protection policy
  4. Create a rule at the top in your Check Point firewall to bypass the Geo-Protection

Answer(s): C

Explanation:

Nothing needs to be done to get SIC to work if there is a Geo-Protection policy blocking Australia and a network requires a Check Point Firewall to be installed in Sydney, Australia. SIC stands for Secure Internal Communication, and it is a mechanism that ensures secure and authenticated communication between Check Point components by using certificates issued by an internal Certificate Authority (ICA). SIC is not affected by Geo-Protection policy, which is a feature that allows administrators to block or allow traffic based on the geographic location of the source or destination IP address. Geo-Protection policy only applies to data traffic, not control traffic, and SIC uses control traffic to establish trust between Check Point components.



Viewing page 51 of 127
Viewing questions 251 - 255 out of 628 questions


Post your Comments and Discuss Checkpoint 156-315.81 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!