4A0-107 · Question #24
Which of the following statements is considered best practice when changing a network policy that has been associated with an interface?
The correct answer is B. A new network policy should be created and applied to the interface, overwriting the previous. Creating and applying a new policy (B) is best practice because it provides an atomic replacement - the interface is never left in an unprotected or unconfigured state, and the transition happens in a single operation without service disruption. Why the distractors are wrong: A…
Question
Which of the following statements is considered best practice when changing a network policy that has been associated with an interface?
Options
- AThe policy should be placed in a "shutdown" state before changes are made.
- BA new network policy should be created and applied to the interface, overwriting the previous
- CThe policy must first be removed from the interface, then modified and re-applied to the interface.
- DBefore the policy can be changed, it must be deleted with the no network qos <policy- id>
- EBefore any changes are made to the policy, all network interfaces where the policy is applied
How the community answered
(33 responses)- A6% (2)
- B82% (27)
- C9% (3)
- D3% (1)
Explanation
Creating and applying a new policy (B) is best practice because it provides an atomic replacement - the interface is never left in an unprotected or unconfigured state, and the transition happens in a single operation without service disruption.
Why the distractors are wrong:
- A is wrong because network QoS policies don't have a "shutdown" state - that concept applies to interfaces, not policies.
- C is wrong because removing the policy first leaves the interface unprotected during the gap between removal and re-application.
- D is wrong because deleting the policy entirely with
no network qosdestroys the configuration; you'd then have to rebuild from scratch and the interface would be uncovered in the meantime. - E (incomplete, but implies removing from all interfaces first) is wrong for the same reason as C - it causes unnecessary disruption across multiple interfaces.
Memory tip: Think "Overwrite, don't orphan" - always push the new policy on top of the old one so the interface is never left without coverage. If you remove first, you create a window of risk; if you overwrite, there's no gap.
Topics
Community Discussion
No community discussion yet for this question.