When a large branch office experiences a high volume of employees logging in within a short time frame, the following apply:
* Maximum pending TCP DNS requests is 64- This means that Prisma Access can queue up to 64 pending DNS requests over TCP before dropping additional requests. If more requests are received simultaneously, some may fail or experience delays.
* Maximum number of TCP DNS retries is 3- If a DNS request fails over TCP, Prisma Access will attempt to retry the request up to three times before failing over to another method or returning an error.

Configuring a webhook allows the company to receive real-time notifications when Prisma Access changes its egress IP addresses, ensuring that policy rules are updated automatically. Downloading a client certificate is necessary for authentication to the Egress IP API, allowing secure API access for retrieving updated IP addresses. These actions ensure that security policies remain effective without manual intervention.

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.
Reference:Prisma Access Remote Networks - BGP Configuration and Advertise Default Route.

When configuringRemote Browser Isolation (RBI)inPrisma Access (Managed by Strata Cloud Manager) for mobile users, aURL access management profilemust be created with thesite access action set to
"Isolate". This profile is thenapplied to a Security policyto enforce isolation for specific URLs. This ensures thatweb traffic to designated high-risk or untrusted sitesisredirected to a remote, secure browser instance, protecting endpoints from potential web-based threats.

The"400 Bad Request"error when attemptingSAML authenticationthrough theCloud Identity Engine (CIE)suggests amisconfiguration in the SAML metadata. This typically occurs when theendpoint URLs, certificates, or entity IDsdo not match betweenCloud Identity Engine and the IdP portal. To resolve this, verify that:
TheSAML metadatauploaded toCloud Identity Enginematches theconfiguration from the IdP.

TheACS (Assertion Consumer Service) URL, Entity ID, and certificateare correctly set.

There are no incorrect or expired certificates in theCloud Identity Engine and IdP configuration.

By ensuring theSAML metadatais properly configured inboth systems, authentication should proceed without errors.