The Prisma Access Locations insight within Strata Cloud Manager gives administrators a per-location, real-time operational view of each deployed compute location — effectively each SPN — including bandwidth consumption, connectivity status, and, critically, User-ID and group mapping information for that specific location. Selecting an individual location surfaces a dedicated widget where an administrator can search mappings by username or by user group, directly confirming whether a particular group synchronized from the Cloud Identity Engine has actually propagated to and is recognized by that node — precisely the verification task described in the question. This location-scoped, per-node group visibility is what makes option C the correct choice, as the other three named features operate at a different level of granularity. The SASE Health Dashboard (option A) is oriented toward infrastructure and service health signals — tunnel status, latency, packet loss — not user or group identity data. User Activity Insights (option B) and Region Activity Insights (option D) are not the tools used for this specific per-SPN group-presence check; user activity reporting in Strata Cloud Manager focuses on traffic, application, and behavioral trends rather than confirming raw group synchronization state on an individual processing node. When troubleshooting group-based policy that appears not to be matching for users in a specific region, checking the Prisma Access Locations view for that location is the documented first step.

Domain-based split tunneling behaves fundamentally differently from traditional access-route-based split tunneling: where access-route tunneling operates purely through entries in the local operating system routing table, domain-based split tunneling is implemented through a filter driver on Windows and a network extension on macOS that intercepts and redirects connections dynamically as domains are resolved and matched, rather than by inserting static host routes the administrator or user can simply read from a routing table. Because the enforcement mechanism itself lives inside this filter driver/extension rather than in visible routing entries, the documented, reliable way to confirm the configuration has actually been pushed correctly and is being applied as expected is to collect detailed, dump-level GlobalProtect application logs, which expose the filter driver ' s internal decision-making for the specified domain — this is precisely option B, and it matches Palo Alto Networks ' own published troubleshooting guidance for this feature. Checking the routing table (option A) is the correct verification method for route-based (access-route) split tunneling, but it is explicitly documented as not reflective of domain-based split tunnel behavior, since no corresponding static route is guaranteed to appear there. Verifying DNS resolution alone (option C) confirms name resolution occurred, but not that the filter driver actually applied the correct include/exclude action to the resulting session. Pinging the domain (option D) is unreliable because split-tunneling rules apply to TCP/UDP traffic and explicitly do not govern ICMP, so a ping result does not validate split-tunnel enforcement at all.

Security policy evaluation in Strata Cloud Manager follows a hierarchical precedence based on configuration scope, and rules placed in a broader or higher-level scope are evaluated before rules placed in a more specific, lower-level folder such as Mobile Users or a particular connection type. If the new Web Security rule restricting the user group was created within a lower-level, more specific scope, it will not be reached at all whenever traffic first matches a broader, higher-level allow rule earlier in the evaluation order — the higher-level rule effectively wins by virtue of being processed first, and policy lookup stops at the first match. That is exactly the behavior described in the scenario: blocked applications continue to be reachable because a rule elsewhere in the hierarchy, evaluated ahead of the newly created restriction, is already permitting the traffic. This makes option D the accurate description of the root cause. Option C describes the reverse relationship and does not match how rule hierarchy actually influences precedence in this platform. Improper threat management settings (option A) would affect logging or blocking behavior for identified threats, not whether the URL/application access rule is evaluated at all, so it does not explain complete rule bypass. Option B is a plausible but unsubstantiated guess about scope targeting; the scenario gives no indication the rule was misapplied to a connection type rather than a hierarchy level, whereas rule-order precedence is the classic, most common cause of " rule appears configured correctly but has no effect. "

GlobalProtect is the correct mobile-user connection method here because the requirement explicitly calls for remote site connectivity from mobile users to the branch locations, in addition to internet filtering and data center access — a full-tunnel capability that Explicit Proxy, which is scoped to web/proxy-aware traffic only, cannot provide. Remote Networks is the purpose-built onboarding method for the branch locations, tunneling their traffic into Prisma Access over IPSec for consistent internet filtering and, through the shared backbone, reachability to data center resources. Service connections are the piece that stitches both populations to the data center: they terminate at the customer ' s HQ/data center and, once established, become reachable from both the GlobalProtect mobile user pool and the Remote Networks locations across the Prisma Access backbone, satisfying the data center connectivity requirement for both user types without requiring a dedicated tunnel per site. Option B and D are eliminated because Explicit Proxy cannot deliver full network-layer access to internal branch or data center resources; it is designed for outbound web traffic redirection via PAC file or forwarding profile, not IPSec-based site-to-site or full-tunnel remote access. Option C omits Remote Networks entirely, which would leave the branch offices unconnected. GlobalProtect plus Remote Networks plus service connections is the standard, minimal-footprint design pattern for this exact hybrid mobile-user/branch/data-center topology.

The question specifically asks for components that provide data center connectivity over the internet, which is the distinguishing factor between the four options. Service connections are the classic IPSec-based method: they build an encrypted tunnel from the customer ' s data center edge device to Prisma Access across the public internet, requiring no private circuit. ZTNA Connector achieves the same outcome through a different architecture — a lightweight, outbound-only connector deployed in the data center that establishes a secure, brokered tunnel to the nearest Prisma Access cloud gateway, again entirely over the internet, without requiring inbound firewall rules or a traditional IPSec peer. Both are therefore valid answers. Colo-Connect is explicitly excluded because it is built for the opposite use case: it delivers private, high-bandwidth connectivity to data centers using GCP Dedicated or Partner Interconnects, bypassing the public internet entirely to achieve up to 100 Gbps with lower latency and jitter — the architecture exists specifically because customers want to avoid internet transport for their highest-throughput sites. SD-WAN Connector is not a genuine Prisma Access private-application access method; Prisma SD-WAN integrates with Prisma Access through ION devices acting as CPE for remote networks or service connections, not as a distinct " connector " component in this context, so it does not belong in this answer set.

When authentication moves from LDAP-based Windows Active Directory to SAML with Microsoft Entra ID, the identity string the firewall receives for a given user typically changes format — Active Directory–style LDAP authentication commonly surfaces usernames in a sAMAccountName or domain\username form, while SAML assertions from Entra ID typically populate the NameID or subject using userPrincipalName (an email-style identifier). If group mapping was originally built and is still configured to match on the older AD-style attribute, it will no longer correctly correlate the identity string now being delivered via SAML with the correct directory group membership, causing existing group-based Security policy rules to stop matching even though authentication itself succeeds. The fix is to update the group mapping ' s User Attributes configuration so that it recognizes and correlates on userPrincipalName, aligning the attribute used for matching with the format Entra ID actually returns — this is precisely what option C describes and directly resolves the mismatch. Configuring a redistribution profile from the old GlobalProtect firewalls (option A) addresses migrating stale mapping data from the legacy platform, not the fundamental attribute-format mismatch introduced by switching to Entra ID SAML. Migrating group mapping to the Cloud Identity Engine via an AD query agent (option B) does not resolve the issue either, since the root problem is the mismatched attribute used for correlation, not the source of the group data itself. Changing the SAML Username Modifier (option D) affects how the username is formatted for display or session purposes, not how group mapping attribute correlation is performed for policy matching.

Regardless of which client experience is used to reach a private application — full-tunnel GlobalProtect, PAB, or another connection method — the actual pathway from the Prisma Access cloud infrastructure into a customer ' s private data center resources is built using one of two purpose-built private-access connectivity components: Service Connections, the traditional IPSec-tunnel-based method that joins the data center network directly to the Prisma Access backbone, and the ZTNA Connector, a more modern, outbound-initiated, brokered-tunnel alternative that avoids the need for a traditional IPSec peer or inbound firewall exposure. Both are explicitly documented as valid mechanisms for establishing reachability to internal, private application resources, and PAB itself relies on whichever of these has been configured to actually reach the backend application once user access is authorized — making options B and D the correct pair. Explicit Proxy (option A) is a mobile-user connection method for redirecting outbound internet and SaaS traffic through Prisma Access; it is not an infrastructure component used to establish inbound reachability to private data center applications, and conflating the two would be an architectural mismatch. Privileged Remote Access (option C) is not a standard Prisma Access infrastructure connectivity component in this context; it does not appear as a documented mechanism for establishing the backbone-to-data-center pathway that PAB depends on for reaching private applications.

IKE and IPSec negotiation events — including successful and failed Phase 1 (IKE SA) and Phase 2 (IPSec SA) exchanges, proposal mismatches, and negotiation timeouts — are recorded by PAN-OS as System log entries, not as part of the Traffic, Tunnel, or Decrypt log facilities, which each capture a different category of information. Because Phase 1 has already completed successfully in this scenario but Phase 2 negotiation appears to be failing or stalling, the actual diagnostic detail explaining why — such as a proxy-ID/traffic-selector mismatch, an unsupported Phase 2 encryption or authentication algorithm, or a PFS group mismatch between the CPE and Prisma Access — will be recorded as a specific IKE/IPSec negotiation message in System logs, making option B the correct log facility to review. Decrypt logs (option A) capture SSL/TLS decryption events for inspected web traffic and have no relevance to IPSec tunnel negotiation, which is a separate control-plane process entirely. Traffic logs (option C) record session-level information for traffic that has already been successfully permitted through a completed policy match; since the tunnel ' s data plane is not yet fully established, there is no session traffic to log in the first place. Tunnel logs (option D) generally reflect the operational status and utilization of an already-established tunnel, not the underlying IKE/IPSec negotiation failure detail needed to diagnose why Phase 2 never completed.

Pre-logon connections occur before any user has authenticated to the endpoint, which means there is no logged-in user context or user certificate store available for GlobalProtect to draw from at that point in the boot sequence — authentication must instead rely on machine-level identity. For this reason, the certificate used to establish a pre-logon connection must reside in the Machine Certificate Store rather than a user-specific certificate store, since the machine store is accessible to system-level processes and services regardless of whether a user session has started, which is exactly what pre-logon requires. This makes option C the correct, foundational requirement for pre-logon certificate deployment. Option A is incorrect because Prisma Access and GlobalProtect fully support internally issued or enterprise CA-signed certificates for client authentication; there is no requirement that a public CA sign these certificates, and in most enterprise deployments an internal PKI is actually the norm for machine certificates used in pre-logon scenarios. Option B is not an accurate, distinguishing requirement specific to pre-logon; standard certificate practices around Subject and Subject Alternative Name fields apply broadly to certificate usage but are not framed in Palo Alto Networks documentation as a unique pre-logon-specific mandate. Option D is incorrect because pre-logon, by its very nature, occurs before the GlobalProtect agent has a fully interactive user session running; certificate distribution for pre-logon is handled through the machine ' s certificate deployment process (such as group policy or an enterprise PKI/MDM tool), not through the GlobalProtect agent itself pushing certificates.

With the IPSec tunnel already established, the underlying transport connectivity is confirmed to be working correctly, which narrows the troubleshooting focus specifically to the BGP session parameters themselves rather than network reachability. Two configuration values are the most common and immediate causes of a BGP peer failing to come up even over a healthy tunnel: the MD5 authentication secret, if BGP authentication is enabled on either side, must match exactly between Prisma Access and the customer ' s CPE, since any mismatch causes the peer session to be silently rejected during the initial OPEN message exchange, matching option A. Equally critical is the Peer AS Number — if the AS number configured on either the Prisma Access side or the CPE side does not match what the other side expects for that specific peering relationship, the BGP session will never successfully establish, regardless of how correctly every other setting is configured, matching option C. MRAI (Minimum Route Advertisement Interval) timers, referenced in option B, govern how frequently route updates are sent once a BGP session is already established and exchanging routes — they have no bearing on whether the initial peer session comes up in the first place, making them irrelevant to this specific symptom. The Advertise Default Route checkbox (option D) controls whether Prisma Access advertises a 0.0.0.0/0 route once peering is functional; it is a route-advertisement behavior setting, not a prerequisite for the BGP peer session itself to establish.