Checkpoint 156-315.82 Dumps
Checkpoint 156-315.82 Practice Test 48
Question 470
A regional media provider is validating which gateway messages appear as aggregated SmartEvent alerts rather than ordinary per-connection records. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The question is set in this situation: A regional media provider is validating which gateway messages appear as aggregated SmartEvent alerts rather than ordinary per-connection records. This action/test pair addresses “Scope SmartEvent access separately from security policy editing privileges”. Grant security analysts the appropriate permissions to view and investigate events without unnecessarily giving them policy administration or management-server upgrade rights, then verify event access from a nonadmin account. Sign in as a test analyst, open approved SmartEvent reports and alert details, attempt an unrelated policy modification and verify it remains denied. The case instead calls for: 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.
The question is set in this situation: A regional media provider is validating which gateway messages appear as aggregated SmartEvent alerts rather than ordinary per-connection records. The action is applicable: 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. But its proposed test—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.—addresses “Verify SmartEvent server processing after an upstream log-server change”. This requirement is confirmed instead by: 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.
The question is set in this situation: A regional media provider is validating which gateway messages appear as aggregated SmartEvent alerts rather than ordinary per-connection records. 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. Confirm it through this 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. 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 question is set in this situation: A regional media provider is validating which gateway messages appear as aggregated SmartEvent alerts rather than ordinary per-connection records. The test would be relevant: 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. But the offered implementation—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.—addresses “Verify SmartEvent server processing after an upstream log-server change”. The action needed here is: 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.
Question 471
A public-sector SOC recently migrated log storage and reports no recent SmartEvent incidents although gateway access policies work. Which Check Point R82 security engineering action best addresses this requirement?
Answer & Explanations
Correct answer: D
Configure alert action and reporting destinations for approved SmartEvent high-priority events, set clear ownership and escalation criteria, and verify notifications arrive without exposing sensitive logs to unapproved recipients. This addresses “Route SmartEvent critical alerts to an authorized responder workflow”, where the governing principle is: Creating a visible event in SmartEvent is not the same as routing a notification to on-call staff, and unreviewed distribution lists can reveal confidential security details. The stated case instead calls for: 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.
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. This addresses “Deploy SmartEvent with the correct security log ingestion path”, where the governing 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 stated case instead calls for: 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.
Grant security analysts the appropriate permissions to view and investigate events without unnecessarily giving them policy administration or management-server upgrade rights, then verify event access from a nonadmin account. This addresses “Scope SmartEvent access separately from security policy editing privileges”, where the governing principle is: Monitoring visibility and policy-control capabilities are separate operational duties; an account able to open reports should not automatically gain unrestricted authority over gateway configuration. The stated case instead calls for: 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.
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. 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. Verify the result with this test: 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.
Question 472
A public-sector SOC recently migrated log storage and reports no recent SmartEvent incidents although gateway access policies work. The engineer proposes the following 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
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 corresponding implementation is: 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.
Monitoring visibility and policy-control capabilities are separate operational duties; an account able to open reports should not automatically gain unrestricted authority over gateway configuration. That explains “Scope SmartEvent access separately from security policy editing privileges”, not the mechanism behind the described change. The relevant 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.
Creating a visible event in SmartEvent is not the same as routing a notification to on-call staff, and unreviewed distribution lists can reveal confidential security details. That explains “Route SmartEvent critical alerts to an authorized responder workflow”, not the mechanism behind the described change. The relevant 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.
SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics. That explains “Deploy SmartEvent with the correct security log ingestion path”, not the mechanism behind the described change. The relevant 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.
Question 473
A public-sector SOC recently migrated log storage and reports no recent SmartEvent incidents although gateway access policies work. After implementing this 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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
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. This check is decisive because 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.
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. That would help test “Deploy SmartEvent with the correct security log ingestion path”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Trigger a harmless sample critical event in a test environment, verify the expected on-call group receives the approved alert and a noncritical event does not page unrelated staff. That would help test “Route SmartEvent critical alerts to an authorized responder workflow”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Sign in as a test analyst, open approved SmartEvent reports and alert details, attempt an unrelated policy modification and verify it remains denied. That would help test “Scope SmartEvent access separately from security policy editing privileges”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 474
A public-sector SOC recently migrated log storage and reports no recent SmartEvent incidents although gateway access policies work. Which proposed shortcut most directly risks loss of investigative visibility and reduced protections after misdiagnosing a log ingestion outage as broken enforcement and should therefore be rejected?
Answer & Explanations
Correct answer: B
Give all event-monitoring analysts administrator-level access to every Quantum gateway because they need to read SmartEvent dashboards. That shortcut risks unnecessary administrative privilege expansion caused by conflating event analysis and enforcement configuration. Here the specific shortcut is: Disable the gateway threat-prevention blade because SmartEvent dashboards are empty, without verifying whether its logging server still forwards events.
Disable the gateway threat-prevention blade because SmartEvent dashboards are empty, without verifying whether its logging server still forwards events. The foreseeable failure is loss of investigative visibility and reduced protections after misdiagnosing a log ingestion outage as broken enforcement. The safer response is: 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.
Assume opening a SmartEvent dashboard every morning is equivalent to a tested urgent alert notification and incident escalation procedure. That shortcut risks slow response to critical security incidents after relying on passive monitoring without validated notifications. Here the specific shortcut is: Disable the gateway threat-prevention blade because SmartEvent dashboards are empty, without verifying whether its logging server still forwards events.
Deploy a VM called SmartEvent and assume it detects gateway attack patterns immediately without configuring log ingestion or event processing. That shortcut risks missing correlated security events after a nominal monitoring server installation that never received gateway logs. Here the specific shortcut is: Disable the gateway threat-prevention blade because SmartEvent dashboards are empty, without verifying whether its logging server still forwards events.
Question 475
A public-sector SOC recently migrated log storage and reports no recent SmartEvent incidents although gateway access policies work. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The test would be relevant: 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. But the offered implementation—Grant security analysts the appropriate permissions to view and investigate events without unnecessarily giving them policy administration or management-server upgrade rights, then verify event access from a nonadmin account.—addresses “Scope SmartEvent access separately from security policy editing privileges”. The action needed here is: 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 action/test pair addresses “Deploy SmartEvent with the correct security log ingestion path”. 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 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 case instead calls for: 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.
The action is applicable: 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. But its proposed test—Sign in as a test analyst, open approved SmartEvent reports and alert details, attempt an unrelated policy modification and verify it remains denied.—addresses “Scope SmartEvent access separately from security policy editing privileges”. This requirement is confirmed instead by: 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.
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. Confirm it through this test: 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. 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.
Question 476
An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. Which Check Point R82 security engineering action best addresses this requirement?
Answer & Explanations
Correct answer: C
The question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. Grant security analysts the appropriate permissions to view and investigate events without unnecessarily giving them policy administration or management-server upgrade rights, then verify event access from a nonadmin account. This addresses “Scope SmartEvent access separately from security policy editing privileges”, where the governing principle is: Monitoring visibility and policy-control capabilities are separate operational duties; an account able to open reports should not automatically gain unrestricted authority over gateway configuration. The stated case instead calls for: 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.
The question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. 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. This addresses “Deploy SmartEvent with the correct security log ingestion path”, where the governing 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 stated case instead calls for: 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.
The question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. 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. 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. Verify the result with this test: 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.
Define a supported SmartEvent event rule for a specific repeated high-severity security pattern, set suitable correlation criteria and alert thresholds, then test it with safe synthetic logs. This addresses “Create a SmartEvent event rule for a measurable high-severity pattern”, where the governing principle is: Correlation thresholds identify meaningful clusters of records, while generic alerting on every low-severity log can overwhelm responders without improving detection. The stated case instead calls for: 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.
Question 477
An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. The engineer proposes the following 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
The question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. 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 corresponding implementation is: 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.
The question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. SmartEvent correlates events from ingested security logs; simply creating a server object without a working log stream does not provide meaningful threat analytics. That explains “Deploy SmartEvent with the correct security log ingestion path”, not the mechanism behind the described change. The relevant 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.
Correlation thresholds identify meaningful clusters of records, while generic alerting on every low-severity log can overwhelm responders without improving detection. That explains “Create a SmartEvent event rule for a measurable high-severity pattern”, not the mechanism behind the described change. The relevant 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 question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. Monitoring visibility and policy-control capabilities are separate operational duties; an account able to open reports should not automatically gain unrestricted authority over gateway configuration. That explains “Scope SmartEvent access separately from security policy editing privileges”, not the mechanism behind the described change. The relevant 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.
Question 478
An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. After implementing this 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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
The question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. 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. That would help test “Deploy SmartEvent with the correct security log ingestion path”, not the outcome required in this scenario. The relevant acceptance check is: 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 question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. Sign in as a test analyst, open approved SmartEvent reports and alert details, attempt an unrelated policy modification and verify it remains denied. That would help test “Scope SmartEvent access separately from security policy editing privileges”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Generate a controlled series of test events that meets the rule's time window and count, confirm a single actionable alert is issued, and verify low-volume benign samples do not trigger it. That would help test “Create a SmartEvent event rule for a measurable high-severity pattern”, not the outcome required in this scenario. The relevant acceptance check is: 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 question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. 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. This check is decisive because 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.
Question 479
An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. Which proposed shortcut most directly risks loss of investigative visibility and reduced protections after misdiagnosing a log ingestion outage as broken enforcement and should therefore be rejected?
Answer & Explanations
Correct answer: C
The question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. Give all event-monitoring analysts administrator-level access to every Quantum gateway because they need to read SmartEvent dashboards. That shortcut risks unnecessary administrative privilege expansion caused by conflating event analysis and enforcement configuration. Here the specific shortcut is: Disable the gateway threat-prevention blade because SmartEvent dashboards are empty, without verifying whether its logging server still forwards events.
Create an always-fire SmartEvent rule for every benign allow log and assume a larger number of alerts directly proves better threat detection. That shortcut risks SOC alert fatigue after an excessively broad event definition generates constant unactionable notifications. Here the specific shortcut is: Disable the gateway threat-prevention blade because SmartEvent dashboards are empty, without verifying whether its logging server still forwards events.
The question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. Disable the gateway threat-prevention blade because SmartEvent dashboards are empty, without verifying whether its logging server still forwards events. The foreseeable failure is loss of investigative visibility and reduced protections after misdiagnosing a log ingestion outage as broken enforcement. The safer response is: 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.
The question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. Deploy a VM called SmartEvent and assume it detects gateway attack patterns immediately without configuring log ingestion or event processing. That shortcut risks missing correlated security events after a nominal monitoring server installation that never received gateway logs. Here the specific shortcut is: Disable the gateway threat-prevention blade because SmartEvent dashboards are empty, without verifying whether its logging server still forwards events.
Question 480
An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. 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: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. The test would be relevant: 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. But the offered implementation—Grant security analysts the appropriate permissions to view and investigate events without unnecessarily giving them policy administration or management-server upgrade rights, then verify event access from a nonadmin account.—addresses “Scope SmartEvent access separately from security policy editing privileges”. The action needed here is: 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.
The question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. 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. Confirm it through this test: 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. 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 question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. The action is applicable: 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. But its proposed test—Sign in as a test analyst, open approved SmartEvent reports and alert details, attempt an unrelated policy modification and verify it remains denied.—addresses “Scope SmartEvent access separately from security policy editing privileges”. This requirement is confirmed instead by: 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 question is set in this situation: An insurer's monitoring team sees SmartEvent stop updating following a management maintenance window and needs to verify source logs before making enforcement changes. This action/test pair addresses “Deploy SmartEvent with the correct security log ingestion path”. 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 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 case instead calls for: 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.
Check Point Certified Security Expert - R82 (CCSE) (156-315.82) Practice Tests
- 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)
- Checkpoint 156-315.82 Practice Test 49 - 10 Questions (Last Reviewed 30-Sep-2026)
- Checkpoint 156-315.82 Practice Test 50 - 10 Questions (Last Reviewed 29-Sep-2026)