
CTPS 156-590 Dumps Full Questions with Free PDF Questions to Pass
100% Updated CheckPoint 156-590 Enterprise PDF Dumps
NEW QUESTION # 43
Task: Enable DNS reputation protection under Anti-Bot in a custom profile.
Answer:
Explanation:
See the Explanation.Explanation:
1- Edit your custom Threat Prevention profile.
2- Under the Anti-Bot section, enable DNS Reputation.
3- Set to Prevent on High Confidence queries.
4- Ensure "Inspect DNS traffic" is enabled.
5- Save and apply the profile.
NEW QUESTION # 44
Are Cleanup Rules mandatory in a Threat Prevention Policy?
- A. Cleanup Rules are only required, if the Access Control Policy does not have one.
- B. Cleanup Rules are not required if you are using the Basic Profile.
- C. Cleanup Rules are not strictly required in the Threat Prevention Policy.
- D. A Cleanup Rule is required in a Basic Profile.
Answer: C
Explanation:
The correct answer is C. Cleanup Rules are not strictly required in the Threat Prevention Policy . Threat Prevention policy behavior is governed by ordered layers and rule matching, but an administrator is not forced to create an explicit cleanup rule in every Threat Prevention rulebase. Check Point documentation explains that a Threat Prevention Rule Base can contain multiple Policy Layers and that each layer calculates its action separately. For a single layer, the enforced rule is the first rule matched; for multiple layers, the final behavior depends on the layer matches and resulting action logic.
A cleanup rule is still a strong operational best practice because it makes the terminal behavior explicit, easier to audit, and easier for operations teams to troubleshoot. Without an explicit cleanup rule, behavior depends on the layer's implicit cleanup logic and the policy architecture. Check Point Security Management documentation shows that implicit cleanup behavior exists at the layer level and can be configured as Drop or Accept in the Layer Editor. The question asks whether cleanup rules are mandatory, not whether they are recommended. Options A and D incorrectly tie cleanup rule requirement to the Basic Profile. Option B incorrectly links Threat Prevention cleanup requirements to the Access Control cleanup rule. Reference topics: Threat Prevention Policy Layers, implicit cleanup rule, explicit cleanup best practice, Layer Editor behavior.
NEW QUESTION # 45
What is necessary to activate the exception to all Security Gateways?
- A. You have to re-install the Threat Prevention policy.
- B. The changes will be applied immediately, so no need to do anything.
- C. You have to re-install the Access Control policy.
- D. Install Database is sufficient.
Answer: A
Explanation:
The correct answer is B. You have to re-install the Threat Prevention policy . Threat Prevention exceptions are policy constructs, so they must be compiled and installed to the relevant Security Gateways before they affect enforcement. Check Point documentation for creating IPS exceptions shows the workflow: create or configure the exception rule, click OK, and then Install Policy . The Custom Threat Prevention guide also explains that Threat Prevention blades have a dedicated Threat Prevention policy and that this policy can be installed separately from Access Control. It explicitly recommends installing only the Threat Prevention policy to minimize performance impact on Security Gateways.
This is why Install Database is not sufficient. Install Database updates management-side objects and databases, but it does not enforce a new Threat Prevention exception on gateways. Installing Access Control policy is also the wrong policy domain because Anti-Virus, Anti-Bot, IPS, Threat Emulation, and Threat Extraction exceptions belong to Threat Prevention. The change is not immediately active because Security Gateways enforce compiled policy, not unpublished or uninstalled SmartConsole changes. Reference topics:
Threat Prevention Exceptions, IPS Exceptions, policy installation targets, dedicated Threat Prevention policy, exception enforcement lifecycle.
NEW QUESTION # 46
Task: Use CLI to check ThreatCloud status.
Answer:
Explanation:
See the Explanation.Explanation:
1- SSH into Gateway.
2- Run: tecli show cloud status.
3- Look for Status: Connected.
4- Check logs in /opt/CPsuite-R81/fw1/log/te.log.
5- Ensure outbound HTTPS to ThreatCloud servers is allowed.
NEW QUESTION # 47
Which of the following protocols can be scanned by Anti-Virus?
- A. RemoteDesktop
- B. SNMP
- C. Telnet
- D. CIFS
Answer: D
Explanation:
The correct answer is C. CIFS . Check Point Anti-Virus scans file-transfer and content-bearing protocols, not arbitrary management or terminal protocols. The official Anti-Virus settings documentation lists the protocols Anti-Virus can scan as Web HTTP/HTTPS , FTP , SMB , and Mail SMTP or POP3 , with additional support for IMAP and POP3.
CIFS is closely associated with Microsoft file sharing and the SMB protocol family. In the exam context, CIFS maps to the file-sharing traffic class that Anti-Virus can inspect through SMB scanning. This is why CIFS is the correct option. Remote Desktop is an interactive remote-control protocol, not a file-inspection protocol for Anti-Virus scanning in this question. SNMP is a monitoring and management protocol and does not normally carry files for malware inspection. Telnet is an interactive terminal protocol and is not an Anti- Virus file-scanning protocol. The certification distinction is that Anti-Virus inspection focuses on files and content objects crossing supported protocols, especially web downloads, FTP transfers, SMB/CIFS file access, and mail attachments. Reference topics: Anti-Virus Settings, protocol scanning, SMB/CIFS inspection, file-transfer inspection, Threat Prevention protected scope.
NEW QUESTION # 48
What Threat Prevention signature updates you can trigger manually?
- A. Non everything is updated automatically.
- B. IPS, Antivirus and Antibot.
- C. Only IPS.
- D. IPS and antivirus.
Answer: B
Explanation:
The correct answer is D. IPS, Antivirus and Antibot . Threat Prevention updates can be scheduled automatically, but administrators can also manually trigger updates for the major signature/intelligence-driven Threat Prevention blades. Check Point's scheduled-update documentation states that automatic gateway updates can be configured for Anti-Virus , Anti-Bot , Threat Emulation , and IPS blades. It also explains that Anti-Virus, Anti-Bot, and Threat Emulation gateways download updates directly from the Check Point cloud, while IPS update behavior changed from management-based enforcement before R80.20 to gateway direct download starting in R80.20.
In the exam context, the manually triggered signature-update set is IPS, Anti-Virus, and Anti-Bot. These blades depend heavily on continuously updated threat intelligence, signatures, malicious domains, command- and-control intelligence, malware classification, and IPS protection packages. Option B is too narrow because IPS is not the only manually updateable Threat Prevention component. Option C is incomplete because it omits Anti-Bot. Option A is not a valid update-set answer. Operationally, manual updates are used when an urgent threat advisory, lab recommendation, incident response condition, or failed scheduled update requires immediate refresh of protection data. Reference topics: Threat Prevention Updates, IPS Updates, Anti-Virus Updates, Anti-Bot Updates, scheduled and manual update workflow.
NEW QUESTION # 49
Task: Configure inspection settings to reduce performance impact on a busy gateway.
Answer:
Explanation:
See the Explanation.Explanation:
1- Navigate to Threat Prevention > Inspection Settings in SmartConsole.
2- Choose "Performance Optimization" tab.
3- Lower detection sensitivity or exclude internal trusted networks.
4- Save changes and apply policy to the relevant gateways.
5- Monitor logs for false negatives and adjust as needed.
NEW QUESTION # 50
Task: Clone a built-in IPS profile and tailor it to internal services.
Answer:
Explanation:
See the Explanation.Explanation:
1- Open Threat Prevention > Profiles.
2- Select "Optimized" > Right-click > Clone.
3- Rename it (e.g., "Internal_Services_Profile").
4- Disable protections unnecessary for internal traffic (e.g., HTTP-related).
5- Save, apply to Threat Prevention policy layer.
NEW QUESTION # 51
Task: Clone an existing profile to use for mobile endpoints and modify AV scanning.
Answer:
Explanation:
See the Explanation.Explanation:
1- Go to Threat Prevention > Profiles.
2- Select the base profile (e.g., Optimized), right-click > Clone.
3- Name it Mobile_Profile.
4- Edit Anti-Virus settings to use Detect instead of Prevent for medium threats.
5- Save and assign to mobile VPN policy rule.
NEW QUESTION # 52
Task: Troubleshoot policy installation failure.
Answer:
Explanation:
See the Explanation.Explanation:
1- In SmartConsole, attempt policy install again and note error.
2- View install_policy.elg in $FWDIR/log/.
3- Verify SIC is active.
4- Ensure policy contains no rulebase errors.
5- Re-push after resolving syntax or connectivity issues.
NEW QUESTION # 53
Task: Verify if a specific IPS protection is active.
Answer:
Explanation:
See the Explanation.Explanation:
1- Go to Threat Tools > IPS Protections.
2- Use the filter to search by name or CVE ID.
3- Confirm status is "Active" and assigned to profile.
4- Double-click to view scope and affected profiles.
5- Confirm via SmartConsole logs if it triggered recently.
NEW QUESTION # 54
What are the logical components of a SNORT rule?
- A. Rule Header and Rule Options
- B. Rule start / rule options
- C. Rule Header / rule body
- D. Rule start / rule stop
Answer: A
Explanation:
The correct answer is B. Rule Header and Rule Options . Check Point supports SNORT rule import so administrators can create custom IPS protections from SNORT signatures. The official Check Point SNORT Signature Support documentation states that SNORT rules use signatures to define attacks and that a SNORT rule has a rule header and rule options . It also provides the syntax structure, where the first section contains action, protocol, source, destination, ports, and direction, while the options section contains keywords such as message and content match criteria.
The Rule Header defines the traffic selector and enforcement context: protocol, source address, source port, direction, destination address, and destination port. The Rule Options define the detection logic and metadata inside parentheses, such as msg, content, and other matching keywords. "Rule body" is not the formal Check Point/SNORT term in this context, and "rule start/rule stop" is not a recognized logical construction. This matters because imported SNORT rules become IPS protections, so syntax correctness affects whether the Management Server can parse, import, and enforce the custom signature. Reference topics: SNORT Signature Support, Custom IPS Protections, Rule Header, Rule Options, imported SNORT protections.
NEW QUESTION # 55
Which feature can improve performance by allowing the gateway to bypass Anti-Virus inspection of specific files?
- A. Bypass
- B. Exclusions
- C. Exceptions
- D. Content Control
Answer: B
Explanation:
The correct answer is B. Exclusions . In Anti-Virus policy design, exclusions are used to remove selected traffic or file categories from Anti-Virus inspection when inspection is unnecessary, redundant, or too costly for the business flow. Check Point documentation states that Threat Prevention can be configured to exclude files from inspection , including examples such as internal emails and internal file transfers. The same section explains that these settings are based on interface type and traffic direction.
This directly aligns with the performance objective in the question: if the gateway does not inspect files that are already trusted, internal, or operationally low-risk, Anti-Virus consumes fewer CPU, memory, buffering, and content-inspection resources. Content Control is not the Anti-Virus bypass feature named in this context.
Exceptions are policy-level constructs that can exclude traffic from Threat Prevention enforcement, but the question specifically asks for the feature that improves Anti-Virus performance by bypassing inspection of specific files, which is Exclusions . Bypass describes the effect, not the named feature. Reference topics:
Anti-Virus Settings, Protected Scope, file inspection exclusions, interface direction, Threat Prevention performance optimization.
NEW QUESTION # 56
Task: Exclude IP ranges in custom profile by associating a Threat Prevention exception rule.
Answer:
Explanation:
See the Explanation.Explanation:
1- Go to Threat Prevention > Policy.
2- Add top rule: Source = IP Range to be excluded.
3- Assign a profile with minimal protections or disabled blades.
4- Place before general rules.
5- Confirm policy flow and matching logs.
NEW QUESTION # 57
Task: Disable Anti-Virus scanning temporarily for troubleshooting.
Answer:
Explanation:
See the Explanation.Explanation:
1- In SmartConsole > Gateway Properties > Threat Prevention.
2- Uncheck "Anti-Virus" blade temporarily.
3- Publish and install the policy.
4- Re-enable it post-testing following the same steps.
5- Confirm with cpstat antimalware.
NEW QUESTION # 58
What are the three IPS update options?
- A. Auto Update, Policy Update, Update Now
- B. Manual Update, Scheduled Update, Auto Update
- C. Update Now, Schedule Update, Follow policy
- D. Update Now, Schedule Update, Follow Protections
Answer: D
Explanation:
The correct answer is B. Update Now, Schedule Update, Follow Protections . Check Point IPS protection maintenance includes manual updating, scheduled updating, and a follow-up workflow for newly updated protections. The official IPS Protections documentation explains that administrators can immediately update IPS from Custom Policy Tools > Updates > IPS > Update Now , and that IPS protections can also be updated by configuring a schedule for automatic downloads. It also notes that IPS updates require Threat Prevention Policy installation for enforcement.
The same IPS Protections section describes Follow Up behavior for protections: administrators can mark protections for follow-up, filter on them later, and updated protections can be automatically marked for follow- up so they can be reviewed after update. In the course-question wording, this maps to "Follow Protections." The purpose is operational control: update now provides immediate package retrieval, scheduled update automates routine maintenance, and follow protections gives administrators a practical workflow to review newly added or changed IPS protections. The other options either use non-standard names or omit the protection-review workflow. Reference topics: IPS Protections, Update Now, Scheduling IPS Updates, Follow Up Protections, Threat Prevention Policy installation.
NEW QUESTION # 59
Task: Verify if Anti-Bot and Anti-Virus protections are active on a Security Gateway.
Answer:
Explanation:
See the Explanation.Explanation:
1- SSH into the gateway.
2- Run: cpstat antimalware and cpstat anti-bot.
3- Confirm both blades are "Active" and signatures are "Up-to-date."
4- Check with cpview > Threat Prevention section.
5- Use watch -n 5 cpstat antimalware to monitor real-time status.
NEW QUESTION # 60
Task: Manually trigger an IPS update from SmartConsole.
Answer:
Explanation:
See the Explanation.Explanation:
1- Go to Threat Prevention > Updates.
2- Click "Check Now" under IPS section.
3- Wait for update to complete and view the status log.
4- On the gateway, check $FWDIR/log/ips_update.elg for details.
5- Confirm the update applied with ips stat.
NEW QUESTION # 61
Task: Use CLI to test the management server connectivity from the Security Gateway.
Answer:
Explanation:
See the Explanation.Explanation:
1- SSH into the Security Gateway.
2- Ping the management server: ping .
3- Check hostname resolution: nslookup .
4- Confirm SIC is established: cp_conf sic state.
5- Check for outbound connectivity on port 18210 (CPD).
NEW QUESTION # 62
Task: Create a custom Threat Prevention profile named Corporate_TP_Strict in SmartConsole.
Answer:
Explanation:
See the Explanation.Explanation:
1- Go to Threat Prevention > Profiles.
2- Click "New Profile", name it Corporate_TP_Strict.
3- In the base profile, select Optimized as a starting point.
4- Enable IPS, Anti-Bot, Anti-Virus, Threat Emulation, and Threat Extraction.
5- Save the profile for later assignment to a policy rule.
NEW QUESTION # 63
What does the HealthCheck (HCP) tests include?
- A. Assess Health of Console Connections
- B. Assess status of SmartEvent System
- C. Assess Health of System
- D. Assess Security of System
Answer: C
Explanation:
The correct answer is A. Assess Health of System . HealthCheck Point, commonly referred to as HCP , is Check Point's self-updatable health assessment suite. The official Security Management Administration Guide states that the HCP tool is designed for tests that assess the health of your system , WTS timelines that provide critical and informative events, and topology visualization. It also explains that HCP runs on managed Security Gateways every six hours and sends a status report to the Security Management Server or Domain Management Server.
Therefore, the "Tests" function of HCP is specifically system-health assessment. It is not primarily a SmartConsole connection checker, although management connectivity can affect visibility. It is also not a general "security posture" assessment engine in the sense of policy risk analysis, and it is not limited to SmartEvent status. In troubleshooting, HCP is useful because it gives administrators a structured view of platform health, recent critical events, and topology-related information, helping distinguish Threat Prevention blade problems from broader gateway, management, or system-health issues. Reference topics:
HealthCheck Point Tool, HCP Tests, system-health assessment, WTS, topology visualization, managed gateway status reporting.
NEW QUESTION # 64
Which protection setting is generally the LEAST resource intensive?
- A. Inactive
- B. Inspect
- C. Prevent
- D. Detect
Answer: A
Explanation:
The correct answer is D. Inactive . A protection set to Inactive is not enforced for matching traffic, so it does not impose the same inspection and enforcement cost as active protection states. Check Point documentation explains that a Threat Prevention profile determines which protections are activated and which Software Blades are enabled for a rule or policy. The protections a profile activates depend on factors such as performance impact, threat severity, confidence level, and blade-specific settings. Check Point best-practice material also describes that administrators may tune IPS profiles and set protections to prevent , detect , or inactive .
The relative resource logic is direct: Prevent is usually the most expensive because the gateway must inspect and enforce a blocking action inline. Inspect and Detect still require traffic analysis and matching logic, even if the final result is logging rather than prevention. Inactive removes the protection from enforcement consideration, making it the lowest resource option. This does not mean administrators should disable protections indiscriminately; Inactive should be used only when justified by risk, false-positive analysis, performance tuning, or compensating controls. Reference topics: IPS profile tuning, activation settings, performance impact, Prevent/Detect/Inactive behavior, Threat Prevention optimization.
NEW QUESTION # 65
Task: Enable Core Protections in an IPS profile.
Answer:
Explanation:
See the Explanation.Explanation:
1- Open Threat Prevention > Profiles > Edit the desired profile.
2- Scroll to Core Protections and ensure it's enabled.
3- Set action for High and Medium confidence to "Prevent."
4- Choose performance impact level allowed (e.g., Basic or Extensive).
5- Save changes and publish.
NEW QUESTION # 66
......
Use Valid Exam 156-590 by TestkingPass Books For Free Website: https://www.testkingpass.com/156-590-testking-dumps.html
Free CTPS 156-590 Official Cert Guide PDF Download: https://drive.google.com/open?id=1n5Fbq9S9iPLNMWD2iudBsMOqcYFCM4qJ