Interpreting a client-side split-tunnel routing table requires distinguishing three categories of entries: the broad, tunnel-wide default or pool-derived routes automatically installed by the GlobalProtect connection itself, host routes that fall naturally within the local LAN subnet and therefore route locally regardless of tunnel configuration, and host routes that fall entirely outside both the local LAN subnet (192.168.1.0/24) and the mobile user IP pool (172.16.72.0/23) - the latter category is the tell-tale signature of a deliberately, explicitly configured split-tunnel include route, since GlobalProtect would have no other reason to install a specific /32 host route for an address that belongs to neither the local network nor the assigned tunnel pool unless an administrator had explicitly added it as an include access route. A host address such as 9.9.9.9/32 falls squarely outside both of those ranges, so its presence as a specific /32 entry pointing into the tunnel interface is explained only by an explicit administrator-configured include route, which is exactly the conclusion in option A. By contrast, an address like 192.168.5.95 sits inside the broader local LAN addressing scheme referenced in the scenario and would be explained by local network routing behavior rather than a deliberate tunnel exclude configuration, and an address like 172.16.73.1 falls within the 172.16.72.0/23 mobile user pool itself, meaning its routing behavior is already accounted for by the pool ' s own default tunnel-inclusion behavior rather than representing a distinct, explicitly configured exclude entry.
Reference:GlobalProtect - Split Tunnel Access Route Verification via Client Routing Table.

A burst logon event, where a large branch office population authenticates and begins generating DNS lookups within a narrow five-minute window, is exactly the scenario Prisma Access ' s DNS proxy sizing limits and caching behavior are designed to withstand, and understanding those documented defaults explains user- visible behavior during onboarding rushes like this one. The DNS proxy on Prisma Access caches every resolved record it handles, not merely a curated subset of " frequently used " hostnames, for a fixed default duration of 300 seconds; this blanket caching (option D) is precisely what allows a large burst of simultaneous, repeated lookups for the same common destinations (SaaS portals, internal domains, update servers) to be served from cache rather than generating a fresh upstream query for every single request, which is critical to sustaining performance during a synchronized-logon event. The DNS proxy also has a defined ceiling on how many TCP-based DNS requests it will hold pending concurrently, documented as 64 (option B); in a large burst scenario this is the throttling limit that governs how much simultaneous TCP DNS load the proxy will queue before applying back-pressure. Option A misstates the caching behavior - caching is not selective to " frequently used " hostnames, it applies broadly for the TTL period. Option C references a retry count that is not the documented, relevant limiting factor in this burst-capacity scenario.
Reference:Prisma Access - DNS Proxy Behavior and Default Sizing Limits.

TheSASE Health Dashboardprovides visibility intouser and group synchronizationbetween theCloud Identity Engine and the Security Processing Nodes (SPNs). It allows administrators to verifywhether a group from the Cloud Identity Engine is properly fetched and available on the SPN for policy enforcement.
This feature helps in troubleshooting identity-based access control issues and ensures thatuser group mappings are correctly applied within Prisma Access.