How can an engineer verify that only the intended changes will be applied when modifying...

Palo Alto Networks documentation explicitly states that the"Preview Changes"functionality within the Strata Cloud Manager (SCM) push dialogue allows engineers to review a detailed summary of all modifications that will be applied to the Prisma Access configuration before committing the changes. This is the primary and most reliable method to ensure only the intended changes are deployed.

Let's analyze why the other options are incorrect based on official documentation:

A. Review the SCM portal for blue circular indicators next to each configuration menu item and ensure only the intended areas of configuration have this indicator.While blue circular indicators might signify unsaved changes within a specific configuration section, they do not provide a comprehensive, consolidated view ofallpending changes across different policy areas. This method is insufficient for verifying the entirety of the intended modifications.

B. Compare the candidate configuration and the most recent version under "Config Version Snapshots".While comparing configuration snapshots is a valuable method for understanding historical changes and potentially identifying unintended deviationsaftera push, it does not provide a real-time preview of thependingchanges before they are applied during the current modification session

C. Select the most recent job under Operations > Push Status to view the pending changes that would apply to Prisma Access.The "Push Status" section primarily displays the status anddetails ofcompletedorin-progresspush operations. It does not offer a preview of the changesbeforea push is initiated.

Therefore, the "Preview Changes" feature within the push dialogue is the documented and recommended method for an engineer to verify that only the intended changes will be applied when modifying Prisma Access policy configuration in Strata Cloud Manager (SCM).