Helping Hand Questions for SSE-Engineer

Forcing all application access through PAB for unmanaged or non-compliant devices requires addressing two distinct application authentication patterns separately, since a single enforcement mechanism cannot cover both. For applications that are integrated with the organization ' s identity provider and support SSO, the Enforce SSO setting ensures that any attempt to authenticate to that application is redirected specifically through the PAB-brokered session rather than allowing a direct, out-of-band login that would bypass PAB ' s controls entirely — this closes the most common bypass path for SSO-capable SaaS and web applications. For applications that are not SSO-enabled and therefore cannot be gated the same way, Account Protection provides the complementary enforcement mechanism, restricting direct credential-based access to those applications outside of the PAB session so that even non-SSO applications cannot be reached through an unmanaged, unenforced path. Together, these two settings comprehensively cover both application authentication models, which is why options A and B form the correct pair. The PAB Extension (option C) is a deployment and traffic-redirection mechanism, but on its own it does not enforce that access only happens through PAB — a user could still, without SSO enforcement or Account Protection in place, log in to an application directly outside the extension ' s redirected session. Device Posture (option D) is used to assess and act on a device ' s compliance state to allow or block traffic generally; it is a conditional access input, not the specific enforcement mechanism that closes the SSO and non-SSO application bypass paths described in the question.

Preventing paper copies of on-screen information is a data control problem, and PAB ' s actual, named control for this function is the Print control, which can be set to block printing for matching sessions — this is the correct, real mechanism, making option A correct; there is no separate, distinct " kiosk control " object in PAB ' s control set, which makes option B a fabricated distractor rather than a genuine configuration element. The second requirement — ensuring the policy applies specifically and reliably to this one fixed-location kiosk device — is a matching-criteria problem, and the two candidate approaches offered are location-based scoping and network-based scoping. Location-based policy scope in PAB primarily relies on OS-level location services or GeoIP resolution, both of which are typically imprecise at the level of a single building or office floor and can be unavailable entirely on a locked-down, purpose-built kiosk device that may not have location services enabled or a rich OS profile reporting into it. Network-based scoping, by contrast, lets the administrator match specifically on the corporate office ' s known public IP range or CIDR block, which is a precise, reliable, and location-independent way to guarantee the rule applies consistently to traffic originating from that fixed premises regardless of GeoIP accuracy or device location-service availability — making option D the more dependable and correct match criterion for this exact scenario, and Location-based scope (option C) the weaker, less appropriate choice for a fixed, single-building kiosk enforcement requirement.

The PAB Extension ' s core architectural advantage is that it enforces web access and data control policy at the browser layer itself, rather than depending on a full-tunnel VPN connection to redirect traffic through Prisma Access; this means policy enforcement continues to apply to a managed device ' s browser-based access to sanctioned web applications even when that device is not currently connected to VPN, which is exactly the gap the question describes and the capability option A correctly identifies. Because the enforcement point is the browser session rather than the network path, security and data controls (such as access restrictions, DLP, watermarking, and clipboard controls) remain consistently applied for supported browsers regardless of whether the underlying device happens to be VPN-connected at that moment — extending policy reach beyond what a purely network-based tunnel approach could achieve. Option B is incorrect because the Extension specifically operates at the browser level and does not tunnel all endpoint traffic; that full-device tunneling behavior describes a VPN client model, which is the opposite of what makes the Extension valuable for this exact scenario. Option C describes remote browser isolation, which is a separate, more resource-intensive capability generally reserved for isolating risky or unmanaged browsing sessions, not the defining mechanism of the lightweight browser Extension for managed devices. Option D mischaracterizes the Extension ' s purpose as network performance optimization, when its actual function is policy enforcement and data protection, not throughput or latency improvement.

Because PAB is frequently deployed to secure access from BYOD and other endpoints where IT lacks the administrative rights to directly manage, configure, or remediate the device, the value of device posture attributes lies specifically in visibility and conditional access — not remediation. By collecting signals such as OS version, file system encryption state, and device type, PAB gives administrators the information needed to make risk-based access decisions, such as denying or restricting access to sensitive applications from devices running outdated, vulnerable operating system versions, or from device types the organization considers higher risk, even though IT cannot directly touch or manage the underlying device. This read-and-restrict model is precisely what option C describes, and it reflects the actual, realistic capability of a posture-attribute-based access control system operating on unmanaged endpoints. Option A overstates PAB ' s function; it is not a standalone EDR solution, since EDR involves active threat detection, investigation, and endpoint-level response capabilities that PAB, as a browser-centric security control, does not provide. Option B is incorrect because PAB has no ability to remotely enable disk encryption on a device it does not manage — posture attributes are read for assessment purposes, not pushed as configuration changes to unmanaged endpoints. Option D is similarly incorrect; PAB cannot perform OS or browser patching on devices outside of IT ' s administrative control, since doing so would require management-level access the organization explicitly does not have on personal or unmanaged devices.