AZ-800 · Question #49
You have an on-premises network that is connected to an Azure virtual network by using a Site- to-Site VPN. Each network contains a subnet that has the same IP address space. The on- premises subnet…
The correct answer is A. Azure Extended Network. Azure Extended Network (implemented via a stretched subnet) allows you to extend an on-premises subnet into Azure so that the migrated VM retains its original IP address without any changes. This is essential here because both the on-premises and Azure subnets share the same IP…
Question
You have an on-premises network that is connected to an Azure virtual network by using a Site- to-Site VPN. Each network contains a subnet that has the same IP address space. The on- premises subnet contains a virtual machine. You plan to migrate the virtual machine to the Azure subnet. You need to migrate the on premises virtual machine to Azure without modifying the IP address. The solution must minim administrative effort. What should you implement before you perform the migration?
Options
- AAzure Extended Network
- BAzure Virtual Network NAT
- CAzure Application Gateway
- DAzure virtual network peering
How the community answered
(43 responses)- A77% (33)
- B7% (3)
- C2% (1)
- D14% (6)
Explanation
Azure Extended Network (implemented via a stretched subnet) allows you to extend an on-premises subnet into Azure so that the migrated VM retains its original IP address without any changes. This is essential here because both the on-premises and Azure subnets share the same IP address space, meaning standard migration would cause an IP conflict. Azure Virtual Network NAT would translate addresses (changing the IP). Application Gateway is a Layer 7 load balancer. VNet peering cannot bridge overlapping address spaces. Azure Extended Network is specifically designed for this IP-preserving migration scenario with minimal administrative effort.
Topics
Community Discussion
No community discussion yet for this question.