Question 1040
Original unofficial Palo Alto Networks NetSec-Architect scenario: A high-volume service wants active-active firewall load sharing but its application maintains sensitive long-lived sessions and the team has not evaluated state synchronization. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A high-volume service wants active-active firewall load sharing but its application maintains sensitive long-lived sessions and the team has not evaluated state synchronization. Governing principle: Active-active designs introduce state and path consistency considerations that differ from active-passive. The most defensible design response is: Compare supported active-active and active-passive behavior with session flow ownership and recovery requirements. Validation: Long-lived test sessions follow the approved failover behavior during a member loss. Sustained assurance: Test representative long-lived protocols before selecting the HA mode
Incorrect Answers
“Recheck compatibility documentation before future node expansion.” concerns the separate design topic: architect private-cloud ha with active-passive, active-active and fabric options. It would not fix the described weakness: a high-volume service wants active-active firewall load sharing but its application maintains sensitive long-lived sessions and the team has not evaluated state synchronization. Active-active designs introduce state and path consistency considerations that differ from active-passive.
This alternative is linked to the architecture category: assess private-cloud edge, core and east-west microsegmentation capacity. The actual problem is that a high-volume service wants active-active firewall load sharing but its application maintains sensitive long-lived sessions and the team has not evaluated state synchronization; the controlling distinction is: active-active designs introduce state and path consistency considerations that differ from active-passive.
The proposed design “Retest failover and maintenance workflows after changing virtual NIC architecture.” addresses this related architecture topic: design vm-series across esxi, kvm and ahv with resource and acceleration choices. The actual security gap is that a high-volume service wants active-active firewall load sharing but its application maintains sensitive long-lived sessions and the team has not evaluated state synchronization. Active-active designs introduce state and path consistency considerations that differ from active-passive.