Question 780
Original unofficial Palo Alto Networks NetSec-Architect scenario: A water utility has two geographically separate pump stations but collects telemetry only from the main plant switch. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A water utility has two geographically separate pump stations but collects telemetry only from the main plant switch. Governing principle: Network locality limits what a central packet observer can discover. The most defensible design response is: Deploy appropriately distributed sensing or approved metadata collection for each isolated station. Validation: Each station’s test device appears with the correct site attribution in Device Security records. Sustained assurance: Audit remote station traffic feeds against the site inventory
Incorrect Answers
“Trend span-drop counters and sensor ingestion lag.” concerns the separate design topic: differentiate iot sensor placement and passive traffic visibility. It would not fix the described weakness: a water utility has two geographically separate pump stations but collects telemetry only from the main plant switch. Network locality limits what a central packet observer can discover.
The suggested “Identify unobserved local switch-only traffic before claiming full store coverage.” tests a different architectural concern: design device visibility through ngfw, metadata collectors and sd-wan. Here, a water utility has two geographically separate pump stations but collects telemetry only from the main plant switch. Network locality limits what a central packet observer can discover.
The proposed design “Document collection coverage for virtual and physical warehouse segments.” addresses this related architecture topic: design device visibility through ngfw, metadata collectors and sd-wan. The actual security gap is that a water utility has two geographically separate pump stations but collects telemetry only from the main plant switch. Network locality limits what a central packet observer can discover.