Find answers, ask questions, and connect with our
community around the world.

Home Forums Azure Connect VM to VNet

  • Connect VM to VNet

     JR-TutorialsDojo updated 6 months ago 2 Members · 4 Posts
  • samabc

    Member
    August 3, 2025 at 1:45 am

    > TDVM1 needs to connect to a newly created virtual network named TDNET1 that is located in Japan West.

    > What should you do to connect TDVM1 to TDNET1?

    > Solution: You create a network interface in TD1 in the South East Asia region.

    > Does this meet the goal?

    > The solution proposed in the question is incorrect because the virtual network is not located in the same region as TDVM1.

    I believe the proposed solution is incorrect – but not because the virtual network is not located in the same region as TDVM1.

    The proposed solution is more accurately described as incomplete because a peering must also be created.

    > Take note that a virtual machine, virtual network and network interface must be in the same region or location.

    In this question both VM and NIC will be in South East Asia.

  • JR-TutorialsDojo

    Administrator
    August 6, 2025 at 11:52 am

    Hello samabc,

    Thanks for the feedback.

    The key issue lies in regional alignment rather than peering requirements.

    As noted in the explanation, “A virtual machine, its network interface, and the virtual network it connects to must all reside in the same region.”

    In the given scenario:

    • TDVM1 and the NIC are in South East Asia.
    • TDNET1 is in Japan West.

    This means the NIC cannot be attached to TDNET1, as cross-region NIC-to-VNet attachment is not supported. Additionally, VNet peering (including global peering) is used to enable communication between virtual networks, not to attach a NIC to a VNet in another region.

    Take note that a VM can be directly connected to a VNet via a NIC, as long as the VM, NIC, and VNet are in the same region. No peering is required in that case.

    Please refer to this: https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface?tabs=azure-portal

    I hope this helps! Let us know if you need further assistance.

    Best regards,
    JR @ Tutorials Dojo

  • samabc

    Member
    August 8, 2025 at 8:40 am

    > This means the NIC cannot be attached to TDNET1,

    Hi JR,

    The question asks “What should you do to connect TDVM1 to TDNET1?”

    The question does not ask “How to can you attach the NIC to TDNET1”, although that is certainly part of a solution.

    I believe there are two solutions to the question “What should you do to connect TDVM1 to TDNET1?” :

    The first solution is to redeploy TDVM1 from South East Asia to Japan West region and then create and attach the network interface in to TDVM1 in the Japan West region.

    This is the answer given in the exam and is arguably the simpler solution.

    The second solution involves three steps:

    Step 1: You create a network interface in TD1 in the South East Asia region.
    Step 2: You create a virtual network in South East Asia region (call it TDNET2).
    Step 3: You create a peering between TDNET2 and TDNET1

    The first step is given in the exam as the solution to the problem:

    > Solution: You create a network interface in TD1 in the South East Asia region.

    This solution is not incorrect – it is just one step of three that are required to implement a complete solution.

    Regards,
    Sam

  • JR-TutorialsDojo

    Administrator
    August 8, 2025 at 10:14 am

    Hi Sam,

    To clarify, the solution that suggests creating a network interface in TD1 in the South East Asia region is incorrect because it is incomplete and does not fully meet the goal stated in the question. The question asks what should be done to connect TDVM1 to TDNET1, which implies establishing a complete and functional connection between the virtual machine and the virtual network named TDNET1 located in Japan West.

    Creating a network interface in South East Asia does not achieve this connection. A network interface must be in the same region as the virtual network it connects to. The proposed solution does not include any steps to address the regional difference between the virtual machine and the target virtual network.

    It is also important to stick to the given question and the proposed solution when evaluating correctness. The question presents a specific action and asks whether it meets the goal. If the action alone does not result in a complete and valid configuration, then it must be considered incorrect, regardless of what additional steps might be possible outside the scope of the given solution.

    Hope this helps! Let us know if you need further assistance.

    Best regards,
    JR @ Tutorials Dojo

Viewing 1 - 4 of 4 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now
Skip to content