Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Palo Alto Networks Certified Security Service Edge Engineer (Prisma Access SASE) · Palo Alto Networks
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
- 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.