You manage your company's Azure virtual network. You have a virtual network named vnet1 with the address space 10.0.0.0/16 that contains three subnets:
public: subnet with the address space 10.0.1.0/24
private: subnet with the address space 10.0.2.0/24
dmz: subnet with the address space 10.0.3.0/24
You create a new network virtual appliance named nvm1 in the dmz subnet with the private IP address 10.0.3.11.
You need to configure a custom route in the private subnet to route the traffic to nvm1.
How should you configure the custom route? To answer, select the appropriate options from the drop-down menus.
You should configure the address prefix as 10.0.2.0/24. You can use the address prefix to configure where the traffic is coming from, which is from the private subnet.
Next, you should configure the next hop type as Virtual appliance. This option configures the type of destination where traffic is routed, which is the nvm1 network virtual appliance.
Finally, you should configure the next hop address as 10.0.3.11. You can use this option to configure the routing destination, which is the nvm1 private IP address.
You should not configure the address prefix as 10.0.1.0/24 or 10.0.3.0/24. These addresses prefixes refer to public and dmz subnets, respectively. You need to route traffic from the private subnet.
You should not configure the next hop type as Internet or Virtual network. You should configure these next hop types to route traffic to the internet or to a virtual network, respectively.
You should not configure the next hop address as 0.0.0.0/0 or 10.0.1.0/24. These addresses could be used to route traffic to the internet or the public subnet, respectively. You need to configure the next hop type as Internet or Virtual network with these addresses.