PSE-PRISMACLOUD · Question #109
What are the two options to dynamically register tags used by Dynamic Address Groups that are referenced in policy? (Choose two.)
The correct answer is A. VM Monitoring D. XML API. VM Monitoring (A) automatically registers tags to IP addresses by monitoring hypervisors (e.g., VMware vCenter), pulling VM attributes like name, OS, and guest group to populate Dynamic Address Groups without manual intervention. The XML API (D) allows external orchestration…
Question
What are the two options to dynamically register tags used by Dynamic Address Groups that are referenced in policy? (Choose two.)
Options
- AVM Monitoring
- BExternal Dynamic List
- CCFT Template
- DXML API
How the community answered
(30 responses)- A93% (28)
- B3% (1)
- C3% (1)
Explanation
VM Monitoring (A) automatically registers tags to IP addresses by monitoring hypervisors (e.g., VMware vCenter), pulling VM attributes like name, OS, and guest group to populate Dynamic Address Groups without manual intervention. The XML API (D) allows external orchestration tools, scripts, or security platforms to programmatically push tag registrations directly to the firewall, making it the go-to method for non-virtualized or custom environments.
External Dynamic List (B) is a distractor because EDLs import pre-defined lists of IPs/URLs/domains for use in policy, but they don't register tags - they function as a separate address object type entirely. CFT Template (C) refers to AWS CloudFormation Templates, an infrastructure-provisioning tool that has no native mechanism to push tag registrations into PAN-OS.
Memory tip: Think "V-X" - VM Monitoring for virtual environments, XML API for everything else. Both push tag data into the firewall dynamically, which is the defining requirement for DAG population.
Topics
Community Discussion
No community discussion yet for this question.