Question 900
Original unofficial Palo Alto Networks NetSec-Architect scenario: A multicloud corporation plans one central inspection VPC for every application and ignores cross-region transfer costs and failure domains. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A multicloud corporation plans one central inspection VPC for every application and ignores cross-region transfer costs and failure domains. Governing principle: Centralization can simplify policy but also introduce transit dependencies and added data movement. The most defensible design response is: Compare centralized and distributed cloud security insertion against latency, resiliency and data-transfer economics. Validation: The architecture assessment demonstrates eligible latency/cost tradeoffs for representative regional workloads. Sustained assurance: Review cloud flow placement after new regions are introduced
Incorrect Answers
“Test tunnel renegotiation and route convergence during HA drills.” concerns the separate design topic: design cloud ngfw operations, maintenance, vpn and decryption. It would not fix the described weakness: a multicloud corporation plans one central inspection VPC for every application and ignores cross-region transfer costs and failure domains. Centralization can simplify policy but also introduce transit dependencies and added data movement.
The suggested “Run bidirectional path validation after every TGW route update.” tests a different architectural concern: architect aws inspection insertion, gwlb, transit gateway and ha. Here, a multicloud corporation plans one central inspection VPC for every application and ignores cross-region transfer costs and failure domains. Centralization can simplify policy but also introduce transit dependencies and added data movement.
The proposed design “Require route parity checks for blue/green subnet changes.” addresses this related architecture topic: architect gcp ngfw insertion, load balancing and resilience. The actual security gap is that a multicloud corporation plans one central inspection VPC for every application and ignores cross-region transfer costs and failure domains. Centralization can simplify policy but also introduce transit dependencies and added data movement.