Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam AZ-700 Topic 6 Question 57 Discussion

Actual exam question for Microsoft's AZ-700 exam
Question #: 57
Topic #: 6
[All AZ-700 Questions]

SIMULATION

Task 1

You need to ensure that virtual machines on VNET1 and VNET2 are included automatically in a DNS zone named contoso.azure. The solution must ensure that the virtual machines on VNET1 and VNET2 can resolve the names of the virtual machines on either virtual network.

Show Suggested Answer Hide Answer
Suggested Answer: A

Here are the steps and explanations for creating the object that will provide the IP addressing configuration of the on-premises network to the Site-to-Site VPN:

The object that you need to create is called a local network gateway. A local network gateway represents your on-premises network and VPN device in Azure. It contains the public IP address of your VPN device and the address prefixes of your on-premises network that you want to connect to the Azure virtual network1.

To create a local network gateway, you need to go to the Azure portal and selectCreate a resource. Search forlocal network gateway, selectLocal network gateway, then selectCreate2.

On theCreate local network gatewaypage, enter or select the following information and accept the defaults for the remaining settings:

Name: Type a unique name for your local network gateway.

IP address: Type the public IP address of your VPN device, which is 131.107.50.60 in this case.

Address space: Type the internal address range of your on-premises network, which is 10.10.0.0/16 in this case.

Subscription: Select your subscription name.

Resource group: Select your resource group name.

Location: Select the same region as your virtual network.

SelectReview + createand then selectCreateto create your local network gateway2.


Contribute your Thoughts:

Darrin
14 days ago
I hope the solution doesn't involve any DNS witchcraft. That's the kind of thing that keeps me up at night.
upvoted 0 times
Leah
3 days ago
User 1: Don't worry, it's not that complicated.
upvoted 0 times
...
...
Glory
26 days ago
Is it just me, or does this sound like a job for a network engineer with a magic wand?
upvoted 0 times
...
Doug
30 days ago
I bet the answer involves some Azure networking wizardry. Can't wait to see the step-by-step guide!
upvoted 0 times
Ceola
16 hours ago
That's right, and the solution should allow the virtual machines on both virtual networks to resolve each other's names.
upvoted 0 times
...
Kattie
10 days ago
Yes, we also need to ensure that the virtual machines on VNET1 and VNET2 are automatically included in the DNS zone.
upvoted 0 times
...
Kimbery
16 days ago
I think we need to create a DNS zone named contoso.azure for this task.
upvoted 0 times
...
...
Louis
1 months ago
Ah, good old DNS zones. This should be a piece of cake, as long as we follow the instructions carefully.
upvoted 0 times
Hector
2 days ago
User 2: Next, we need to configure VNET1 and VNET2 to automatically include their virtual machines in the DNS zone.
upvoted 0 times
...
Lindy
3 days ago
User 1: Let's start by creating a DNS zone named contoso.azure.
upvoted 0 times
...
...
Sharika
2 months ago
I believe we need to create a virtual network link between VNET1 and VNET2 for them to resolve each other's names.
upvoted 0 times
...
Shakira
2 months ago
This seems like a straightforward task, but I wonder if there are any potential gotchas or edge cases we should consider.
upvoted 0 times
Jess
1 months ago
It's important to double check the configuration to avoid any potential issues.
upvoted 0 times
...
Hassie
1 months ago
Make sure to follow the step by step instructions provided in the Explanation.
upvoted 0 times
...
...
Tom
2 months ago
I agree, setting up DNS zones can be tricky.
upvoted 0 times
...
Sage
2 months ago
I think this question is challenging.
upvoted 0 times
...

Save Cancel