Q: 5
What is a result of enabling split tunneling in the GlobalProtect portal configuration with the “Both
Network Traffic and DNS” option?
Options
Discussion
D . This basically lets you control which domains resolve via the VPN DNS and which stick with local DNS, so fits what split tunneling does in GlobalProtect. Not 100% if there's a weird edge case, but pretty sure.
Option D Had something like this in a mock, and it matches how split tunneling with DNS works in GlobalProtect as far as I know.
Option D not B. B feels like a trick since seamless FQDN is a different feature I think.
Its B here. With split tunneling set this way, I'm thinking users can hit internal and external resources based on location but using the same FQDN. Not 100% sure, open to other views.
D vs B, but pretty sure D is it since B mixes up features. Trap for those thinking seamless FQDN.
B
D every time here. That's the whole point of DNS split tunneling in GlobalProtect, you pick which domains go to each DNS.
Pretty sure it's B. The way split tunneling works, when you enable both network and DNS, users get access to internal stuff locally and external stuff remotely, all using the same FQDN. I think that's what the option is saying.
I think B makes more sense for "Both Network Traffic and DNS" split tunneling, not D. B.
D . C looks tempting if you're just thinking about DNS in general, but with GlobalProtect split tunneling and the "Both" option, it's all about specifying which domains use which DNS server. Seen this on other practice sets too.
Be respectful. No spam.
