Your company network includes two branch offices. Users at the company access internal
virtual machines (VMs).
You want to ensure secure communications between the branch offices and the internal
VMs and network.
You need to create a site-to-site VPN connection.
What are two possible ways to achieve this goal? Each correct answer presents a complete
solution.
A.
a private IPv4 IP address and a compatible VPN device
B.
a private IPv4 IP address and a RRAS running on Windows Server 2012
C.
a public-facing IPv4 IP address and a compatible VPN device
D.
a public-facing IPv4 IP address and a RRAS running on Windows Server 2012
First, we’re enhancing the existing ‘Site-to-Site VPN’ connectivity so you can use Windows Server 2012 RRAS (Routing and Remote Access) as an on-premises VPN server. This gives you the flexibility of using a software based VPN solution to connect your on-premises network to Windows Azure.
0
0
is it correct?
0
0
Yes!
0
0
According to https://msdn.microsoft.com/en-us/library/azure/dn133798.aspx?f=255&MSPPError=-2147217396#bkmk_site_to_site
says “You must have an externally facing IPv4 IP address and a VPN device or RRAS to configure a site-to-site VPN connection.”
So CD are correct!
0
0
C+D
0
0
Dont be tricked like I was. Its obvious answer: C & D. Stupid me got the idea in my head “oh does Microsoft mean the RRAS will be handling the NAT as well, so it really needs the internal IP address in which to NAT pre-VPN tunneling?
No…C & D are the correct answers
0
0