Question 440
Original unofficial Palo Alto Networks NetSec-Architect scenario: A service-connection cutover leaves name resolution working, but users cannot establish a TCP session to the target application. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A service-connection cutover leaves name resolution working, but users cannot establish a TCP session to the target application. Governing principle: DNS success proves address translation, not route or transport authorization. The most defensible design response is: Troubleshoot the end-to-end connector/service route, destination access policy and return path rather than treating DNS success as sufficient. Validation: A synthetic handshake succeeds in both directions and logs show the expected policy decision. Sustained assurance: Check DNS, transport and security policy separately during cutovers
Incorrect Answers
This alternative is linked to the architecture category: differentiate service connections, ztna connectors, colo-connect and ncc. The actual problem is that a service-connection cutover leaves name resolution working, but users cannot establish a TCP session to the target application; the controlling distinction is: DNS success proves address translation, not route or transport authorization.
The suggested “Check overlapping address inventory before onboarding new data centers.” tests a different architectural concern: architect regional and global prisma access private application designs. Here, a service-connection cutover leaves name resolution working, but users cannot establish a TCP session to the target application. DNS success proves address translation, not route or transport authorization.
The proposed design “Use negative destination tests before expanding remote contractor groups.” addresses this related architecture topic: architect regional and global prisma access private application designs. The actual security gap is that a service-connection cutover leaves name resolution working, but users cannot establish a TCP session to the target application. DNS success proves address translation, not route or transport authorization.