AZ-700 Question 58
Single answerYou are designing a hub-and-spoke network in Azure where a custom third-party network virtual appliance (NVA) in the hub VNet needs to dynamically learn on-premises routes via BGP. You decide to deploy Azure Route Server in the hub VNet, but your initial deployment fails. Which action should you take first before attempting to deploy Azure Route Server again?
- A
Configure a dedicated subnet named 'RouteServerSubnet' in the hub VNet with a /27 or larger address space.
- B
Place the Azure Route Server in the same subnet as your custom NVA to ensure direct adjacency.
- C
Enable IP forwarding on your custom NVA� network interface in the Azure portal.
- D
Modify the hub VNet� DNS settings to point to the Azure Route Server IP addresses.
Show answer and explanation
Correct answer: A
Explanation
Azure Route Server must reside in a dedicated 'RouteServerSubnet' with at least a /27 address space. This requirement is detailed in Microsoft� documentation: https://learn.microsoft.com/azure/route-server/route-server-overview. Ensuring this subnet is properly configured before deployment is essential; if you try to deploy Azure Route Server with an incorrect subnet prefix size or an incorrect subnet name, the deployment will fail.
- A. Correct.
Correct. Azure Route Server requires a dedicated subnet named 'RouteServerSubnet' with a minimum subnet size of /27. Without this properly sized, correctly named subnet, the deployment fails. Creating this specific subnet first is a mandatory step.
- B. Incorrect.
Incorrect. Azure Route Server must exist in its own subnet named �RouteServerSubnet� and cannot be deployed in the same subnet as other resources�even if they are NVAs�according to Azure documentation.
- C. Incorrect.
Incorrect. While some NVAs require IP forwarding to be enabled for packet processing, this step alone doesn�t address Azure Route Server� subnet requirements and would not fix the deployment failure issue.
- D. Incorrect.
Incorrect. Editing DNS settings has no bearing on Azure Route Server� subnet prerequisites. DNS settings do not affect the BGP route exchange or the deployment of the route server itself.