The requirement describes split tunneling. Internet-bound traffic should remain local at the remote client, while traffic destined for corporate data center networks should traverse the VPN tunnel. In Aruba VIA, this behavior is configured in the VIA Connection Profile by enabling split tunneling and defining which destination networks should be tunneled. Adding the data center networks to the tunneled networks list ensures only those corporate routes are sent through the VPN. Firewall roles control access permissions after authentication, but they are not the primary place to define the VIA client's split-tunnel routing behavior. VPN pools assign client IP addresses, not destination routing rules. Therefore, split tunneling in the VIA Connection Profile is the correct configuration.

===============