Exam AZ-700 All Questions

View all questions & answers for the AZ-700 exam

Exam AZ-700 topic 1 question 22 discussion

Actual exam question from Microsoft's AZ-700

Question #: 22
Topic #: 1

SIMULATION
-

Username and password
-

Use the following login credentials as needed:

To enter your username, place your cursor in the Sign in box and click on the username below.

To enter your password, place your cursor in the Enter password box and click on the password below.

Azure Username: [email protected]

Azure Password: xxxxxxxxxx
-

If the Azure portal does not load successfully in the browser, press CTRL-K to reload the
portal in a new browser tab.

The following information is for technical support purposes only:

Lab Instance: 12345678
-

You need to ensure that hosts on VNET2 can access hosts on both VNET1 and VNET3. The solution must prevent hosts on VNET1 and VNET3 from communicating through VNET2.

To complete this task, sign in to the Azure portal.

Show Suggested Answer

Suggested Answer:

by thor04 at June 17, 2023, 7:13 a.m.

Comments

Submit Cancel

Ozarsif

1 week ago

as of july, 2025, there was no labs

upvoted 1 times

...

nabeel79

2 months, 4 weeks ago

peering the HubNet1 to VNet2 and 3

upvoted 1 times

...

VeryOldITGuy

1 year, 6 months ago

In Exam Feb 2024

upvoted 1 times

...

jakubklapka

1 year, 10 months ago

In exam Sep, 2023

upvoted 2 times

...

DGUI

2 years, 1 month ago

Hello, ca?n you specify the url for this lab please

upvoted 1 times

...

Lazylinux

2 years, 1 month ago

The answer is correct but should be clearer..YEs it is kind of HUB-Spoke setup mainly using vNET peering, you configure it from vNET2 and allow traffic both ways i.e. i.e. vms on both peered vNET2 and vNET1 can communicate with each other or you could just configure to ONLY allow communication for vms in vNET2 to vNET1 but not otherway round. Now to prevent vNET1 and vNET3 from accessing other resources such as internet or vms in vNET1 able to communicate with vms in vNET3 is to DISABLE GATEWAY TRANSIT. I believe some inform is missing in this question like address space, if vNETs in same region or not and in same subscription of not but assume simple scenario it is easier to create peering (Global reach Peering is also possible) than S2S for vNETS. For me when not routes or different Geo i would use S2S for vNETs See my next comments

upvoted 1 times

grimrodd

1 year ago

By default peerings are not transient.

upvoted 1 times

...

Eddie_Sli

1 year ago

disagreed. VNET peering, no need to be configured for both VNETs, set it up on one VNET, it will peer with the other one.

upvoted 1 times

...

Lazylinux

2 years, 1 month ago

Following on Here snippet for S2S for vNETs from MS following reasons: **Cross region geo-redundancy and geo-presence You can set up your own geo-replication or synchronization with secure connectivity without going over Internet-facing endpoints. With Azure Traffic Manager and Load Balancer, you can set up highly available workload with geo-redundancy across multiple Azure regions. One important example is to set up SQL Always On with Availability Groups spreading across multiple Azure regions. **Regional multi-tier applications with isolation or administrative boundary Within the same region, you can set up multi-tier applications with multiple virtual networks connected together due to isolation or administrative requirements. https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vnet-vnet-rm-ps

upvoted 1 times

...

thor04

2 years, 2 months ago

Do we need to create the connection for VPN site-to-site ?

upvoted 1 times

Lazylinux

2 years, 1 month ago

No we dont, see my comments

upvoted 1 times

...