If you want, I can:

: The client automatically selects the optimal network protocol path based on network conditions, switching transparently between SSL and IKEv2.

Prevents internal corporate DNS queries from leaking onto public local ISP networks.

In some Windows scenarios, DNS requests might not be routed through the VPN tunnel correctly. This was a known issue in the 4.7 branch, sometimes requiring a reconfiguration of the network interface 1.2.1.

If you are looking for the specific reason this "4703052" build exists (the "exclusive" part), it is typically to patch specific critical bugs. This build addressed several high-severity issues, including:

Historically, connecting to public Wi-Fi networks (like those in hotels or airports) while using aggressive "Always-On" VPN profiles resulted in a operational deadlock: the VPN blocked all traffic until a secure tunnel was built, but the public network blocked the tunnel until the user logged into a web portal.