PCNSA Managing Objects Practice Question
A company uses dynamic address groups based on tags. A virtual machine receives the tag "WebServer". After the VM is decommissioned, the tag is removed. What happens to the dynamic address group?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The group automatically updates and removes the IP address.
Dynamic address groups update automatically based on tag membership. When the tag is removed from the VM, the VM's IP address is automatically removed from the group. No manual intervention or commit is required for the group to reflect the change, though a commit may be needed for policy enforcement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The group automatically updates and removes the IP address.
Why this is correct
Dynamic address groups resolve membership from tag criteria rather than static lists. When the WebServer tag is removed from the decommissioned VM, the firewall re-evaluates the filter and drops that IP automatically, requiring no manual edit.
- ✗
The group retains the IP address until manually removed.
Why it's wrong here
Membership is derived from current tag registrations, so the IP is dropped once its tag is removed; nothing is retained for manual cleanup. Retention tempts because static address objects persist until edited, but dynamic groups hold no stored member list to retain.
- ✗
The group is deleted.
Why it's wrong here
Dynamic address groups are membership filters, not containers; removing the last matching tag empties the group while the group object itself persists in the policy configuration. Deletion tempts because an empty group seems redundant, but deletion would break every security policy referencing that group name.
- ✗
The group requires a commit to update.
Why it's wrong here
Dynamic address group membership updates automatically as tags change, without a commit; the firewall re-evaluates registered IP-to-tag mappings continuously. A commit tempts because static configuration changes do require one, but tag-driven membership is runtime state, not candidate configuration.
Go deeper
Related to this question
About these practice questions
This PCNSA question is part of Courseiva's 385-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PCNSA practice question is part of Courseiva's free Palo Alto Networks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCNSA exam.