Actual 156-590 Exam Recently Updated Questions with Free Demo
Free CheckPoint 156-590 Exam Questions Self-Assess Preparation
NEW QUESTION # 12
Task: Configure inspection settings for mobile VPN users.
Answer:
Explanation:
See the Explanation.Explanation:
1- Go to Threat Prevention > Inspection Settings.
2- Add a new exception group for mobile user IP pool.
3- Set reduced inspection sensitivity for this group.
4- Save, publish, and test VPN user traffic.
5- Ensure logs still show critical threats being detected.
NEW QUESTION # 13
Task: Use CLI to test connectivity with IPS update servers.
Answer:
Explanation:
See the Explanation.Explanation:
1- SSH into the Gateway.
2- Run: curl -v https://updates.checkpoint.com.
3- Confirm certificate and connection success.
4- Run ips update now for manual update.
5- Check /opt/CPsuite-R81/fw1/log/ips_update.elg for result.
NEW QUESTION # 14
What is the name of the default Threat Prevention Profile?
- A. Basic
- B. Strict
- C. Optimized
- D. Standard
Answer: C
Explanation:
The correct answer is D. Optimized . In Check Point Threat Prevention, profiles define how the gateway applies protections across blades such as IPS, Anti-Bot, Anti-Virus, Threat Emulation, and Threat Extraction.
The default profile is Optimized , because it balances effective security with acceptable gateway performance. Check Point documentation states that the Optimized profile is activated by default and that it gives excellent security with good gateway performance.
This design reflects the practical tradeoff in enterprise Threat Prevention: not every protection should be enabled at the most aggressive setting on every gateway, because high-impact protections can increase CPU consumption, latency, and inspection overhead. The Optimized profile uses criteria such as protection severity, confidence, and performance impact to activate protections that are broadly useful without creating unnecessary operational cost. Basic is less aggressive and is intended for lower-impact protection coverage.
Strict provides wider coverage but can affect performance more significantly. Standard is not one of the default Threat Prevention profiles in this context. Reference topics: Threat Prevention Profiles, default profile behavior, Optimized Protection Profile settings, blade activation, security/performance balance.
NEW QUESTION # 15
Task: Configure a specific protection for DNS tunneling detection.
Answer:
Explanation:
See the Explanation.Explanation:
1- Go to Threat Tools > IPS Protections.
2- Search for "DNS tunneling" and select it.
3- Set action to "Prevent" and tag it for monitoring.
4- Add it to your active IPS profile.
5- Confirm with SmartConsole logs if any events occur post-enforcement.
NEW QUESTION # 16
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 # 17
Task: Update IPS protection database on the Security Gateway manually.
Answer:
Explanation:
See the Explanation.Explanation:
1- SSH into the Gateway.
2- Run: ips update now to fetch new protections.
3- Verify update status: ips stat or cpview.
4- Check update timestamp in SmartConsole > Gateways > Threat Prevention > Updates.
5- Confirm protections appear in IPS Protections list.
NEW QUESTION # 18
What information is provided by "fwaccel stats"?
- A. You can check the percentage of F2F connections along with the reason why those connections could not be accelerated.
- B. The command is used to examine traffic utilization statistics.
- C. This command is to enable acceleration on QoS packets.
- D. You can check the SecureXL status of your Security Gateway.
Answer: A
Explanation:
The correct answer is B. You can check the percentage of F2F connections along with the reason why those connections could not be accelerated . The command fwaccel stats is part of SecureXL performance analysis. It is used to inspect how traffic is distributed across acceleration paths and firewall paths, which is essential when Threat Prevention blades or deep inspection features push traffic away from full acceleration.
Check Point's Performance Tuning documentation shows that fwaccel stats -s provides a summary including accelerated packets, F2Fed packets, F2V packets, CPASXL packets, PSLXL packets, and related totals.
The same documentation explains that F2F packets are packets SecureXL forwarded to the Firewall kernel in the slow path. This makes the command directly useful when diagnosing performance issues caused by non- accelerated inspection, SecureXL violations, or traffic that must be inspected by firewall and Threat Prevention components. Option A is wrong because fwaccel stats does not enable QoS acceleration. Option C is too generic; the command is not merely utilization monitoring. Option D better describes fwaccel stat , which reports SecureXL status, accelerated interfaces, and accelerated features. Reference topics: SecureXL, fwaccel stats, F2F packets, accelerated path, firewall path, performance troubleshooting.
NEW QUESTION # 19
Task: Configure specific protections for SMB protocol attacks.
Answer:
Explanation:
See the Explanation.Explanation:
1- In IPS Protections, filter by "Protocol: SMB."
2- Enable all protections related to SMB and set to "Prevent."
3- Add a tag: "Windows Server Protections."
4- Attach them to a custom profile.
5- Save and assign the profile in Threat Prevention policy.
NEW QUESTION # 20
Which protection setting is generally the MOST resource intensive?
- A. Detect
- B. Inactive
- C. Inspect
- D. Prevent
Answer: D
Explanation:
The correct answer is B. Prevent . From a performance perspective, the most resource-intensive setting is generally the one that requires the gateway not only to inspect and identify the threat, but also to enforce a blocking decision inline. Prevent mode means the protection is actively applied to traffic and the gateway must make a real-time enforcement decision. Check Point explains that Threat Prevention profiles activate protections based on factors that include the performance impact of the protection , threat severity, confidence level, and blade-specific settings. Check Point's IPS optimization guidance also warns that some protections require more system resources to inspect traffic and recommends focusing on lower-impact protections when reducing gateway resource use is necessary.
By comparison, Inactive is the least intensive because the protection is not enforced. Detect can log or report detection without blocking, which is useful for staging and troubleshooting. Inspect still consumes inspection resources, but Prevent typically represents the highest operational burden because it performs inline analysis and enforcement, and may require buffering, stream handling, packet modification, or connection termination depending on blade and protocol. In real deployments, the exact resource cost also depends on traffic mix, protocol, file size, SSL inspection, protection complexity, and whether traffic remains accelerated. Reference topics: IPS Profile Settings, protection activation, Prevent versus Detect, Performance Impact, IPS optimization.
NEW QUESTION # 21
Which DNS Protection mechanism has been introduced with R81.20?
- A. ThreatCloud DNS Tunneling Protection.
- B. Malware DNS Trap.
- C. Propagation of a Bogus IP as a response to a DNS request.
- D. Synchronization of the /etc/hosts file from Protection servers.
Answer: A
Explanation:
The correct answer is C. ThreatCloud DNS Tunneling Protection . Check Point R81.20 introduced major Advanced Threat Prevention enhancements, including AI Deep Learning improvements for DNS attacks. The R81.20 Release Notes state that AI Deep Learning prevents more DNS attacks in real time and specifically reference ThreatCloud DNS tunneling protection as part of the DNS Security enhancements.
DNS tunneling protection is distinct from Malware DNS Trap. Malware DNS Trap returns a false or bogus IP address for known malicious hosts and domains, and it can help identify compromised clients by observing connection attempts to the false trap address. That mechanism is represented by option A/B, but it is not the R81.20-introduced DNS protection being tested here. ThreatCloud DNS Tunneling Protection targets a different technique: abuse of DNS as a covert channel for command-and-control, data exfiltration, or tunneling traffic through recursive DNS infrastructure. Option D is unrelated to Check Point DNS Threat Prevention architecture. Reference topics: R81.20 Advanced Threat Prevention, DNS Security, ThreatCloud DNS Tunneling Protection, Malware DNS Trap, Anti-Bot and Anti-Virus DNS protections.
NEW QUESTION # 22
Which location is NOT able to create a Threat Prevention Exception?
- A. Log Overview
- B. Log Details
- C. Policy Rule
- D. SmartView
Answer: D
Explanation:
The correct answer is D. SmartView . Threat Prevention exceptions are created and managed in SmartConsole policy and log workflows, not from SmartView as the tested location. Check Point documentation states that an exception can be added directly to a rule, and the procedure begins by selecting the rule in the Policy pane and clicking Add Exception . It also documents creating exceptions from IPS Protections and from logs or events in the Logs & Monitor view, where the administrator right-clicks a log and selects Add Exception .
This validates Policy Rule, Log Overview, and Log Details-style workflows as valid exception creation contexts. SmartView, by contrast, is primarily used for browser-based log viewing, reporting, dashboards, and event analysis. It is not the SmartConsole policy-editing context where Threat Prevention exception rules are inserted into the policy package and then installed. The operational reason is enforcement integrity:
exceptions modify the compiled Threat Prevention policy, so they must be created in a policy-aware workflow where protected scope, protection/site/file/blade, action, track, install targets, and policy installation are controlled. Reference topics: Exception Rules, Adding Exception to Rule, Creating Exceptions from Logs or Events, IPS Protections exceptions, Threat Prevention Policy installation.
NEW QUESTION # 23
Task: Enable DNS reputation check in Anti-Bot.
Answer:
Explanation:
See the Explanation.Explanation:
1- Go to SmartConsole > Gateway Properties > Threat Prevention.
2- Under Anti-Bot settings, enable DNS reputation check.
3- Save and install the policy.
4- Simulate a DNS lookup to a known malicious domain.
5- Confirm log entries for DNS reputation actions.
NEW QUESTION # 24
Core Activation Exceptions are applied to what?
- A. Protection Groups
- B. Individual Protections
- C. Threat Cloud
- D. Inspection Settings
Answer: B
Explanation:
The correct answer is D. Individual Protections . Core Activation Exceptions are used to override activation behavior at the protection level, not at a broad ThreatCloud, inspection-engine, or protection-group abstraction. The official IPS profile settings documentation explains that the Additional Activation section gives administrators granular control to select IPS protections to activate or deactivate. It states that activated protections are enforced by gateways, while deactivated protections are not enforced, regardless of the general profile protection settings.
Check Point's IPS Protections documentation reinforces this object-level model: each profile is a set of activated protections plus instructions for what IPS does if traffic matches an activated protection, and administrators can change the action for a specified protection. Therefore, a Core Activation Exception is not a general tuning category and does not apply to the entire ThreatCloud or to engine-wide inspection settings.
It is used when a specific protection requires a different activation state than the profile would normally produce. This is common during false-positive handling, staged rollout, exception tuning, or targeted hardening for a specific vulnerability. Reference topics: IPS Protections, Additional Activation, activation overrides, individual protection enforcement, profile-based IPS tuning.
NEW QUESTION # 25
Task: Validate Anti-Bot blade updates on the Gateway.
Answer:
Explanation:
See the Explanation.Explanation:
1- SSH into the Gateway.
2- Run: cpstat threat-emulation and cpstat anti-bot.
3- Check SmartConsole > Gateways > Updates tab.
4- Validate signature update timestamps.
5- Ensure outbound connectivity to Check Point update servers.
NEW QUESTION # 26
What is the primary benefit of DNS Trap?
- A. Blocking known bad URLs
- B. Blocking inbound malicious DNS queries
- C. Infected host identification
- D. Blocking outbound malicious DNS queries
Answer: C
Explanation:
The correct answer is A. Infected host identification . Malware DNS Trap is designed to help identify compromised clients by redirecting malicious DNS resolution to a controlled false IP address and then observing which internal hosts attempt to connect to that trap address. Check Point's R81.20 Threat Prevention guide states that Malware DNS Trap can be used to detect compromised clients by checking logs with connection attempts to the false IP address. It also notes that internal DNS servers can be added to better identify the origin of malicious DNS requests.
This makes the primary operational benefit host attribution. While DNS security can block or prevent malicious DNS-related activity, DNS Trap's distinctive value is showing which internal endpoint is likely infected or attempting malicious communication. Option B is more aligned with URL Filtering or URL reputation, not DNS Trap. Option C describes a blocking outcome, but it misses the key trap mechanism and attribution purpose. Option D is incorrect because the usual DNS Trap use case concerns internal clients generating suspicious outbound DNS or follow-up connections, not inbound malicious DNS queries.
Reference topics: Malware DNS Trap, Anti-Bot & Advanced DNS, false IP address, compromised-client detection, infected-host investigation.
NEW QUESTION # 27
Task: Check the current IPS protection version on the Security Gateway.
Answer:
Explanation:
See the Explanation.Explanation:
1- Open SmartConsole > Gateways & Servers.
2- Select the gateway and go to the "Threat Prevention" tab.
3- Note the IPS database version and timestamp.
4- On CLI: run ips stat to cross-verify.
5- Ensure version matches the latest published by Check Point.
NEW QUESTION # 28
Task: Validate the IPS update server connectivity from the gateway.
Answer:
Explanation:
See the Explanation.Explanation:
1- SSH into the gateway.
2- Use: curl -v https://updates.checkpoint.com
3- Confirm DNS resolves and certificate is valid.
4- Check proxy settings if blocked.
5- Verify SmartConsole > Gateways > Update section reflects success.
NEW QUESTION # 29
......
156-590 Free Sample Questions to Practice One Year Update: https://learningtree.actualvce.com/CheckPoint/156-590-valid-vce-dumps.html