Question 460
Following remediation of this issue—A branch ping to the hub succeeds but the business application fails after policy changes—what observable result would confirm success?
Explanation
Correct Answer
The observed result gives evidence of the repaired dependency rather than unrelated service health. The targeted fix is: Capture or trace representative application packets and inspect policy/session decisions. The principle is: Reachability probes and actual service traffic may hit different firewall and SD-WAN rules.
Incorrect Answers
That approach would solve a different incident: A client fails to establish SPA after certificate rotation and the first engineer blames DNS resolution despite correct name responses. The remediation for this case remains: Capture or trace representative application packets and inspect policy/session decisions.
This option serves the scenario “An SD-WAN member is marked green yet packets are dropped at an upstream ISP gateway during congestion”. This observation is aligned with the affected component. The present scenario is distinguished by “The authorized app's complete TCP transaction passes the intended security path”.
This alternative addresses the separate case “A branch suffers intermittent voice dropouts and a packet capture shows traffic switching paths every few seconds”. An effective postchange test must exercise the intended path. The deciding requirement here is “The authorized app's complete TCP transaction passes the intended security path”.