Question 40
Original unofficial Palo Alto Networks NetSec-Architect scenario: A banking application must survive a data-center failover but its inter-tier policy includes only the primary site’s address range. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A banking application must survive a data-center failover but its inter-tier policy includes only the primary site’s address range. Governing principle: Segmentation must remain consistent as topology and service placement change. The most defensible design response is: Design equivalent segmentation controls for both sites with synchronized application role identification and an explicit failover path. Validation: After controlled failover, required app-to-database sessions succeed and unauthorized lateral routes stay blocked. Sustained assurance: Include east-west deny tests in annual recovery exercises
Incorrect Answers
“Validate permitted conduits against the plant’s asset and safety inventory.” concerns the separate design topic: differentiate macrosegmentation and workload microsegmentation. It would not fix the described weakness: a banking application must survive a data-center failover but its inter-tier policy includes only the primary site’s address range. Segmentation must remain consistent as topology and service placement change.
The suggested “Review App-ID changes and application dependencies before platform upgrades.” tests a different architectural concern: differentiate authorization to specific applications. Here, a banking application must survive a data-center failover but its inter-tier policy includes only the primary site’s address range. Segmentation must remain consistent as topology and service placement change.
The proposed design “Recertify privileged role membership and review unusually broad security rules.” addresses this related architecture topic: architect identity, device posture and least-privilege controls using user-id, hip and device-id. The actual security gap is that a banking application must survive a data-center failover but its inter-tier policy includes only the primary site’s address range. Segmentation must remain consistent as topology and service placement change.