Exam AZ-104 topic 5 question 2 discussion

Correct Answer: C There can only be one hub per Azure region. It should be 2 Virtual Hubs and 1 WAN. Since we have just two region, it may be impossible to have 3 hubs. Reference: https://docs.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about

They're all wrong because the question says there are 2 Azure regions, and the below documentation says each region only has a single hub... Should be 2 hubs and one WAN. https://docs.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about "Hub: A virtual hub is a Microsoft-managed virtual network. The hub contains various service endpoints to enable connectivity. From your on-premises network (vpnsite), you can connect to a VPN Gateway inside the virtual hub, connect ExpressRoute circuits to a virtual hub, or even connect mobile users to a Point-to-site gateway in the virtual hub. The hub is the core of your network in a region. There can only be one hub per Azure region."

answer is definitely B

Three Virtual Hubs: One for each datacenter (Miami, Los Angeles, New York). One Virtual WAN: To unify and manage the connectivity across the virtual hubs and enable efficient routing between them and Azure.

To connect the datacenters to the Azure subscription with minimized network latency, the correct option is: B. three virtual hubs and one virtual WAN Virtual WAN: Azure Virtual WAN provides a unified hub-and-spoke architecture that connects on-premises datacenters, branch offices, and Azure regions efficiently. It minimizes latency by routing traffic through Azure's high-speed backbone network. Virtual Hubs: A virtual hub in Azure Virtual WAN is a regional point of connectivity. By creating three virtual hubs (one for each datacenter), you ensure that each datacenter has a dedicated connection to the Azure network via the closest Azure region. Peered virtual networks: The existing peered virtual networks in East US and West US regions can connect to the virtual WAN for seamless communication across datacenters and Azure regions. ** creating multiple WANS would not minimize latency, a single virtual WAN is designed to manage multiple hubs and connections efficiently.

The answer is C. I am not sure where the region limitation everyone is talking about is coming from. Perhaps it is outdated information. Source: https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about "Hub: A virtual hub is a Microsoft-managed virtual network. The hub contains various service endpoints to enable connectivity. From your on-premises network (vpnsite), you can connect to a VPN gateway inside the virtual hub, connect ExpressRoute circuits to a virtual hub, or even connect mobile users to a point-to-site gateway in the virtual hub. The hub is the core of your network in a region. Multiple virtual hubs can be created in the same region."

it´s B the answer should be: two virtual hubs and one virtual WAN but since we have only those options, B is the closest one as it says one WAN.

Correct is B By using three virtual hubs and one virtual WAN (Option B), you can connect each datacenter to its respective virtual hub, and then connect these hubs through the virtual WAN. This setup minimizes network latency and simplifies management by leveraging the capabilities of Azure Virtual WAN to handle multiple connections efficiently.

It cannot be 3 birtual WANs. The definition of virtual WAN says: It contains links to all your virtual hubs that you would like to have within the virtual WAN. Virtual WANs are isolated from each other and can't contain a common hub. Virtual hubs in different virtual WANs don't communicate with each other. Also, the definition of virtual hub says: Multiple virtual hubs can be created in the same region. https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about

The answer is B because Virtual hubs in different virtual WANs don't communicate with each other and Multiple virtual hubs can be created in the same region. To connect these datacenters, virtual hubs must be in the same WAN. Source: https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about

When multiple hubs are enabled in a single virtual WAN, the hubs are automatically interconnected via hub-to-hub links, thus enabling global connectivity between branches and Vnets that are distributed across multiple regions.

Azure Virtual WAN represents the virtual overlay of the Azure virtual network and other resources. For example: you have an on premise office and want to connect to multiple Virtual networks in Azure, then use Azure Virtual WAN. Virtual hub is a MS managed virtual network (created within Virtual WAN) to which you can connect various end points like P2S, S2S, virtual networks etc

What is the importance of "Each region contains a virtual network. The virtual networks are peered" in the question ?

B is correct

Answer from chatgpt and it makes sense: Option B: Three virtual hubs and one virtual WAN Explanation: Virtual hubs in Azure Virtual WAN provide a central point of connectivity and management for your network resources. By deploying three virtual hubs, one for each office, you establish a direct connection from each datacenter to the Azure Virtual WAN. Azure Virtual WAN is designed to optimize connectivity across regions, helping to minimize network latency between the datacenters and the Azure subscription. By using a single virtual WAN, you can centrally manage and configure the network connections for all three datacenters, streamlining administration and ensuring consistent network policies across the infrastructure. Therefore, option B is the most appropriate choice for minimizing network latency while connecting the datacenters to the Azure subscription.

https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about

I am not sure I understand the debate. According to ms docs "Virtual WANs are isolated from each other and can't contain a common hub. Virtual hubs in different virtual WANs don't communicate with each other". That would infer that multiple VWANs is not going to work to connect all of these together. https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about