Question 600
Original unofficial Palo Alto Networks NetSec-Architect scenario: A branch receives a new local ISP prefix and cloud security tunnels fail because the branch NAT assumptions were hard-coded. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A branch receives a new local ISP prefix and cloud security tunnels fail because the branch NAT assumptions were hard-coded. Governing principle: Branch overlay health depends on the underlay and NAT behavior used to establish encrypted sessions. The most defensible design response is: Review underlay/NAT reachability and update the supported tunnel and route configuration for the changed carrier. Validation: Both primary and backup tunnels establish and application flows retain the expected source identity. Sustained assurance: Monitor carrier addressing changes and rehearse renewal scenarios
Incorrect Answers
“Audit template compliance after each deployment batch.” concerns the separate design topic: design branch sase and sd-wan architectures, availability and experience monitoring. It would not fix the described weakness: a branch receives a new local ISP prefix and cloud security tunnels fail because the branch NAT assumptions were hard-coded. Branch overlay health depends on the underlay and NAT behavior used to establish encrypted sessions.
This alternative is linked to the architecture category: evaluate prisma sd-wan identity, device and threat services. The actual problem is that a branch receives a new local ISP prefix and cloud security tunnels fail because the branch NAT assumptions were hard-coded; the controlling distinction is: branch overlay health depends on the underlay and NAT behavior used to establish encrypted sessions.
The proposed design “Validate guest-to-corporate deny tests per location.” addresses this related architecture topic: evaluate prisma sd-wan identity, device and threat services. The actual security gap is that a branch receives a new local ISP prefix and cloud security tunnels fail because the branch NAT assumptions were hard-coded. Branch overlay health depends on the underlay and NAT behavior used to establish encrypted sessions.