An engineer is pushing configuration from Panorama to a managed firewall.
What happens when the pushed Panorama configuration has Address Object names that duplicate the Address Objects already configured on the firewall?
An engineer is pushing configuration from Panorama to a managed firewall.
What happens when the pushed Panorama configuration has Address Object names that duplicate the Address Objects already configured on the firewall?
When pushing configuration from Panorama to a managed firewall, if the pushed Panorama configuration contains Address Object names that duplicate those already configured on the firewall, the firewall will reject the pushed configuration, causing the commit to fail. This is to prevent any conflict or overwriting of existing configurations, ensuring the integrity of the firewall's settings.
It's B, just tested on lab Validation Error: . address -> Test duplicate 'Test duplicate' is already in use
https://docs.paloaltonetworks.com/panorama/9-1/panorama-admin/manage-firewalls/transition-a-firewall-to-panorama-management/plan-the-transition-to-panorama-management A - If a shared firewall object has the same name and value as an existing shared Panorama object, the import excludes that firewall object.
its B, it fails the commit should the local FW has the same object as the Panorama. on this docs it say "shared" https://docs.paloaltonetworks.com/panorama/9-1/panorama-admin/manage-firewalls/transition-a-firewall-to-panorama-management/plan-the-transition-to-panorama-management
It's B. A is wrong as that is discussing the IMPORT into PAN; not the export push down. The Commit will fail with an error displaying the duplicate object.
The answer is B. I dealt with this SO MUCH at my last job!
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClcICAS
none of the answers are relevant to the question.
B commit will fail