An engineer is pushing configuration from Panorama lo a managed firewall. What happens when the pushed Panorama configuration has Address Object names that duplicate the Address Objects already…

Question

Options

• AThe firewall rejects the pushed configuration, and the commit fails.
• BThe firewall renames the duplicate local objects with "-1" at the end signifying they are clones;
• CThe firewall fully commits all of the pushed configuration and overwrites its locally configured
• DThe firewall ignores only the pushed objects that have the same name as the locally

• A
  94% (32)
• B
  3% (1)
• C
  3% (1)

Explanation

When Panorama pushes configuration to a managed firewall, PAN-OS enforces that object names must be unique within their scope. If a pushed Address Object shares the same name as a locally configured Address Object on the firewall, the firewall treats this as a naming conflict and the commit is rejected - the entire push fails. The firewall does not silently overwrite local objects, rename them with suffixes like '-1', or selectively ignore duplicates. This behavior protects local configurations from being inadvertently overwritten and forces the administrator to resolve naming conflicts before the push can succeed.

No community discussion yet for this question.