Checkpoint 156-315.82 Dumps
Checkpoint 156-315.82 Practice Test 71
Question 700
A regional school district is consolidating its firewall manager into a new data center and must validate secure gateway management after an address change. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The action is applicable: After importing Security Management to a new approved appliance, check its management identity, SIC trust and reachable IP or NAT assumptions for managed gateways before resuming production policy changes. But its proposed test—Import a test export into an approved clean destination, start supported management services, open SmartConsole and compare known gateway objects and access rules with the preexport inventory.—addresses “Import the exported management database into a supported clean destination server”. This requirement is confirmed instead by: From a controlled remote gateway verify management connection and SIC health, retrieve status and install a harmless reviewed test policy after switching to the migrated server.
The question is set in this situation: A regional school district is consolidating its firewall manager into a new data center and must validate secure gateway management after an address change. After importing Security Management to a new approved appliance, check its management identity, SIC trust and reachable IP or NAT assumptions for managed gateways before resuming production policy changes. Confirm it through this test: From a controlled remote gateway verify management connection and SIC health, retrieve status and install a harmless reviewed test policy after switching to the migrated server. Migration transfers management data but a changed interface address or upstream NAT path can still prevent gateways from reaching the correct trusted management server; imported objects alone cannot fix packet routing.
The test would be relevant: From a controlled remote gateway verify management connection and SIC health, retrieve status and install a harmless reviewed test policy after switching to the migrated server. But the offered implementation—Build the supported destination Security Management Server at the intended release, satisfy official migration prerequisites, then import the verified database archive and validate service startup rather than manually recreating policy objects.—addresses “Import the exported management database into a supported clean destination server”. The action needed here is: After importing Security Management to a new approved appliance, check its management identity, SIC trust and reachable IP or NAT assumptions for managed gateways before resuming production policy changes.
This action/test pair addresses “Plan management HA peers separately when migrating the active management database”. Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment. In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions. The case instead calls for: After importing Security Management to a new approved appliance, check its management identity, SIC trust and reachable IP or NAT assumptions for managed gateways before resuming production policy changes.
Question 701
A large retailer is relocating its primary management server but also has a secondary peer whose older backup may not match the target R82 version. Which Check Point R82 security engineering action best addresses this requirement?
Answer & Explanations
Correct answer: C
Protect an exported Security Management database as sensitive configuration data, validate file integrity and transfer completeness, and restrict access to approved migration staff before importing to the destination. This addresses “Preserve management export integrity and access controls”, where the governing principle is: Management archives can contain detailed security topology and trust material; an incomplete transfer or publicly shared archive undermines both successful migration and confidentiality. The stated case instead calls for: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
After importing Security Management to a new approved appliance, check its management identity, SIC trust and reachable IP or NAT assumptions for managed gateways before resuming production policy changes. This addresses “Reconcile management SIC and gateway reachability after migrating server identity”, where the governing principle is: Migration transfers management data but a changed interface address or upstream NAT path can still prevent gateways from reaching the correct trusted management server; imported objects alone cannot fix packet routing. The stated case instead calls for: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment. Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization. Verify the result with this test: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions.
Build the supported destination Security Management Server at the intended release, satisfy official migration prerequisites, then import the verified database archive and validate service startup rather than manually recreating policy objects. This addresses “Import the exported management database into a supported clean destination server”, where the governing principle is: A database import restores management configuration into a supported installation context, while a new empty management VM has no knowledge of existing object identities, policy packages or managed gateway associations. The stated case instead calls for: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
Question 702
A large retailer is relocating its primary management server but also has a secondary peer whose older backup may not match the target R82 version. The engineer proposes the following change: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
A database import restores management configuration into a supported installation context, while a new empty management VM has no knowledge of existing object identities, policy packages or managed gateway associations. That explains “Import the exported management database into a supported clean destination server”, not the mechanism behind the described change. The relevant principle is: Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization.
Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization. The corresponding implementation is: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
Management archives can contain detailed security topology and trust material; an incomplete transfer or publicly shared archive undermines both successful migration and confidentiality. That explains “Preserve management export integrity and access controls”, not the mechanism behind the described change. The relevant principle is: Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization.
Migration transfers management data but a changed interface address or upstream NAT path can still prevent gateways from reaching the correct trusted management server; imported objects alone cannot fix packet routing. That explains “Reconcile management SIC and gateway reachability after migrating server identity”, not the mechanism behind the described change. The relevant principle is: Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization.
Question 703
A large retailer is relocating its primary management server but also has a secondary peer whose older backup may not match the target R82 version. After implementing this change—Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions. This check is decisive because management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization.
Calculate the approved archive hash on the source and destination, compare complete byte lengths, check permissions on the transfer location and verify the test target can read the intact export. That would help test “Preserve management export integrity and access controls”, not the outcome required in this scenario. The relevant acceptance check is: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions.
Import a test export into an approved clean destination, start supported management services, open SmartConsole and compare known gateway objects and access rules with the preexport inventory. That would help test “Import the exported management database into a supported clean destination server”, not the outcome required in this scenario. The relevant acceptance check is: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions.
From a controlled remote gateway verify management connection and SIC health, retrieve status and install a harmless reviewed test policy after switching to the migrated server. That would help test “Reconcile management SIC and gateway reachability after migrating server identity”, not the outcome required in this scenario. The relevant acceptance check is: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions.
Question 704
A large retailer is relocating its primary management server but also has a secondary peer whose older backup may not match the target R82 version. Which proposed shortcut most directly risks split management state and failed synchronization after combining incompatible migration and HA recovery artifacts and should therefore be rejected?
Answer & Explanations
Correct answer: D
Upload an unencrypted sensitive management database archive to an unrestricted public file share and assume its file name prevents others from inspecting network policy contents. That shortcut risks exposure of network security configuration or failed database restore due to unsafe archive handling. Here the specific shortcut is: Restore a stale standby snapshot from an unrelated software release next to the newly migrated primary and assume Check Point automatically merges both databases without peer reconfiguration.
Assume all managed gateways automatically find an imported management database on a new network address without checking connectivity, trust or NAT state. That shortcut risks remote gateways orphaned from policy management after a database migration with changed reachable management endpoint. Here the specific shortcut is: Restore a stale standby snapshot from an unrelated software release next to the newly migrated primary and assume Check Point automatically merges both databases without peer reconfiguration.
Create a new Security Management VM and assume its empty SmartConsole automatically discovers the old manager's policies and trust just because it shares a DNS name. That shortcut risks lost policy and gateway management data following cutover to an empty unpopulated destination server. Here the specific shortcut is: Restore a stale standby snapshot from an unrelated software release next to the newly migrated primary and assume Check Point automatically merges both databases without peer reconfiguration.
Restore a stale standby snapshot from an unrelated software release next to the newly migrated primary and assume Check Point automatically merges both databases without peer reconfiguration. The foreseeable failure is split management state and failed synchronization after combining incompatible migration and HA recovery artifacts. The safer response is: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
Question 705
A large retailer is relocating its primary management server but also has a secondary peer whose older backup may not match the target R82 version. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment. Confirm it through this test: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions. Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization.
This action/test pair addresses “Reconcile management SIC and gateway reachability after migrating server identity”. After importing Security Management to a new approved appliance, check its management identity, SIC trust and reachable IP or NAT assumptions for managed gateways before resuming production policy changes. From a controlled remote gateway verify management connection and SIC health, retrieve status and install a harmless reviewed test policy after switching to the migrated server. The case instead calls for: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
The test would be relevant: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions. But the offered implementation—Build the supported destination Security Management Server at the intended release, satisfy official migration prerequisites, then import the verified database archive and validate service startup rather than manually recreating policy objects.—addresses “Import the exported management database into a supported clean destination server”. The action needed here is: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
The action is applicable: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment. But its proposed test—Import a test export into an approved clean destination, start supported management services, open SmartConsole and compare known gateway objects and access rules with the preexport inventory.—addresses “Import the exported management database into a supported clean destination server”. This requirement is confirmed instead by: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions.
Question 706
A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Which Check Point R82 security engineering action best addresses this requirement?
Answer & Explanations
Correct answer: D
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. After importing Security Management to a new approved appliance, check its management identity, SIC trust and reachable IP or NAT assumptions for managed gateways before resuming production policy changes. This addresses “Reconcile management SIC and gateway reachability after migrating server identity”, where the governing principle is: Migration transfers management data but a changed interface address or upstream NAT path can still prevent gateways from reaching the correct trusted management server; imported objects alone cannot fix packet routing. The stated case instead calls for: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
Use the management migration utility package supplied for the intended newer target release when importing from an older management version, and review official migration compatibility notes and backup prerequisites. This addresses “Choose migration tools compatible with the target management release”, where the governing principle is: The migration tool's supported target software version matters when schema versions differ; using an arbitrary old utility can produce an export that a newer manager cannot safely import. The stated case instead calls for: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Build the supported destination Security Management Server at the intended release, satisfy official migration prerequisites, then import the verified database archive and validate service startup rather than manually recreating policy objects. This addresses “Import the exported management database into a supported clean destination server”, where the governing principle is: A database import restores management configuration into a supported installation context, while a new empty management VM has no knowledge of existing object identities, policy packages or managed gateway associations. The stated case instead calls for: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment. Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization. Verify the result with this test: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions.
Question 707
A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. The engineer proposes the following change: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
The migration tool's supported target software version matters when schema versions differ; using an arbitrary old utility can produce an export that a newer manager cannot safely import. That explains “Choose migration tools compatible with the target management release”, not the mechanism behind the described change. The relevant principle is: Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization.
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. A database import restores management configuration into a supported installation context, while a new empty management VM has no knowledge of existing object identities, policy packages or managed gateway associations. That explains “Import the exported management database into a supported clean destination server”, not the mechanism behind the described change. The relevant principle is: Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization.
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization. The corresponding implementation is: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Migration transfers management data but a changed interface address or upstream NAT path can still prevent gateways from reaching the correct trusted management server; imported objects alone cannot fix packet routing. That explains “Reconcile management SIC and gateway reachability after migrating server identity”, not the mechanism behind the described change. The relevant principle is: Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization.
Question 708
A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. After implementing this change—Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Import a test export into an approved clean destination, start supported management services, open SmartConsole and compare known gateway objects and access rules with the preexport inventory. That would help test “Import the exported management database into a supported clean destination server”, not the outcome required in this scenario. The relevant acceptance check is: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions.
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions. This check is decisive because management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization.
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. From a controlled remote gateway verify management connection and SIC health, retrieve status and install a harmless reviewed test policy after switching to the migrated server. That would help test “Reconcile management SIC and gateway reachability after migrating server identity”, not the outcome required in this scenario. The relevant acceptance check is: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions.
Confirm source and target versions in a staging migration, select the supported target-release tool, inspect export and import logs, and verify a representative object and rule survive the transfer. That would help test “Choose migration tools compatible with the target management release”, not the outcome required in this scenario. The relevant acceptance check is: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions.
Question 709
A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Which proposed shortcut most directly risks split management state and failed synchronization after combining incompatible migration and HA recovery artifacts and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Restore a stale standby snapshot from an unrelated software release next to the newly migrated primary and assume Check Point automatically merges both databases without peer reconfiguration. The foreseeable failure is split management state and failed synchronization after combining incompatible migration and HA recovery artifacts. The safer response is: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
Use any old migrate utility found in a previous appliance backup to perform every future major-version management migration regardless of target release compatibility. That shortcut risks failed import or corrupted migrated management state after using a migration tool incompatible with the intended destination. Here the specific shortcut is: Restore a stale standby snapshot from an unrelated software release next to the newly migrated primary and assume Check Point automatically merges both databases without peer reconfiguration.
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Assume all managed gateways automatically find an imported management database on a new network address without checking connectivity, trust or NAT state. That shortcut risks remote gateways orphaned from policy management after a database migration with changed reachable management endpoint. Here the specific shortcut is: Restore a stale standby snapshot from an unrelated software release next to the newly migrated primary and assume Check Point automatically merges both databases without peer reconfiguration.
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Create a new Security Management VM and assume its empty SmartConsole automatically discovers the old manager's policies and trust just because it shares a DNS name. That shortcut risks lost policy and gateway management data following cutover to an empty unpopulated destination server. Here the specific shortcut is: Restore a stale standby snapshot from an unrelated software release next to the newly migrated primary and assume Check Point automatically merges both databases without peer reconfiguration.
Question 710
A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
This action/test pair addresses “Import the exported management database into a supported clean destination server”. Build the supported destination Security Management Server at the intended release, satisfy official migration prerequisites, then import the verified database archive and validate service startup rather than manually recreating policy objects. Import a test export into an approved clean destination, start supported management services, open SmartConsole and compare known gateway objects and access rules with the preexport inventory. The case instead calls for: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
The question is set in this situation: A hospital's management migration change includes an HA pair and requires a controlled synchronization rehearsal after the new primary is commissioned. Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment. Confirm it through this test: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions. Management HA relies on compatible synchronized databases and identities; replacing the primary management installation can require reestablishing supported standby peer relationships and initial synchronization.
The test would be relevant: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions. But the offered implementation—After importing Security Management to a new approved appliance, check its management identity, SIC trust and reachable IP or NAT assumptions for managed gateways before resuming production policy changes.—addresses “Reconcile management SIC and gateway reachability after migrating server identity”. The action needed here is: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment.
The action is applicable: Coordinate the primary-management migration with a supported secondary-server recovery or reinstallation plan, preserving correct HA roles and synchronization rather than restoring mismatched peer databases into a partially migrated environment. But its proposed test—From a controlled remote gateway verify management connection and SIC health, retrieve status and install a harmless reviewed test policy after switching to the migrated server.—addresses “Reconcile management SIC and gateway reachability after migrating server identity”. This requirement is confirmed instead by: In a lab migrate the primary management database, bring a compatible secondary peer into the supported HA configuration, perform an initial sync and verify Active and Standby roles and matching policy revisions.
Check Point Certified Security Expert - R82 (CCSE) (156-315.82) Practice Tests
- Checkpoint 156-315.82 Practice Test 69 - 10 Questions (Last Reviewed 06-Nov-2026)
- Checkpoint 156-315.82 Practice Test 70 - 10 Questions (Last Reviewed 05-Nov-2026)
- Checkpoint 156-315.82 Practice Test 71 - 10 Questions (Last Reviewed 04-Nov-2026)
- Checkpoint 156-315.82 Practice Test 72 - 10 Questions (Last Reviewed 03-Nov-2026)
- Checkpoint 156-315.82 Practice Test 73 - 10 Questions (Last Reviewed 02-Nov-2026)