After importing a pre-configured firewall configuration to Panorama, what step is required to ensure a commit/push is successful without duplicating local configurations?

After importing a pre-configured firewall configuration to Panorama, what step is required to ensure a commit/push is successful without duplicating local configurations?
A . Ensure Force Template Values is checked when pushing configuration.
B . Push the Template first, then push Device Group to the newly managed firewall.
C . Perform the Export or push Device Config Bundle to the newly managed firewall.
D . Push the Device Group first, then push Template to the newly managed firewall

View Answer

Answer: C

Explanation:

https://docs.paloaltonetworks.com/panorama/11-0/panorama-admin/manage-firewalls/transition-a-firewall-to-panorama-management/migrate-a-firewall-to-panorama-management Push the configuration bundle from Panorama to the newly added firewall to remove all policy rules and objects from its local configuration. This step is necessary to prevent duplicate rule or object names, which would cause commit errors when you push the device group configuration from Panorama to the firewall in the next step.