Question 400
Original unofficial Palo Alto Networks NetSec-Architect scenario: A company deploys ZTNA Connectors using wildcard hostnames but the approved set contains sensitive administration hosts matching the wildcard. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A company deploys ZTNA Connectors using wildcard hostnames but the approved set contains sensitive administration hosts matching the wildcard. Governing principle: A wildcard name pattern can expand the accessible application surface unexpectedly. The most defensible design response is: Constrain wildcard publication and associate only reviewed FQDNs or specific application destinations with permitted groups. Validation: The intended app is accessible but the administrative hostname sharing the suffix is denied. Sustained assurance: Review wildcard matches each time private DNS zones change
Incorrect Answers
“Monitor connector resource utilization and routinely test failover.” concerns the separate design topic: differentiate service connections, ztna connectors, colo-connect and ncc. It would not fix the described weakness: a company deploys ZTNA Connectors using wildcard hostnames but the approved set contains sensitive administration hosts matching the wildcard. A wildcard name pattern can expand the accessible application surface unexpectedly.
This alternative is linked to the architecture category: architect private application access through prisma browser. The actual problem is that a company deploys ZTNA Connectors using wildcard hostnames but the approved set contains sensitive administration hosts matching the wildcard; the controlling distinction is: a wildcard name pattern can expand the accessible application surface unexpectedly.
The suggested “Compare access scope, user experience and policy assurance before standardizing.” tests a different architectural concern: architect private application access through prisma browser. Here, a company deploys ZTNA Connectors using wildcard hostnames but the approved set contains sensitive administration hosts matching the wildcard. A wildcard name pattern can expand the accessible application surface unexpectedly.