support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
CrowdStrike
Anthropic
All Vendors
  1. Home
  2. Exams
  3. Microsoft
  4. AZ-700

Free AZ-700 Exam Braindumps
Designing and Implementing Microsoft Azure Networking Solutions Questions 136–140 (page: 29)

Updated On: 10-Feb-2026
Page 29 of 75
PDF with 396 Questions
View Related Case Study

HOTSPOT (Drag and Drop is not supported)

Your on-premises network contains the subnets shown in the following table.



The network contains a firewall named FW1 that uses a public IP address of 131.107.100.200.

You have an Azure subscription that contains the resources shown in the following table.



You plan to configure a Site-to-Site (S2S) VPN named VPN1 that will connect GW1 to FW1.

You need to configure LNG1 to support VPN1. The solution must meet the following requirements:

Ensure that the resources on Subnet1 and Subnet2 can communicate with the resources on VNet1.

Minimize administrative effort.

How should you configure LNG1? To answer, select the appropriate options in the answer area.

Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: 192.168.10.0/24 and 192.168.20.0/24

Address space

We use both the addresses of Subnet1 and Subnet2.

For Address space: The address range or ranges for the network this local network gateway represents. For example: 192.168.0.0/16. If you add multiple address space ranges, make sure that the ranges you specify don't overlap with ranges of other networks that you want to connect to.

Box 2: 131.107.100.200
IP address
For IP address use the public IP address of your local gateway on-premises.
In this case it is the Public Address of firewall FW1.


Reference:

https://learn.microsoft.com/en-us/azure/storage/files/storage-files-configure-s2s-vpn



View Related Case Study

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: User-12345678@cloudslice.onmicrosoft.com
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 plan to deploy a VPN gateway and an ExpressRoute gateway to VNET2.

You need to prepare VNET2 to ensure that you can deploy the gateways.

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

  1. See Explanation section for answer.

Answer(s): A

Explanation:

Configure ExpressRoute and Site-to-Site coexisting connections using the Azure portal Step 1: In the Azure portal, search for and select virtual networks.

Step 2: On the Virtual networks page, select the virtual network you want to add a subnet to. Select the VNET2 virtual network

Step 3: On the virtual network page, select Subnets from the left navigation.

Step 4: On the Subnets page, select + Subnet.

Step 5: On the Add subnet screen, enter or select values for the subnet settings.

You can configure the following settings for a subnet:
* Name - The name must be unique within the virtual network.
* Subnet address range - The range must be unique within the address space and can't overlap with other subnet address ranges in the virtual network. You must specify the address space by using Classless Inter- Domain Routing (CIDR) notation.

The Gateway Subnet must be /27 or a shorter prefix (such as /26 or /25).

Specify: 10.0.0.0/27

Step 6: Select Save.


Reference:

https://learn.microsoft.com/en-us/azure/expressroute/how-to-configure-coexisting-gateway-portal https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-manage-subnet



View Related Case Study

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: User-12345678@cloudslice.onmicrosoft.com
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 plan to manage the public DNS records for a domain named fabrikam.com by using an Azure solution.

You need to ensure that wvw.fabrikam.com resolves to 131.107.2.50.

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

  1. See Explanation section for answer.

Answer(s): A

Explanation:

Create an Azure DNS zone [already done] and record using the Azure portal

Create a DNS record
DNS records are created for your domain inside the DNS zone. A new address record, known as an 'A' record, is created to resolve a host name to an IPv4 address.

To create an 'A' record

Step 1: In the Azure portal, under All resources, open the fabrikam.com DNS zone. You can enter fabrikam.com in the Filter by name box to find it more easily.

Step 2: In the Add a record set window, enter or select the following values:

Step 3: At the top of the fabrikam.com DNS zone page, select + Record set. Name: Type www. This record name is the host name that you want to resolve to the specified IP address. Type: Select A. 'A' records are the most common, but there are other record types for mail servers ('MX'), IP v6 addresses ('AAAA'), and so on.
TTL: Type 1. Time-to-live of the DNS request specifies how long DNS servers and clients can cache a response.
TTL unit: Select Hours. The time unit for the TTL entry is specified here. IP address: Type 131.107.2.50. This value is the IP address that the record name resolves to. In a real-world scenario, you would enter the public IP address for your web server.

Step 4: Select OK to create the A record.


Reference:

https://learn.microsoft.com/en-us/azure/dns/dns-getstarted-portal



View Related Case Study

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: User-12345678@cloudslice.onmicrosoft.com

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 plan to configure a VPN tunnel for VNET2.

You need to ensure that all internet traffic from subnet2-1 is routed through an on-premises firewall before reaching the destination. The solution must be achieved without using dynamic routing protocols.

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

  1. See Explanation section for answer.

Answer(s): A

Explanation:

Route network traffic with a route table using the Azure portal Azure routes traffic between all subnets within a virtual network, by default. You can create your own routes to override Azure's default routing. Custom routes are helpful when, for example, you want to route traffic between subnets through a network virtual appliance (NVA) (or a Firewall).

Send Traffic from Azure Firewall to Internet

Even if the Azure Firewall is created with support for Forced Tunneling, you do not have to add a Route Table here at all.
The default behavior will provide outbound connectivity to Internet just like a regular firewall.

Phase 1: Create a route table
In this section, create a route table to define the route of the traffic through the NVA virtual machine. The route table is associated to the subnet-1 subnet where the vm-public virtual machine is deployed.

Step 1: In the search box at the top of the portal, enter Route table. Select Route tables in the search results.

Step 2: Select + Create.

Step 3: In Create Route table enter or select the following information:
* Details omitted. *

Step 4: Select Review + create.

Step 5: Select Create.

Phase 2: Create a route
In this section, create a route in the route table that you created in the previous steps.

Step 1: In the search box at the top of the portal, enter Route table. Select Route tables in the search results.

Step 2: Select route-table-public.

Step 3: In Settings select Routes.

Step 4: Select + Add in Routes.

Step 5: Enter or select the following information in Add route:
Route name: to-firewall.

Destination type: Select IP Addresses.
Destination IP addresses/CIDR ranges Enter 0.0.0.0/0

Use 0.0.0.0/0 for any unmatched routes.

Next hop type: Select Virtual appliance.
Next hop address: Enter the IP address of the Firewall.
This is the IP address you of the Firewall.

Step 6: Select Add.

Step 7: Select Subnets in Settings.

Step 8: Select + Associate.

Step 9: Enter or select the following information in Associate subnet:

Setting Value
Virtual network: Select VNET2
Subnet: Select subnet2-1.

Step 10: Select OK.

Note: Route network traffic with a route table using the Azure portal Azure routes traffic between all subnets within a virtual network, by default. You can create your own routes to override Azure's default routing. Custom routes are helpful when, for example, you want to route traffic between subnets through a network virtual appliance (NVA).


Reference:

https://learn.microsoft.com/en-us/azure/virtual-network/tutorial-create-route-table-portal https://learn.microsoft.com/en-us/answers/questions/1356750/internet-routing-via-azure-firewall



View Related Case Study

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: User-12345678@cloudslice.onmicrosoft.com
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 plan to deploy two DNS servers to subnet2-1. Each server will host a DNS zone for fabrikam,com. The DNS zones will contain records from the on-premises network only. The IP address of the DNS servers will be 10.2.1.4 and 10.2.1.5.

You need to ensure that virtual machines on VNET2 can resolve the names of the on-premises servers in fabrikam.com.

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

  1. See Explanation section for answer.

Answer(s): A

Explanation:

Azure DNS Private Resolver
The Azure DNS Private Resolver is a service that can resolve on-premises DNS queries for Azure DNS private zones. Previously, it was necessary to deploy a VM-based custom DNS resolver, or use non-Microsoft DNS, DHCP, and IPAM (DDI) solutions to perform this function.

Create a DNS resolver inside the virtual network

Step 1: In the Azure portal, search for DNS Private Resolvers.

Step 2: Select DNS Private Resolvers, select Create, and then on the Basics tab for Create a DNS Private Resolver enter the following:

Subscription
Resource group:
Name: Enter a name for your DNS resolver (ex: mydnsresolver). Region: Choose the region you used for the VNET2 virtual network.
Virtual Network: Select VNET2.

Don't create the DNS resolver yet.



Add rules to the forwarding ruleset
Add two new conditional forwarding rules to the ruleset.

Step 3: On the myruleset | Rules page, select Add, and enter the following rule data:

Rule Name: Internal
Domain Name: internal.fabrikam.com. (fabrikam.com domain in the question) Rule State: Enabled
Under Destination IP address enter 10.2.1.4, and then select Add.

Question has the IP address of the DNS servers will be 10.2.1.4 and 10.2.1.5.

Step 4: On the myruleset | Rules page, select Add, and enter the following rule data:

Rule Name: Internal
Domain Name: internal.fabrikam.com. (fabrikam.com domain in the question) Rule State: Enabled
Under Destination IP address enter 10.2.1.5, and then select Add.


Reference:

https://learn.microsoft.com/en-us/azure/dns/dns-private-resolver-get-started-portal



  PDF
Viewing page 29 of 75
Viewing questions 141 - 145 out of 396 questions


Post your Comments and Discuss Microsoft AZ-700 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!