Disable Server Response Inspection (DSRI) is a performance-oriented Security policy rule setting that instructs the firewall to skip Layer 7 content inspection — which includes both App-ID continuation and all threat signature matching — on the server-to-client leg of a session, regardless of the application or protocol in use. Once enabled on a rule, it applies uniformly to every session matching that rule, not selectively to HTTP; protocols such as SMB and FTP, which are chatty in the return direction and commonly the reason DSRI is enabled in the first place, are affected exactly the same way as any other server-to-client flow. This makes option C the accurate description: all server-to-client traffic on that rule bypasses threat inspection, full stop. This is precisely why DSRI carries an operational risk that engineers must weigh deliberately: attaching a Threat Prevention profile to the same rule does not re-enable inspection or " win out " over the DSRI setting in any direction, which eliminates options B and D — the two settings are not designed to arbitrate against each other, and DSRI simply takes precedence for the return traffic. Because of this, DSRI should only ever be applied to rules governing traffic to servers that are already fully trusted, since checking the box removes visibility into exploits, malware, and data returned from that server regardless of any other profile attached to the rule.

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.

Prisma Access egress and public IP addresses can change as a result of autoscaling or infrastructure upgrades, so any allow-list dependent on those addresses (SaaS tenant restrictions, partner firewalls, third-party services) needs a reliable way to stay current. Palo Alto Networks addresses this with two complementary mechanisms. First, an Egress IP Notification URL — the webhook referenced in option A — can be configured under Infrastructure Settings so that Prisma Access sends an HTTP POST a few seconds before a new IP address becomes active, giving downstream automation advance warning to update firewall or SaaS allow-lists before the change takes effect. Second, retrieving the actual address list requires authenticating to the Egress/Public IP retrieval API using an API key that is generated and copied from the service infrastructure settings, as described in option B; this key is passed in the request header when calling the retrieval endpoint. There is no separate " enable the Egress IP API endpoint " toggle, since the retrieval API is available by default once a key is generated — making option C incorrect. Authentication to this API is strictly key-based, not certificate-based, so downloading a client certificate (option D) is not a supported or required step. Together, the webhook and API key form the complete automation loop: notify, then retrieve and apply.

App Acceleration works by having Prisma Access decrypt, optimize, and re-encrypt SaaS application traffic across its backbone to reduce round-trip latency and improve throughput to well-known, high-volume SaaS destinations, and that optimization is fundamentally dependent on SSL Forward Proxy decryption already being functional and trusted end-to-end. Two certificate-related prerequisites make this possible: a Forward Trust Certificate configured for SSL decryption, which Prisma Access presents to the client in place of the SaaS provider ' s original certificate when it performs the man-in-the-middle decryption necessary to inspect and accelerate the session, and that certificate ' s issuing CA must be distributed to and trusted by client endpoints as a Trusted Root CA, so that browsers and applications do not throw certificate warnings or reject the substituted certificate. Both of these are explicit, documented prerequisites for App Acceleration to function correctly, which makes options C and D the correct pair. There is no dedicated " acceleration agent " software component that must be installed on client machines (option A); App Acceleration operates transparently at the Prisma Access infrastructure level for tunneled or proxied users, not through an endpoint agent add-on. QoS (option B) is a separate traffic-shaping capability used to prioritize bandwidth for specific application classes; it is not a prerequisite for App Acceleration to be enabled and is functionally unrelated to the decryption trust chain that acceleration depends on.

Panorama ' s multitenancy implementation for Prisma Access relies on Access Domains as the primary boundary mechanism: when a tenant is created, Panorama automatically generates the device groups, templates, and template stack associated with that tenant and binds them to a dedicated access domain. Restricting an administrator to that access domain confines their visibility and configuration rights strictly to the objects belonging to that tenant, which is exactly the outcome the question requires — full access within the tenant, no visibility into any other tenant ' s device groups or templates. This makes option A the structurally correct answer, because the access domain is the object that actually enforces the tenant boundary; a custom role alone, without an access domain restriction, defines what privileges an administrator has but not which tenant ' s objects those privileges apply to. Options B and C describe custom administrative roles, which are a necessary complement to access domains for fine-tuning specific privilege sets, but neither role definition by itself creates the tenant isolation the scenario demands — a role with " all privileges " or with device-group/template privileges could still be applied across every tenant ' s device groups unless paired with an access domain restriction. Assigning the Superuser role (option D) is explicitly the wrong direction: Superuser grants unrestricted access across the entire Panorama instance and all tenants, which directly violates the requirement to restrict access to other tenants.

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.

The branch requirement is internet filtering plus data center connectivity, which means every branch location needs Prisma Access to become its default gateway to the internet while still exchanging specific internal routes with the data center. Enabling eBGP on the Remote Networks connection is the scalable way to accomplish this: dynamic routing lets the CPE and Prisma Access exchange branch subnet reachability automatically, without the administrative burden of manually maintaining static routes across every site as the branch network changes — critical for a multi-branch B2B/enterprise deployment. Enabling the Advertise Default Route option on the Remote Networks connection is what actually delivers the internet-filtering requirement: it causes Prisma Access to advertise a 0.0.0.0/0 route to the branch CPE over the tunnel so that all branch-originated internet-bound traffic is pulled into Prisma Access for inspection, rather than breaking out locally. Static routes (options A and C) are technically workable at very small scale, but they do not scale for multi-site deployments, are error-prone to maintain, and do nothing on their own to steer default (internet) traffic into the tunnel the way the Advertise Default Route setting does. eBGP with Advertise Default Route is the documented best-practice combination for branch internet filtering and site connectivity through Remote Networks.

Because the two data centers are joined by a private link, without any additional filtering each service connection can learn the mobile user IP pool routes for both regions and re-advertise them across that private inter-data-center link, creating a path for return traffic destined to European mobile users to be pulled toward the North American service connection (and vice versa) rather than staying within its own region. In default Prisma Access routing mode, the cleanest and most deterministic fix is applied at the source of the advertisement: configuring each service connection ' s outbound route filtering to exclude the mobile user pool prefixes belonging to the other region. This ensures the data center only ever learns the " local " region ' s mobile user routes from its adjacent service connection, so return traffic naturally stays on the correct, geographically appropriate path without depending on BGP path-selection tie-breaking. Options A and C attempt to solve the problem through CPE-side BGP attribute manipulation (community string preference or MED preference); while conceptually plausible in isolation, this places the burden of correct routing on customer-managed equipment reacting to attributes rather than eliminating the unwanted route at the source, and is not the documented approach for default routing mode. AS-path prepending (option D) only influences path preference when multiple paths exist for the same prefix — it does not prevent an undesired prefix from being learned or selected at all, making it an unreliable mechanism for this scenario.

Command Center in Strata Cloud Manager is specifically built as a unified, interactive visual summary that draws on data from an organization ' s cloud-delivered security subscriptions and Autonomous DEM to surface applications, threats, user experience, and hosts across the network in a single consolidated view — and critically, it is designed to aggregate this insight consistently across both NGFW-managed sites and Prisma Access deployments rather than requiring the operations team to pivot between separate NGFW-only and Prisma-Access-only interfaces. This cross-product, single-pane consolidation of application, threat, and user data is exactly the capability the question describes, making option A the correct feature. Log Viewer (option B) provides raw, queryable access to individual log records across log types; it is a powerful investigative tool, but it is not the purpose-built visual summary interface for correlated application/threat/user insight the question is asking about, and using it for that purpose would require manual correlation the operations team would otherwise get natively from Command Center. " Branch Site Monitor " (option C) is not a named feature within Strata Cloud Manager. The SASE Health Dashboard (option D) is oriented toward infrastructure and connectivity health signals — tunnel status, latency, packet loss, and service availability — rather than application, threat, and user-centric insight, making it a distinct and separate capability from the one described in the question.

Strata Copilot ' s documented value proposition is centered on being an AI-assisted guidance layer embedded within Strata Cloud Manager, surfacing context-aware, actionable recommendations that help security teams diagnose and resolve issues faster — effectively an intelligent advisor that interprets the operational and configuration state of the environment and proposes specific, relevant next steps for the administrator to take. This positions Strata Copilot as an assistive, human-in-the-loop tool rather than an autonomous engine that independently performs actions, which is precisely what makes option C the accurate description of its current capability: customized guidance and recommended next steps, delivered to inform an administrator ' s own decision-making and remediation actions. Option A overstates Copilot ' s function by describing it as performing automated threat prevention through real-time traffic analysis, which is the domain of the platform ' s actual security enforcement engines (Threat Prevention, Advanced URL Filtering, and similar cloud-delivered security services), not Copilot itself. Option B similarly overstates capability by suggesting Copilot can perform entire initial Prisma Access deployments through natural language alone; while conversational and assistive elements exist, this framing goes beyond documented, current guided-assistance functionality. Option D describes fully autonomous remediation of misconfigurations without human review, which does not match Copilot ' s positioning as a recommendation and guidance tool — actual policy changes remain administrator-driven, with Copilot providing the analysis and suggested path forward rather than executing changes independently.