[Jul 28, 2026] 156-590 Exam Dumps, 156-590 Practice Test Questions
Free 156-590 Study Guides Exam Questions and Answer
NEW QUESTION # 31
Mike wants to block all files in the event of internal failure; what option should he choose?
- A. fail-open
- B. open system
- C. fail-close
- D. closed system
Answer: C
Explanation:
The correct answer is B. fail-close . Fail mode defines how the Threat Prevention inspection engine behaves when it is overloaded or experiences an internal failure. Check Point's Threat Prevention Engine Settings documentation defines two options: Allow all connections (Fail-open) and Block all connections (Fail- close) . Fail-open allows connections when the engine is overloaded or fails; Fail-close blocks connections in that condition.
Because the question specifically says Mike wants to block all files if an internal failure occurs, the secure choice is fail-close. This prioritizes protection and containment over availability. It is appropriate where allowing unscanned files would be unacceptable, such as highly regulated environments, malware-sensitive segments, or traffic paths carrying untrusted downloads. The tradeoff is operational: fail-close can interrupt business traffic if the inspection engine is unavailable, overloaded, or unable to complete the decision. Fail- open is the default availability-oriented behavior because it keeps traffic moving during failure, but it permits files or connections that may not have completed inspection. "Open system" and "closed system" are not the correct Check Point Threat Prevention fail-mode terms in this context. Reference topics: Threat Prevention Engine Settings, ThreatSpect fail mode, fail-open, fail-close, inspection failure handling.
NEW QUESTION # 32
Task: Assign Anti-Bot and Anti-Virus profiles to a Threat Prevention policy rule.
Answer:
Explanation:
See the Explanation.Explanation:
1- Open Threat Prevention > Policy.
2- Add a rule with appropriate Source, Destination, Services.
3- Under "Profile," assign the custom AV/AB profile.
4- Set Action to "Accept" and Track to "Log."
5- Publish and install the policy.
NEW QUESTION # 33
What kind of information is stored in the Audit Log?
- A. An audit log is a record of system event logs on the Security Gateway.
- B. An audit log is a portion of the traffic log which has been filtered by filter expression defined by the administrator.
- C. An audit log is a record of actions taken by administrators.
- D. An audit log is a record of system event logs on the Security Management Server.
Answer: C
NEW QUESTION # 34
What is the primary benefit of DNS Trap?
- A. Blocking inbound malicious DNS queries
- B. Infected host identification
- C. Blocking outbound malicious DNS queries
- D. Blocking known bad URLs
Answer: B
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 # 35
What are the logical components of a SNORT rule?
- A. Rule Header / rule body
- B. Rule start / rule options
- C. Rule Header and Rule Options
- D. Rule start / rule stop
Answer: C
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 # 36
What is true concerning the Threat Prevention Policy?
- A. The Threat Prevention Policy can override an Access Control Policy Drop or Reject.
- B. In a case of a conflict, the Threat Prevention Policy takes precedence over an Access Control Policy.
- C. Multiple Threat Prevention Policies can be assigned to one Security Gateway.
- D. The Threat Prevention Policy is only applied after traffic is accepted by Access Control Policy.
Answer: D
Explanation:
The correct answer is D. The Threat Prevention Policy is only applied after traffic is accepted by Access Control Policy . Threat Prevention is a follow-up inspection framework for traffic that has already passed the access decision. The Access Control policy determines whether a connection is allowed, rejected, or dropped.
Only traffic that is allowed by Access Control can proceed into Threat Prevention evaluation for IPS, Anti- Bot, Anti-Virus, Threat Emulation, and related blades. Check Point's policy workflow separates Access Control and Threat Prevention, and the Threat Prevention guide describes the Threat Prevention rulebase as the policy used to activate needed protections and prevent attacks against accepted traffic flows.
Options B and C are incorrect because Threat Prevention does not resurrect or override a connection that Access Control has already dropped or rejected. The inspection chain is sequential from an enforcement perspective: blocked traffic does not continue to malware or IPS inspection as an accepted connection. Option A is also incorrect because a gateway is assigned policy through its policy package and Threat Prevention policy structure, not by stacking multiple independent Threat Prevention policies on the same target as competing enforcement policies. Reference topics: Threat Prevention Policy workflow, Access Control then Threat Prevention sequence, policy package enforcement, accepted-traffic inspection.
NEW QUESTION # 37
Task: Monitor if Anti-Bot is detecting lateral movement inside the network.
Answer:
Explanation:
See the Explanation.Explanation:
1- Use simulated internal bot communication in test lab.
2- Logs & Monitor > Filter blade:"Anti-Bot" and internal source/destination IPs.
3- Check behavior pattern logs, not just single IP detection.
4- Review communication timeline and triggered protections.
5- Use this to tune bot detection rules in the profile.
NEW QUESTION # 38
Task: Simulate a file download test and confirm Anti-Virus prevention using the custom profile.
Answer:
Explanation:
See the Explanation.Explanation:
1- Use EICAR test file in a browser.
2- Confirm file is blocked and logs show blade:"Anti-Virus" and action:"Prevented".
3- Confirm the active profile name matches your custom profile.
4- Check logs for file hash and signature info.
5- Document success as part of validation.
NEW QUESTION # 39
Task: Enable Threat Prevention debug mode for troubleshooting.
Answer:
Explanation:
See the Explanation.Explanation:
1- SSH into the Gateway.
2- Run: tecli debug on or pdp debug on.
3- Reproduce the issue.
4- View logs in $FWDIR/log/.
5- Disable debug mode: tecli debug off.
NEW QUESTION # 40
Task: Check if IPS blade is inspecting encrypted traffic.
Answer:
Explanation:
See the Explanation.Explanation:
1- Confirm HTTPS Inspection is enabled on the gateway.
2- Navigate to Threat Prevention > Protections.
3- Check protections related to SSL/TLS.
4- Confirm visibility of SSL payloads in logs.
5- Use HTTPS test traffic and review detection.
NEW QUESTION # 41
Task: Roll back IPS protections to a previous version.
Answer:
Explanation:
See the Explanation.Explanation:
1- Go to Threat Prevention > Updates.
2- Click "View Versions" under IPS.
3- Select an older version and click "Install."
4- Monitor status and confirm with ips stat.
5- Document rollback for audit purposes.
NEW QUESTION # 42
Task: Set Anti-Virus protections to prevent downloads of known malware in the same profile.
Answer:
Explanation:
See the Explanation.Explanation:
1- Edit Corporate_TP_Strict > Anti-Virus tab.
2- Enable protection against malicious files and emails.
3- Set confidence level High and Medium to Prevent.
4- Enable file scanning on protocols like HTTP, SMTP, FTP.
5- Save and close.
NEW QUESTION # 43
Which mode allows you to tune or troubleshoot the Threat Prevention Blade?
- A. Observe Mode
- B. Detect Mode
- C. Watch Mode
- D. Display Mode
Answer: B
Explanation:
The correct answer is B. Detect Mode . Detect Mode is used when an administrator wants visibility into Threat Prevention behavior without immediately enforcing a blocking decision. In troubleshooting and tuning, this is essential because it allows security teams to identify which protections would have triggered, review logs, validate false positives, and adjust profiles or exceptions before moving to full prevention. Check Point's official troubleshooting guidance for Autonomous Threat Prevention describes Detect Only mode and states that protections set to Prevent allow traffic to pass while continuing to track threats according to the Track setting.
This makes Detect Mode the correct operational mode for safe tuning. It preserves observability while reducing the risk of production disruption during policy validation, IPS profile changes, new blade rollout, or incident investigation. Observe Mode , Display Mode , and Watch Mode are not the Check Point Threat Prevention operating modes used for this purpose in the exam context. In a certification scenario, Detect Mode should be understood as a non-blocking validation state: it logs and tracks what Threat Prevention would have done, but does not stop the connection based on a Prevent action. Reference topics: Detect Only, Threat Prevention troubleshooting, profile tuning, false-positive validation, Track settings.
NEW QUESTION # 44
Which protection setting is generally the LEAST resource intensive?
- A. Prevent
- B. Detect
- C. Inspect
- D. Inactive
Answer: D
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 # 45
What is the correct action to exclude one or more Threat Prevention Blades in a Blade exception rule?
- A. "ignore"
- B. "inactive"
- C. "bypass"
- D. "Ask user"
Answer: C
Explanation:
The correct answer is D. "bypass" . A blade exception rule is used when matching traffic should be excluded from inspection by one or more Threat Prevention blades. In this context, bypass is the correct action because it tells the gateway not to apply the selected blade inspection to that traffic. Check Point's exception documentation describes exceptions as a way to set a different action for an object in the protected scope, usually to reduce enforcement. The same guide shows that exception rules can include a Protection/Site/File
/Blade cell, where administrators can select categories including Blades as exception items.
This is distinct from making a protection inactive globally. Inactive disables a protection or blade more broadly and is not the correct per-exception action for excluding selected traffic. Ignore is not the Threat Prevention exception action used in this context. Ask user is a UserCheck-style interaction and is not appropriate for bypassing Threat Prevention blade inspection. Bypass is precise: it preserves the broader policy while excluding only the matching scope from the selected blade or file-processing behavior. The guide also shows bypass behavior in file-type exception configuration, where a file type can be selected and bypassed under profile exception handling. Reference topics: Threat Prevention Exception Rules, Blade exceptions, bypass action, protected scope, file/blade exclusion.
NEW QUESTION # 46
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 # 47
What Track - Settings Forensics does not?
- A. Forensics details also include Security Gateway statistics, which are sent to the Check Point Cloud.
- B. When enabled, advanced forensics detailed information is included in logs.
- C. Check Point researchers use advanced forensics details for troubleshooting and attack analysis.
- D. Communicate forensics data collected to Government Agencies.
Answer: D
Explanation:
The correct answer is D. Communicate forensics data collected to Government Agencies . The Forensics tracking option exists to enrich Threat Prevention logs with deeper technical context for analysis and troubleshooting. Check Point documentation states that the Forensics option adds fields to Threat Prevention logs and that the additional information gives a deeper understanding of an attack. The Monitoring Threat Prevention guidance also explains that Advanced Forensics Details can include protocol-specific details for DNS, FTP, SMTP, HTTP, and HTTPS, and that this information is used by Check Point researchers to analyze attacks.
The purpose is security analysis, incident investigation, and support-quality evidence collection, not government reporting. Options A and B accurately describe the function of Forensics tracking. Option C reflects the broader idea that forensic and diagnostic details may include gateway-related technical data for Check Point analysis, depending on configuration and feature behavior. Option D is the false statement because Check Point Threat Prevention Forensics is not defined as a mechanism for transmitting collected forensic data to government agencies. In production, enabling Forensics should be treated as a deliberate logging and privacy decision because it may add protocol and transaction context to logs. Reference topics:
Threat Prevention Track Options, Forensics tracking, Advanced Forensics Details, Logs & Monitor, attack analysis.
NEW QUESTION # 48
Who owns and maintains the CVE program and database?
- A. National Institute of Standards and Technology (NIST)
- B. US Department of Homeland Security (DHS)
- C. MITRE Corporation
- D. Check Point
Answer: C
Explanation:
The correct answer is C. MITRE Corporation . CVE, or Common Vulnerabilities and Exposures, is the standardized naming system used across security vendors, vulnerability databases, IPS signatures, advisories, scanners, and remediation programs. In a Check Point Threat Prevention context, CVE identifiers are important because IPS protections frequently map detections and exploit protections to known vulnerabilities.
This allows administrators to correlate a Check Point IPS protection with vendor advisories, exposure management, patching, and risk prioritization. The official CVE site describes CVE as an authoritative reference method for publicly known information-security vulnerabilities and exposures. MITRE documentation states that The MITRE Corporation maintains CVE and its public website , manages compatibility, and provides technical guidance to the CVE Editorial Board.
The distractors represent related but distinct roles. DHS/CISA has historically sponsored or funded the program, but sponsorship is not ownership and maintenance of the CVE list itself. NIST maintains the National Vulnerability Database, which enriches CVE data with scoring and analysis, but NVD is downstream from CVE identifiers. Check Point consumes CVE intelligence through IPS and ThreatCloud- driven protections; it does not own the CVE program. Reference topics: IPS vulnerability mapping, CVE- based protection metadata, threat intelligence normalization, vulnerability-to-protection correlation.
NEW QUESTION # 49
Task: Enable Anti-Bot and Anti-Virus software blades on a Security Gateway.
Answer:
Explanation:
See the Explanation.Explanation:
1- Open SmartConsole > Gateways & Servers.
2- Double-click the relevant Security Gateway.
3- Under the "General Properties" tab, enable "Anti-Bot" and "Anti-Virus."
4- Click OK > Publish the changes.
5- Install the Access Control and Threat Prevention policy.
NEW QUESTION # 50
......
156-590 Exam Dumps, 156-590 Practice Test Questions: https://examtorrent.testkingpdf.com/156-590-testking-pdf-torrent.html
