Question 480
Original unofficial Palo Alto Networks NetSec-Architect scenario: A mobile engineering group needs access to internal database clients and command-line tools, but the proposed design permits only browser traffic. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A mobile engineering group needs access to internal database clients and command-line tools, but the proposed design permits only browser traffic. Governing principle: Secure enterprise browsing alone does not transport all native application protocols. The most defensible design response is: Select a supported endpoint agent or GlobalProtect path for authorized nonbrowser private application traffic. Validation: A managed test device reaches the sanctioned database protocol while other internal services remain blocked. Sustained assurance: Validate application protocol inventories when onboarding mobile teams
Incorrect Answers
This alternative is linked to the architecture category: compare prisma browser, prisma access agent, explicit proxy and globalprotect use cases. The actual problem is that a mobile engineering group needs access to internal database clients and command-line tools, but the proposed design permits only browser traffic; the controlling distinction is: secure enterprise browsing alone does not transport all native application protocols.
The suggested “Retest route and identity continuity for high-mobility groups.” tests a different architectural concern: architect prisma access mobile-user capacity, identity and global coverage. Here, a mobile engineering group needs access to internal database clients and command-line tools, but the proposed design permits only browser traffic. Secure enterprise browsing alone does not transport all native application protocols.
The proposed design “Test connection mode compliance for each endpoint class.” addresses this related architecture topic: architect globalprotect on-demand, always on user-logon and always on pre-logon. The actual security gap is that a mobile engineering group needs access to internal database clients and command-line tools, but the proposed design permits only browser traffic. Secure enterprise browsing alone does not transport all native application protocols.