Checkpoint 156-315.82 Dumps
Checkpoint 156-315.82 Practice Test 46
Question 450
A municipal emergency service tests redundant remote-site VPN connectivity and must measure both failover and restoration before approving the design. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The test would be relevant: Restore the primary test link, inspect selected IKE addresses, active tunnel status and protected traffic in both directions, and document whether the configured return behavior matches the approved design. But the offered implementation—Configure supported tunnel management and health monitoring for site-to-site VPN, then test expected negotiation, liveness and rekey or reconnection behavior rather than relying only on physical interface status.—addresses “Monitor VPN tunnel liveness and rekey behavior through deliberate tests”. The action needed here is: After a supported ISP redundancy test, confirm the VPN community returns to its intended path policy, negotiation is healthy and all protected subnet traffic remains stable without duplicate or stale tunnel routes.
The question is set in this situation: A municipal emergency service tests redundant remote-site VPN connectivity and must measure both failover and restoration before approving the design. After a supported ISP redundancy test, confirm the VPN community returns to its intended path policy, negotiation is healthy and all protected subnet traffic remains stable without duplicate or stale tunnel routes. Confirm it through this test: Restore the primary test link, inspect selected IKE addresses, active tunnel status and protected traffic in both directions, and document whether the configured return behavior matches the approved design. Failing over to an alternate link is only half the recovery process; the subsequent path change may leave inconsistent preferred routes or stale peer endpoints if not validated.
This action/test pair addresses “Select Link Selection settings matching peer-reachable external addresses”. Configure supported Check Point VPN Link Selection to use the intended peer-reachable ISP interfaces or addresses and validate route and address advertisement against the network edge's real topology. Inspect the selected local and remote IKE addresses during two controlled tunnel negotiations and verify protected traffic uses the approved external interface. The case instead calls for: After a supported ISP redundancy test, confirm the VPN community returns to its intended path policy, negotiation is healthy and all protected subnet traffic remains stable without duplicate or stale tunnel routes.
The action is applicable: After a supported ISP redundancy test, confirm the VPN community returns to its intended path policy, negotiation is healthy and all protected subnet traffic remains stable without duplicate or stale tunnel routes. But its proposed test—Use a safe staged peer interruption, watch tunnel liveness and reestablishment events, then verify encrypted test application traffic resumes with expected policy and logs.—addresses “Monitor VPN tunnel liveness and rekey behavior through deliberate tests”. This requirement is confirmed instead by: Restore the primary test link, inspect selected IKE addresses, active tunnel status and protected traffic in both directions, and document whether the configured return behavior matches the approved design.
Question 451
A small bank is standing up SmartEvent for its remote Quantum gateways and needs to prove the log collector path is ready before enabling alerts. Which Check Point R82 security engineering action best addresses this requirement?
Answer & Explanations
Correct answer: C
Enable the supported R82 Compliance Blade assessment of managed security policy and gateway configuration, review relevant Security Best Practice findings and remediate validated risks through approved policy change procedures. This addresses “Activate Compliance Blade assessment and interpret security-best-practice findings”, where the governing principle is: Compliance assessment compares configuration against defined best-practice controls; a green monitoring uptime graph does not demonstrate that policy hardening or regulatory requirements have been met. The stated case instead calls for: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
Use gateway logs for individual connection details and SmartEvent for configured aggregation and correlation of related incidents, checking source records and event definitions before treating an alert as conclusive. This addresses “Distinguish raw gateway logs from SmartEvent correlated security events”, where the governing principle is: A single logged deny or intrusion signature is not always a correlated incident; SmartEvent groups and analyzes relevant input according to its event policy and processing. The stated case instead calls for: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service. SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics. Verify the result with this test: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions.
When SmartEvent results stop updating after moving logging infrastructure, inspect log source connectivity, relevant event processing configuration and time windows before changing the protected access policy. This addresses “Verify SmartEvent server processing after an upstream log-server change”, where the governing principle is: Event analysis depends on the source log delivery path and processing, so a valid security gateway policy can remain effective while SmartEvent sees no new records. The stated case instead calls for: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
Question 452
A small bank is standing up SmartEvent for its remote Quantum gateways and needs to prove the log collector path is ready before enabling alerts. The engineer proposes the following change: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics. The corresponding implementation is: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
Event analysis depends on the source log delivery path and processing, so a valid security gateway policy can remain effective while SmartEvent sees no new records. That explains “Verify SmartEvent server processing after an upstream log-server change”, not the mechanism behind the described change. The relevant principle is: SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics.
Compliance assessment compares configuration against defined best-practice controls; a green monitoring uptime graph does not demonstrate that policy hardening or regulatory requirements have been met. That explains “Activate Compliance Blade assessment and interpret security-best-practice findings”, not the mechanism behind the described change. The relevant principle is: SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics.
A single logged deny or intrusion signature is not always a correlated incident; SmartEvent groups and analyzes relevant input according to its event policy and processing. That explains “Distinguish raw gateway logs from SmartEvent correlated security events”, not the mechanism behind the described change. The relevant principle is: SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics.
Question 453
A small bank is standing up SmartEvent for its remote Quantum gateways and needs to prove the log collector path is ready before enabling alerts. After implementing this change—Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
Create several synthetic allowed test logs that should form a configured event, inspect the raw records and correlated SmartEvent result, and verify an unrelated log is not incorrectly included. That would help test “Distinguish raw gateway logs from SmartEvent correlated security events”, not the outcome required in this scenario. The relevant acceptance check is: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions.
Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions. This check is decisive because smartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics.
Generate a controlled new gateway log after repairing the log path, confirm its event timestamp and receipt, and check that the configured event view reflects current data rather than cached history. That would help test “Verify SmartEvent server processing after an upstream log-server change”, not the outcome required in this scenario. The relevant acceptance check is: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions.
Inspect a controlled noncompliant test setting, locate its Compliance finding and recommended remediation, apply a reviewed change, then verify the score or finding updates as expected. That would help test “Activate Compliance Blade assessment and interpret security-best-practice findings”, not the outcome required in this scenario. The relevant acceptance check is: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions.
Question 454
A small bank is standing up SmartEvent for its remote Quantum gateways and needs to prove the log collector path is ready before enabling alerts. Which proposed shortcut most directly risks missing correlated security events after a nominal monitoring server installation that never received gateway logs and should therefore be rejected?
Answer & Explanations
Correct answer: D
Disable the gateway threat-prevention blade because SmartEvent dashboards are empty, without verifying whether its logging server still forwards events. That shortcut risks loss of investigative visibility and reduced protections after misdiagnosing a log ingestion outage as broken enforcement. Here the specific shortcut is: Deploy a VM called SmartEvent and assume it detects gateway attack patterns immediately without configuring log ingestion or event processing.
Assume every individual dropped packet is automatically an independently validated high-severity SmartEvent incident requiring emergency response. That shortcut risks alert noise and inaccurate incident severity after confusing raw log entries with correlated security events. Here the specific shortcut is: Deploy a VM called SmartEvent and assume it detects gateway attack patterns immediately without configuring log ingestion or event processing.
Treat absence of SmartEvent threat alerts as proof that every gateway complies with all regulatory requirements without enabling or reviewing Compliance assessments. That shortcut risks undetected policy configuration weaknesses after using operational log quietness as a substitute for compliance evaluation. Here the specific shortcut is: Deploy a VM called SmartEvent and assume it detects gateway attack patterns immediately without configuring log ingestion or event processing.
Deploy a VM called SmartEvent and assume it detects gateway attack patterns immediately without configuring log ingestion or event processing. The foreseeable failure is missing correlated security events after a nominal monitoring server installation that never received gateway logs. The safer response is: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
Question 455
A small bank is standing up SmartEvent for its remote Quantum gateways and needs to prove the log collector path is ready before enabling alerts. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service. Confirm it through this test: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions. SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics.
The test would be relevant: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions. But the offered implementation—Use gateway logs for individual connection details and SmartEvent for configured aggregation and correlation of related incidents, checking source records and event definitions before treating an alert as conclusive.—addresses “Distinguish raw gateway logs from SmartEvent correlated security events”. The action needed here is: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
The action is applicable: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service. But its proposed test—Create several synthetic allowed test logs that should form a configured event, inspect the raw records and correlated SmartEvent result, and verify an unrelated log is not incorrectly included.—addresses “Distinguish raw gateway logs from SmartEvent correlated security events”. This requirement is confirmed instead by: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions.
This action/test pair addresses “Verify SmartEvent server processing after an upstream log-server change”. When SmartEvent results stop updating after moving logging infrastructure, inspect log source connectivity, relevant event processing configuration and time windows before changing the protected access policy. Generate a controlled new gateway log after repairing the log path, confirm its event timestamp and receipt, and check that the configured event view reflects current data rather than cached history. The case instead calls for: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
Question 456
A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Which Check Point R82 security engineering action best addresses this requirement?
Answer & Explanations
Correct answer: C
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Use gateway logs for individual connection details and SmartEvent for configured aggregation and correlation of related incidents, checking source records and event definitions before treating an alert as conclusive. This addresses “Distinguish raw gateway logs from SmartEvent correlated security events”, where the governing principle is: A single logged deny or intrusion signature is not always a correlated incident; SmartEvent groups and analyzes relevant input according to its event policy and processing. The stated case instead calls for: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
Generate an approved SmartEvent report based on a documented event type, time window and relevant gateway sources, validate underlying records and share only through controlled reporting channels. This addresses “Build a focused SmartEvent report for a defined security investigation”, where the governing principle is: An event report summarizes selected correlated evidence; an arbitrary exported chart cannot prove scope or accuracy without the correct event filter and source logs. The stated case instead calls for: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service. SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics. Verify the result with this test: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. When SmartEvent results stop updating after moving logging infrastructure, inspect log source connectivity, relevant event processing configuration and time windows before changing the protected access policy. This addresses “Verify SmartEvent server processing after an upstream log-server change”, where the governing principle is: Event analysis depends on the source log delivery path and processing, so a valid security gateway policy can remain effective while SmartEvent sees no new records. The stated case instead calls for: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
Question 457
A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. The engineer proposes the following change: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics. The corresponding implementation is: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
An event report summarizes selected correlated evidence; an arbitrary exported chart cannot prove scope or accuracy without the correct event filter and source logs. That explains “Build a focused SmartEvent report for a defined security investigation”, not the mechanism behind the described change. The relevant principle is: SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. A single logged deny or intrusion signature is not always a correlated incident; SmartEvent groups and analyzes relevant input according to its event policy and processing. That explains “Distinguish raw gateway logs from SmartEvent correlated security events”, not the mechanism behind the described change. The relevant principle is: SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Event analysis depends on the source log delivery path and processing, so a valid security gateway policy can remain effective while SmartEvent sees no new records. That explains “Verify SmartEvent server processing after an upstream log-server change”, not the mechanism behind the described change. The relevant principle is: SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics.
Question 458
A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. After implementing this change—Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
Select a controlled test incident period, generate the report, cross-check sampled event IDs with source logs and verify an authorized viewer can retrieve the same scoped result. That would help test “Build a focused SmartEvent report for a defined security investigation”, not the outcome required in this scenario. The relevant acceptance check is: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Generate a controlled new gateway log after repairing the log path, confirm its event timestamp and receipt, and check that the configured event view reflects current data rather than cached history. That would help test “Verify SmartEvent server processing after an upstream log-server change”, not the outcome required in this scenario. The relevant acceptance check is: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Create several synthetic allowed test logs that should form a configured event, inspect the raw records and correlated SmartEvent result, and verify an unrelated log is not incorrectly included. That would help test “Distinguish raw gateway logs from SmartEvent correlated security events”, not the outcome required in this scenario. The relevant acceptance check is: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions. This check is decisive because smartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics.
Question 459
A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Which proposed shortcut most directly risks missing correlated security events after a nominal monitoring server installation that never received gateway logs and should therefore be rejected?
Answer & Explanations
Correct answer: C
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Disable the gateway threat-prevention blade because SmartEvent dashboards are empty, without verifying whether its logging server still forwards events. That shortcut risks loss of investigative visibility and reduced protections after misdiagnosing a log ingestion outage as broken enforcement. Here the specific shortcut is: Deploy a VM called SmartEvent and assume it detects gateway attack patterns immediately without configuring log ingestion or event processing.
Export every available gateway log into an unfiltered public spreadsheet and label it a certified SmartEvent incident report for the management board. That shortcut risks inaccurate reporting and avoidable data exposure after bypassing event filters and report access controls. Here the specific shortcut is: Deploy a VM called SmartEvent and assume it detects gateway attack patterns immediately without configuring log ingestion or event processing.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Deploy a VM called SmartEvent and assume it detects gateway attack patterns immediately without configuring log ingestion or event processing. The foreseeable failure is missing correlated security events after a nominal monitoring server installation that never received gateway logs. The safer response is: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Assume every individual dropped packet is automatically an independently validated high-severity SmartEvent incident requiring emergency response. That shortcut risks alert noise and inaccurate incident severity after confusing raw log entries with correlated security events. Here the specific shortcut is: Deploy a VM called SmartEvent and assume it detects gateway attack patterns immediately without configuring log ingestion or event processing.
Question 460
A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. This action/test pair addresses “Verify SmartEvent server processing after an upstream log-server change”. When SmartEvent results stop updating after moving logging infrastructure, inspect log source connectivity, relevant event processing configuration and time windows before changing the protected access policy. Generate a controlled new gateway log after repairing the log path, confirm its event timestamp and receipt, and check that the configured event view reflects current data rather than cached history. The case instead calls for: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service. Confirm it through this test: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions. SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. The test would be relevant: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions. But the offered implementation—Use gateway logs for individual connection details and SmartEvent for configured aggregation and correlation of related incidents, checking source records and event definitions before treating an alert as conclusive.—addresses “Distinguish raw gateway logs from SmartEvent correlated security events”. The action needed here is: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service.
The question is set in this situation: A university security team has provisioned a new event-monitoring appliance but sees an empty SmartEvent interface despite generating firewall logs. The action is applicable: Configure an R82 SmartEvent deployment with the required supported server and management/log connections, verify licensed and enabled components where applicable, and ensure gateway security events reach the analysis service. But its proposed test—Create several synthetic allowed test logs that should form a configured event, inspect the raw records and correlated SmartEvent result, and verify an unrelated log is not incorrectly included.—addresses “Distinguish raw gateway logs from SmartEvent correlated security events”. This requirement is confirmed instead by: Generate one harmless labeled security log from a test gateway, confirm the record reaches the logging path and appears in SmartEvent search or event processing, and validate relevant collection permissions.
Check Point Certified Security Expert - R82 (CCSE) (156-315.82) Practice Tests
- Checkpoint 156-315.82 Practice Test 44 - 10 Questions (Last Reviewed 05-Oct-2026)
- Checkpoint 156-315.82 Practice Test 45 - 10 Questions (Last Reviewed 04-Oct-2026)
- Checkpoint 156-315.82 Practice Test 46 - 10 Questions (Last Reviewed 03-Oct-2026)
- Checkpoint 156-315.82 Practice Test 47 - 10 Questions (Last Reviewed 02-Oct-2026)
- Checkpoint 156-315.82 Practice Test 48 - 10 Questions (Last Reviewed 01-Oct-2026)