Strata Logging Service retains logs independently of whether or not an external forwarding destination was reachable at the time they were generated, so no log data is actually lost during a syslog server outage - it simply was never forwarded during the disruption window. The mechanism designed to reconcile this gap is a replay profile: an administrator specifies the affected time range and associates that replay configuration with the relevant syslog server profile, and Strata Logging Service then resends every log that falls within that window to the external destination, effectively backfilling the outage period without requiring any manual export or reconstruction of the log set. This makes option A the correct, purpose-built remediation. Deleting and recreating the syslog server profile (option B) does nothing to recover the logs generated during the outage; it only affects the configuration used for logs going forward, and any pending backlog would still need to be replayed by other means. Manually exporting and importing logs (option C) is operationally burdensome, error-prone at scale, and unnecessary given that a native replay capability exists specifically to automate this exact recovery scenario. A log filter (option D) narrows which log types or attributes are forwarded going forward - it is a scoping mechanism, not a retransmission mechanism, and configuring one does not cause any historical, unforwarded logs to be resent.
Reference:Strata Logging Service - Log Forwarding Replay Profiles.

When multiple Remote Networks share an identical, overlapping IP address subnet, Prisma Access has no way to uniquely and deterministically route traffic destined to a specific store, to a specific mobile user, or to a private application located behind one particular site, because the destination or source subnet alone can no longer disambiguate which physical location a packet needs to reach - every store looks identical on the wire. The Overlapping Subnets checkbox exists to acknowledge and accommodate this reality, but the trade- off is that Prisma Access can only reliably support the traffic flow where uniqueness of the store ' s internal subnet is not required for correct forwarding: outbound internet-bound traffic, which is source-NATed at egress and does not depend on the branch ' s internal addressing being globally unique within the Prisma Access backbone. This is why option B, internet-bound traffic, is the flow that remains fully supported. Flows to private applications (option A) and to other remote networks (option C) require the backbone to route based on the branch ' s actual internal subnet to reach specific internal destinations or to allow other sites to reach that store directly, which becomes ambiguous and unsupported once the subnet is duplicated across multiple onboarded locations. Mobile user access to an overlapping-subnet branch (option D) suffers from the same ambiguity, since a mobile user ' s traffic destined to that internal subnet cannot be deterministically routed to the correct physical store.
Reference:Prisma Access Remote Networks - Onboarding Locations with Overlapping Subnets.

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.
Reference:Prisma Access - App Acceleration Requirements (Forward Trust Certificate and Trusted Root CA).

Video conferencing tools embedded in a browser depend on two independent technical layers functioning correctly together: the WebRTC protocol, which carries the actual real-time audio/video media stream, and the browser ' s grant of camera and microphone device permissions to the site requesting them. If either layer is restricted, " any video conferencing features across various tools " will fail exactly as described, which is the key to identifying the correct two categories. WebRTC handling is governed under Browser Security Controls - a Prisma Access Browser administrator can explicitly set WebRTC to Block, which is documented as breaking video conferencing tools such as Teams, Zoom, Meet, and WebEx unless their domains are specifically exempted through an exclusion list - making this the first correct category. The second required category is Access & Data Controls, where the Camera and Microphone controls live; these are configured to Allow or Block access to the respective device per matching URL, application, or category, and a Block setting here will prevent any web-based conferencing tool from acquiring the audio/video stream even if WebRTC itself is otherwise permitted. Browser Customization Controls, the second option in the original answer set, govern cosmetic and productivity settings - branding, homepage configuration, and interface appearance - and have no functional relationship to device permissions or media protocol handling, so they cannot explain a video-conferencing failure. Network Security Controls govern network-layer access rather than in-browser device or protocol permissions, and are similarly unrelated to this specific symptom.
Reference:Prisma Access Browser - Browser Security Controls (WebRTC) and Access & Data Controls (Camera, Microphone).

Strata Cloud Manager ' s Config Version Snapshots screen is purpose-built for this exact validation task: it allows an administrator to select the " Candidate " entry and compare the currently pending, uncommitted configuration directly against a previously pushed version, surfacing exactly which objects, rules, and settings have changed before anything is deployed. This gives a precise, itemized diff rather than a general status indicator, which is why it is the correct answer over the distractors. The blue circular indicators described in option A are scope indicators that show where a configuration element is inherited from or whether it is locally defined - useful for understanding configuration hierarchy, but not a change-verification mechanism, and they do not surface a diff of pending edits. Push Status (option C) is a historical and in-progress operations log; it reports on push jobs that have already been submitted, including their result and target devices, but it does not offer a pre-push preview of what is about to change. The push dialogue itself (option D) primarily lets an administrator select admin scope, folders, and services to include in a push; while some validation occurs at push time, it is not designed as a deliberate side-by-side comparison tool the way Config Version Snapshots is. For rigorous change control, comparing the candidate configuration against the last known-good snapshot before pushing is the documented method.
Reference:Strata Cloud Manager - Configuration: Config Version Snapshots.