Native RBI by Palo Alto Networks is built directly on top of the existing URL Access Management framework rather than introducing a separate, parallel policy construct: an administrator creates or updates a URL Access Management profile, selects the specific URL website categories that should undergo isolation, and associates an isolation profile with those categories to define what browser actions (copy/paste, uploads, downloads, printing) are permitted during the isolated session. That URL Access Management profile is then applied to a Security policy rule the same way any other URL filtering profile would be, which is precisely the configuration path option A describes and is confirmed by Palo Alto Networks ' own RBI configuration documentation. Option D is close but structurally imprecise - a Security policy rule alone, without a properly configured URL Access Management profile carrying the " Isolate " site access action for the relevant categories, is not sufficient; the isolation logic itself lives in the profile object, not as a directly assignable Security policy action independent of that profile. There is no DNS Security profile mechanism for triggering isolation (option B); DNS Security governs DNS-based threat detection and sinkholing, an entirely separate capability unrelated to browser isolation triggers. Option C inverts the actual object relationship: an isolation profile is attached to the URL Access Management profile, not the reverse, so describing an " RBI profile applied to the URL access management profile " as the defining element misstates which object drives which.
Reference:Remote Browser Isolation - Configure RBI (Strata Cloud Manager), URL Access Management Profiles.

Prisma Access is architected as a cloud-delivered, fully managed service, and Palo Alto Networks performs infrastructure and software maintenance, including Cloud Services plugin upgrades on Panorama, in a manner designed to be non-disruptive to the security processing nodes actually handling live customer traffic. The plugin upgrade primarily updates the management-plane component on Panorama that renders the Prisma Access configuration interface and pushes configuration to the cloud infrastructure; it does not require taking the data-plane gateways, service connections, or remote network tunnels offline, so existing sessions continue to be processed without interruption. This is why option C, that the upgrade is transparent to users, correctly reflects the documented behavior. Option A, suggesting users will experience latency during the upgrade, is not accurate as a general statement of impact - Palo Alto Networks explicitly designs and schedules these upgrades to avoid measurable service degradation for the customer ' s traffic flows. Option B is incorrect and would represent an unacceptable service-level outcome for a platform marketed on continuous availability; flows are not automatically terminated as a side effect of a management-plane plugin update. Option D introduces a false dependency: Panorama HA is a resiliency best practice for the management plane ' s own availability and for administrative continuity, but it is not a prerequisite for Prisma Access data-plane traffic to remain unaffected during a Cloud Services plugin upgrade, since the upgrade ' s transparency to traffic is a property of the Prisma Access service architecture itself.
Reference:Prisma Access - Cloud Services Plugin Upgrades and Service Continuity.

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.
Reference:Strata Cloud Manager Insights - Monitor Prisma Access Locations (User-ID and Group Mappings).

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.
Reference:GlobalProtect - Pre-Logon Authentication and Machine Certificate Store Requirements.