SSE-Engineer Practice Questions

The foundational step in any Entra ID group-driven access model is establishing the directory relationship itself: adding Microsoft Entra ID as an identity provider within the Cloud Identity Engine and explicitly configuring the group mappings that correspond to each project ensures Prisma Access has a live, synchronized view of which users belong to which project-specific groups as those memberships change over time — without this step, no downstream policy can reference accurate, current group membership at all, which makes option D a clearly necessary configuration. Once group membership is flowing correctly from Entra ID through the Cloud Identity Engine, the second half of the requirement is translating that group membership into actual differentiated network access to project-specific resources; this is accomplished by associating each synchronized group with the corresponding project ' s IP address pool or resource scope within Prisma Access ' s access configuration, so that a user ' s dynamically evaluated group membership determines which project resources their Security policy grants them reachability to, which is the mechanism described in option

A.  

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.

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.