You are increasing your usage of Cloud VPN between on-premises and GCP, and you want to support more traffic than a single tunnel can handle. You want to increase the available bandwidth using Cloud VPN.
What should you do?
You are increasing your usage of Cloud VPN between on-premises and GCP, and you want to support more traffic than a single tunnel can handle. You want to increase the available bandwidth using Cloud VPN.
What should you do?
To increase the available bandwidth using Cloud VPN between on-premises and GCP, you should add a second on-premises VPN gateway with a different public IP address. Then, create a second tunnel on the existing Cloud VPN gateway that forwards the same IP range but points to the new on-premises gateway IP. This configuration allows for load balancing the traffic across both VPN gateways and effectively increases the bandwidth.
The correct anwser is C Option 1: Scale the on-premises VPN gateway https://cloud.google.com/network-connectivity/docs/vpn/concepts/classic-topologies#option-1
Answer is 100% C! There is practically no difference between C and D in terms of increasing the throughput. However, D does not work due to one info given in the statement. 'create a secondary VPN gateway in a DIFFERENT region'. The secondary VPN gateway should be in the same region as the first VPN gateway in order for this method to work.
C is the correct option. Option D says to create another Cloud VPN GW to a DIFFERENT region, so it's not an option here. Doc: https://cloud.google.com/network-connectivity/docs/vpn/concepts/classic-topologies#vpn-throughput
Answer C: Just read the first sentence https://cloud.google.com/network-connectivity/docs/vpn/concepts/classic-topologies#option-1
Option C is the only option that matches one of the Google Increased throughput and load balancing options (option 2), and it has to be in the same region https://cloud.google.com/network-connectivity/docs/vpn/concepts/classic-topologies#option-1
The correct answer is C
why not B? you can have 1 cloudVPN gw in HA setup and you can configure each tunnel individually to the same remote public peer. Tested in the LAB and working fine
Option B is the correct choice. By creating two VPN tunnels, you can distribute traffic between the tunnels, effectively increasing the available bandwidth. This configuration is known as a "redundant VPN gateway" configuration, where both tunnels are active at the same time and traffic can flow through either of them.
I dont think so increase BW by creating multiple tunnels on top of internetlinks.
yes now i roll back my comments
Yes, I was wrong. C is correct: https://cloud.google.com/network-connectivity/docs/vpn/concepts/classic-topologies#option-1
B is correct as per https://cloud.google.com/network-connectivity/docs/vpn/concepts/classic-topologies#option-1
I mean C
You want this in the same region, so the answer is C
Definitely C
Choose C. Explanation: Adding a second on-premises VPN gateway with a different public IP address can provide redundancy and potentially load balancing across the two on-premises gateways. Creating a second tunnel on the existing Cloud VPN gateway that forwards the same IP range to the new on-premises gateway allows you to distribute traffic across both on-premises gateways. If the goal is to increase bandwidth by load balancing traffic across two on-premises VPN gateways, this approach can be valid.
C. Add a second on-premises VPN gateway with a different public IP address. Create a second tunnel on the existing Cloud VPN gateway that forwards the same IP range, but points at the new on-premises gateway IP.
C: Set up a second on-premises VPN gateway device with a different external IP address. Create a second tunnel on your existing Cloud VPN gateway that forwards the same IP range, but pointing at the second on-premises gateway IP. Your Cloud VPN gateway automatically load balances between the configured tunnels. You can set up the VPN gateways to have multiple tunnels load balanced this way to increase the aggregate VPN connectivity throughput.
https://cloud.google.com/network-connectivity/docs/vpn/concepts/classic-topologies#option-1 .....based on this, answer is C
B seems correct : One peer VPN device with one IP address This topology describes one HA VPN gateway that connects to one peer device that has one external IP address. The HA VPN gateway uses two tunnels, both tunnels to the single external IP address on the peer device. https://cloud.google.com/network-connectivity/docs/vpn/concepts/topologies#1-peer-1-address
If you look at the diagram - the VPN gateway has two external IP address, not one. C is correct
Apologizes - Answer B says two VPN tunnels on the VPN gateway... no reference to IP addresses. Answer B is 'more' correct thanC.
NOT B because would not necessarily increase the available bandwidth as the tunnels would still be limited by the capacity of the single on-premises VPN gateway