- 1 view
Exam
Answer needs confirmation
Question
You have a Site-to-Site VPN between an on-premises network and an Azure VPN gateway. BGP is disabled for the Site-to-Site VPN.
You have an Azure virtual network named Vnet1 that contains a subnet named Subnet1. Subnet1 contains a virtual machine named Server1.
You can connect to Server1 from the on-premises network.
You extend the address space of Vnet1. You add a subnet named Subnet2 to Vnet1. Subnet2 uses the extended address space. You deploy an Azure virtual machine named Server2 to Subnet2.
You cannot connect to Server2 from the on-premises network. Server1 can connect to Server2.
You need to ensure that you can connect to Subnet2 from the on-premises network.
What should you do?
Proposed answer
- A. Add an additional Site-to-Site VPN between the on-premises network and Vnet1.
- B. Add a private endpoint to Subnet2.
- C. To Subnet2, add a route table that contains a user-defined route.
- D. Update the routing information on the on-premises routers.
Suggested answer
D. Update the routing information on the on-premises routers.
syu31svc
3 months, 1 week ago
Selected Answer: D
By default, Azure VPN gateway advertises the virtual network address space to the on-premises VPN device using the Border Gateway Protocol (BGP). However, in this scenario, BGP is disabled for the Site-to-Site VPN. Therefore, you need to manually update the on-premises VPN device with the new extended address space of Vnet1 and create a new route for it. Answer is D
upvoted 3 times
jecawi9630
6 months, 2 weeks ago
Selected Answer: D
Correct. Your on-prem needs to know that the new subnet is part of the VPN tunnel, and to send traffic to the tunnel.
upvoted 4 times