Paloalto Networks SSE-Engineer - Palo Alto Networks Security Service Edge Engineer

AI Access Security extends Prisma Access ' s existing App-ID-based application classification model to the generative AI space, and the mechanism it uses to let organizations differentiate their risk tolerance across the rapidly growing number of AI applications in use is to apply status tags — sanctioned, tolerated, or unsanctioned — directly to the identified Generative AI applications themselves, mirroring the same governance pattern long used for SaaS Security application risk classification. Once an AI application carries one of these tags, Security policy rules and dashboards can reference that classification consistently across the environment, giving administrators a scalable way to express organizational policy (which AI tools are approved, which are tolerated with monitoring, and which are explicitly prohibited) without having to hand-build a separate access rule for every individual AI application discovered. This makes option A the correct answer, since the tag is applied at the application object level, not any of the other locations listed. Applying tags to Security rules (option B) inverts the actual relationship: rules reference the application ' s tag/classification, they are not themselves the object being tagged. Tagging user devices (option C) would conflate device posture management with application classification, which are separate control domains in Prisma Access. Tagging Generative AI URL categories (option D) misattributes the classification mechanism to URL Filtering category objects, when AI Access Security ' s sanctioned/tolerated/unsanctioned tagging is applied to the discovered applications themselves via App-ID, not to a URL category construct.

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.