Question 490
The deployment team is preparing a sign-off for: An engineer changes the source NAT pool for one SD-WAN circuit and established sessions appear to retain older translated addresses. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that existing session state cannot always be assumed to recompute NAT after every policy change. The case concerns an engineer changes the source NAT pool for one SD-WAN circuit and established sessions appear to retain older translated addresses. The safer path is to review session-table NAT bindings, routing changes, and new-session path selection and then, after verification, to validate translation using fresh sessions and apply an approved change procedure for any sessions requiring renewal. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
Probe source path should not be inferred from a sample of user data sessions alone. The check concerns probe source path should not be inferred from a sample of user data sessions alone, not confirming that existing session state cannot always be assumed to recompute NAT after every policy change.
A successful test from one subnet is not proof another subnet matches the same NAT policy. This assesses a successful test from one subnet is not proof another subnet matches the same NAT policy; it does not determine the reported condition—an engineer changes the source NAT pool for one SD-WAN circuit and established sessions appear to retain older translated addresses.
A single interface byte counter cannot establish the routing decision for an individual session. The case-specific requirement is confirming that existing session state cannot always be assumed to recompute NAT after every policy change, which that option does not establish.