Question 800
Original unofficial Palo Alto Networks NetSec-Architect scenario: A cloud-hosted warehouse has east-west IoT traffic that never passes the branch SD-WAN edge, so central asset analytics are incomplete. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A cloud-hosted warehouse has east-west IoT traffic that never passes the branch SD-WAN edge, so central asset analytics are incomplete. Governing principle: SD-WAN edge telemetry cannot describe flows that remain inside another forwarding domain. The most defensible design response is: Add a supported virtual metadata collector or visibility tap at the workload segment where those flows occur. Validation: Synthetic local IoT-to-controller traffic appears in the asset console after collector activation. Sustained assurance: Document collection coverage for virtual and physical warehouse segments
Incorrect Answers
“Check capture interfaces after hypervisor upgrades.” concerns the separate design topic: design device visibility through ngfw, metadata collectors and sd-wan. It would not fix the described weakness: a cloud-hosted warehouse has east-west IoT traffic that never passes the branch SD-WAN edge, so central asset analytics are incomplete. SD-WAN edge telemetry cannot describe flows that remain inside another forwarding domain.
The suggested “Trend span-drop counters and sensor ingestion lag.” tests a different architectural concern: differentiate iot sensor placement and passive traffic visibility. Here, a cloud-hosted warehouse has east-west IoT traffic that never passes the branch SD-WAN edge, so central asset analytics are incomplete. SD-WAN edge telemetry cannot describe flows that remain inside another forwarding domain.
The proposed design “Track unpatchable device exceptions and planned replacement dates.” addresses this related architecture topic: architect iot and ot device security visibility, risk and enforcement. The actual security gap is that a cloud-hosted warehouse has east-west IoT traffic that never passes the branch SD-WAN edge, so central asset analytics are incomplete. SD-WAN edge telemetry cannot describe flows that remain inside another forwarding domain.