Dynamic Address Groups provide dynamic membership based on tags:
A . Its update requires "Commit" to enforce membership mapping: Dynamic Address Groups update their membership automatically based on tag changes. A commit is not required for the group membership to reflect tag changes. The commit is required to apply the security policy using the dynamic address group.
B . It allows creation and enforcement of consistent Security policy across multiple cloud environments: This is a key benefit. Tags and Dynamic Address Groups can be used to create consistent security policies across different cloud environments, simplifying multi-cloud management.
C . Tags cannot be defined statically on the firewall: Tags can be defined statically on the firewall, as well as dynamically through integrations with cloud providers or other systems.
D . It uses tags as filtering criteria to determine IP address mapping to a group: This is the core functionality of Dynamic Address Groups. They use tags to dynamically determine which IP addresses should be included in the group.
E . Its maximum number of registered IP addresses is dependent on the firewall platform: The capacity of Dynamic Address Groups is limited by the hardware/virtual resource capacity of the firewall.
Reference:
The Palo Alto Networks firewall administrator's guide provides detailed information on Dynamic Address Groups, including how they use tags and their limitations.