Which two options describe use cases of internal and external tags in Panorama? (Choose two.)

Question

Options

• Adevice group membership
• Btemplate membership
• CDynamic Address Group membership
• Drule grouping

• A
  89% (54)
• B
  3% (2)
• D
  8% (5)

Explanation

Internal and external tags in Panorama serve as dynamic membership criteria, making A (device group membership) and C (Dynamic Address Group membership) correct. Tags can automatically assign firewalls to device groups in Panorama based on registered attributes, and they are the core mechanism by which IP addresses are dynamically included in or excluded from Dynamic Address Groups (DAGs) - enabling policy enforcement without static address definitions.

B is wrong because template membership in Panorama is determined by explicit device serial number assignment, not by tags. D is wrong because while tags can label individual security rules for filtering/visibility within the rule editor, "rule grouping" is not a functional use case driven by internal/external tag logic - it's more of a UI organization feature.

Memory tip: Think of tags as the "dynamic engine" in Panorama - anywhere membership needs to be automatic and responsive (Device Groups, Dynamic Address Groups), tags are in play. Static constructs like Templates use fixed serial-number assignment instead.

No community discussion yet for this question.