Exam AZ-103 All Questions

View all questions & answers for the AZ-103 exam

Exam AZ-103 topic 4 question 14 discussion

Actual exam question from Microsoft's AZ-103

Question #: 14
Topic #: 4

You have two subscriptions named Subscription1 and Subscription2. Each subscription is associated to a different Azure AD tenant.
Subscription1 contains a virtual network named VNet1. VNet1 contains an Azure virtual machine named VM1 and has an IP address space of 10.0.0.0/16.
Subscription2 contains a virtual network named VNet2. VNet2 contains an Azure virtual machine named VM2 and has an IP address space of 10.10.0.0/24.
You need to connect VNet1 to VNet2.
What should you do first?

A. Move VM1 to Subscription2.
B. Modify the IP address space of VNet2.
C. Provision virtual network gateways.
D. Move VNet1 to Subscription2.

Show Suggested Answer

Suggested Answer: C 🗳️
The virtual networks can be in the same or different regions, and from the same or different subscriptions. When connecting VNets from different subscriptions, the subscriptions do not need to be associated with the same Active Directory tenant.
Configuring a VNet-to-VNet connection is a good way to easily connect VNets. Connecting a virtual network to another virtual network using the VNet-to-VNet connection type (VNet2VNet) is similar to creating a Site-to-Site IPsec connection to an on-premises location. Both connectivity types use a VPN gateway to provide a secure tunnel using IPsec/IKE, and both function the same way when communicating.
The local network gateway for each VNet treats the other VNet as a local site. This lets you specify additional address space for the local network gateway in order to route traffic.
References:
https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal

by Marz at Oct. 23, 2019, 9:54 a.m.

Comments

Submit Cancel

certificatores

Highly Voted 5 years, 3 months ago

there should be zero comment on this very easy question but now due to the amount of the comments, readers will be confused.... virtual network gateway is the answer. looks like, people here try to mislead others.

upvoted 32 times

walexkino

4 years, 3 months ago

thast what i dont like about examtopics too much misleading talks `

upvoted 1 times

...

gsbence

Highly Voted 5 years, 2 months ago

The given answer is right. Side note: Cross AAD tenant vnet peering is now available. https://azure.microsoft.com/en-in/updates/cross-aad-vnet-peering/

upvoted 8 times

josemessias

5 years, 1 month ago

Yes, vnet peering is a way to establish connectivity, but this choice is not available So, the righ answer is C. Provision virtual network gateways

upvoted 2 times

...

sidharthwader

Most Recent 4 years, 2 months ago

When you want to connect two VNets we can use either virtual network gateway or peering. As here only Virtual Network gateway exists so its the solution.

upvoted 2 times

...

OsimIndia

4 years, 6 months ago

guys,, here it is asked to connect Vnets and not for peering... So why are we checking if address space overlaps or not... We simply need to provision Vnet gateway. As simple :)

upvoted 1 times

...

Tomzinho

4 years, 7 months ago

They're not overlapping 10.0.0.0/8 = 10.0.0.0 - 10.254.254.254 10.0.0.0/16 = 10.0.0.0 - 10.0.254.254 10.10.0.0/24 = 10.10.0.0 - 10.10.0.254 If VNet1 was 10.0.0.0/8, then the address space overlap. Answer is C

upvoted 2 times

...

Thi

4 years, 8 months ago

C. Provision virtual network gateways.

upvoted 2 times

...

wideawake

5 years ago

if we create site-to-site vpn connection between vnet1 and vnet2 for connectivty.right answer must be B. because there is no address space left for the gateway subnet.

upvoted 2 times

KenZx

4 years, 7 months ago

Correct, Vnet2 need address space for gateway subnet so B is correct

upvoted 2 times

...

ilaiya

5 years, 2 months ago

Answer is correct... IP ranges are diff.

upvoted 5 times

...

Cloudyuga

5 years, 2 months ago

Its a correct answer Azure AD tenant is only associated with 1 a/c only here he is saying 2 differenr AD tenant a/c means these subscription are of different account all together so we need VPN connection i.e. answer C. Provision virtual network gateways.

upvoted 4 times

...

sapien45

5 years, 3 months ago

Peering would alos work . You can also peer virtual networks in different supported regions and in different Azure subscriptions, https://docs.microsoft.com/en-us/azure/virtual-network/tutorial-connect-virtual-networks-portal

upvoted 2 times

asdfgh1234567

5 years, 2 months ago

would work but isn't an option here unfortunately

upvoted 2 times

pandeya442

5 years, 2 months ago

Agreed

upvoted 2 times

...

johnsteve

5 years, 5 months ago

Jesus, the range is overlapping. 10.0.0.0/24 is part of 10.0.0.0/16.

upvoted 2 times

johnsteve

5 years, 5 months ago

Jesus, I read that too quick. 10.10.0.0/24 is NOT part of 10.0.0.0/16

upvoted 15 times

DanteSurman

1 year, 1 month ago

you and me both, haha

upvoted 1 times

...

shanan_ilen

4 years, 12 months ago

Yeah true johnsteve

upvoted 4 times

...

yicim24216

5 years, 6 months ago

It looks like, as of recently, you can also use vnet peering https://azure.microsoft.com/en-us/updates/cross-aad-vnet-peering/

upvoted 5 times

Lubomir

5 years, 4 months ago

Agree, to connect 2VNets in Azure, you should you peering (even so they are in different AD tenants), so this question is kind of old. Anyway from the options, C should be the on to go with.

upvoted 4 times

praveen97

5 years ago

Agree with Lubomir & yicim24216. As per the available options, answer is C. Provision virtual network gateways. But this can also be acheived with VNet peering. https://docs.microsoft.com/en-us/azure/virtual-network/create-peering-different-subscriptions

upvoted 1 times

...

erick

5 years, 7 months ago

it's different AD tent!!!!C is correct!

upvoted 3 times

macco455

5 years, 1 month ago

Does not matter. Virtual Network gateway is he answer here or you could do Peering if the answers get changed.

upvoted 1 times

...

Learner3000

5 years, 7 months ago

Hi all. Are you sure the vnets are not overlapping? 10.0.0.0/24 (10.0.0.1 - 10.0.0.254), and 10.0.0.0/16 (10.0.0.1 - 10.0.255.254). I think the answer is B.

upvoted 3 times

saran1987

5 years, 7 months ago

No, definitely the addresses are not overlapping. If you see the CIDR notation /16, it would make the change only in the last two octets of 10.0.0.0/16. The subnet in subscription 2 contains a change in the first two octet 10.10.0.0/24 hence it is not overlapping.

upvoted 13 times

...

Novix

5 years, 5 months ago

You made a mistake with the /24 it's 10.10.0.0/24. You have read it as 10.0.0.0/24. The answer is C

upvoted 5 times

...

Alag

5 years, 8 months ago

Vnets are not overlapping and the subscriptions are in different vnet so we have to use a express route or vpn gateway

upvoted 1 times

...

Alag

5 years, 8 months ago

Vnets are not overlapping and the subscriptions are in different vnet so we have to use a express route or vpn gateway

upvoted 3 times

...

Marz

5 years, 8 months ago

I think the correct answer is B. Cause the addess spaces overlap, you cannot use vnet peering. So first need to change the Address space and then change the IP of the VM2. https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal#create-and-configure-testvnet1

upvoted 7 times

Marz

5 years, 8 months ago

disregard this, the vnets are not overlapping, so the suggested answer is correct :-)

upvoted 30 times

...

Milk

5 years, 2 months ago

They're in the same space , they don't overlap.

upvoted 3 times

Milk

5 years, 2 months ago

10.[0].0.0/16. 10.[10].0.0/24 ----- > you can interpret as 10.0.0/24 , careful with the eye :)

upvoted 15 times

...