Free Practice Questions for Microsoft AZ-700 Exam

To deploy a firewall to subnetl-2, you need to create a network virtual appliance (NVA) in the same virtual network as subnetl-2.  An NVA is a virtual machine that performs network functions, such as firewall, routing, or load balanc ing 1 .

To create an NVA, you need to create a virtual machine in the Azure portal and select an image that has the firewall software installed.  You can choose from th e Azure Marketplace or upload your own image 2 .

To assign the IP address of 10.1.2.4 to the NVA, you need to create a static private IP address for the network interface of the virtual machine.  You can do this in the IP configura tions settings of the network interface 3 .

To ensure that traffic from subnetl-1 to the IP address range of 192.1 68.10.0/24 is routed through the NVA, you need to create a user-defined route (UDR) table and associate it with subnetl-1.  A UDR table allows you to override the default routing behavior of Azure and specify custom routes for your subnets 4 .

To create a UDR ta ble, you need to go to the Route tables service in the Azure portal and select + Create.  You can give a name and a resource group for the route table 5 .

To create a custom route, you need to select Routes in the route table and select + Add.  You can enter the f ollowing information for the route 5 :

Destination: 192.168.10.0/24

Next hop type: Virtual appliance

Next hop address: 10.1.2.4

To associate the route table with subnetl-1, you need to select Subnets in the route table and select + Associate.  Y ou can select the virtual network and subnet that you want to asso ciate with the route table 5 .

To provide a single host name that routes traffic based on the origin, you can use  Azure Traffic Manager . This service allows you to route traffic to different endpoints based on various routing methods, i ncluding geographic routing.

Navigate to the Azure Portal .

Search for “Traffic Manager profiles”  and select it.

Click on “Create” .

Enter the following details :

Name : Enter a name for the Traffic Manager profile (e.g.,  ContosoTrafficManager ).

Routing method : Select  Geographic .

Subscription : Select your subscription.

Resource group : Select an existing resource group or create a new one.

Resource group location : Choose a location (this does not affect the routing).

Click on “Create” .

Navigate to the newly created Traffic Manager profile .

Select “Endpoints”  from the left-hand menu.

Click on “Add”  to add a new endpoint.

Enter the following details :

Type : Select  Exter nal endpoint .

Name : Enter a name for the endpoint (e.g.,  NewYorkEndpoint ).

FQDN : Enter  ny.contoso.com .

Geographic region : Select  “World”  (this will be adjusted later).

Click on “Add”  to save the endpoint.

Repeat the process  to add the second endpoint:

Type : Select  External endpoint .

Name : Enter a name for the endpoint (e.g.,  GermanyEndpoint ).

FQDN : Enter  de.contoso.com .

Geographic region : Select  Europe .

Navigate to the Traffic Manager profile .

Select “Configuration”  from the left-hand menu.

Under “Geographic routing” , adjust the regions:

For the  GermanyEndpoint , ensure that the geographic region is set to  Europe .

For the  NewYorkEndpoint , ensure that the geographic region is set to  World  (excluding Europe).

Use a DNS query tool  to test the routing.

From a location in Germany , query the Traffic Manager profile’s DNS name and ensure it resolves to  de.contoso.com .

From a location outside Europe , query the Traffic Manager profile’s DNS name and ensure it resolves to  ny.contoso.com .

Azure Traffic Manager : This service uses DNS to direct client requests to the most appropriate endpoint based on the routing method you choose. Geographic routing ensures that traffic is directed based on t he origin of the request.

Geographic Routing : This method allows you to route traffic based on the geographic location of the DNS query origin, ensuring that users are directed to the nearest or most appropriate endpoint.

Step-by-Step Solution Step 1: Create a Traffic Manager Profile Step 2: Configure Endpoints Step 3: Adjust Geographic Routing Step 4: Test the Configuration Explanation By following these steps, you can provide a single host name that routes traffic to  de.contoso.com  for users in Germany and to  ny.contoso.com  for users from other locations, ensuring efficient and appropriate traffic management.

To ensure that hosts on VNET1 and VNET2 can communicate with minimal latency, you can use  Virtual Network Peering . This method connects the two virtual networks directly through the Microsoft backbone network, ensuring low-latency and high-bandwidth communication.

Step-by-Step Solution

Step 1: Set Up Virtual Network Peering

Navigate to the Azure Portal .

Search for “Virtual networks”  and select VNET1.

In the left-hand menu , select  “Peerings”  under the “Settings” section.

Click on “Add”  to create a new peering.

Enter the following details :

Name : Enter a name for the peering (e.g., VNET1-to-VNET2).

Peer virtual network : Select VNET2.

Allow virtual network access : Ensure this is enabled.

Allow forwarded traffic : Enable if needed.

Allow gateway transit : Enable if needed.

Click on “Add” .

Step 2: Configure Peering on VNET2

Navigate to VNET2  in the Azure Portal.

In the left-hand menu , select  “Peerings”  under the “Sett ings” section.

Click on “Add”  to create a new peering.

Enter the following details :

Name : Enter a name for the peering (e.g., VNET2-to-VNET1).

Peer virtual network : Select VNET1.

Allow virtual network access : Ensure this is enabled.

Allow forwarded traffic : Enable if needed.

Allow gateway transit : Enable if needed.

Click on “Add” .

Explanation

Virtual Network Peering : This feature connects two virtual networks in the same or different regions, allowing resources in both networks to communicate with each othe r as if they were part of the same network.  Th e traffic between peered virtual networks uses the Micros oft backbone infrastructure, ensuring low la tency and hi gh bandwidth 1 2 .

Allow Virtual Network Access : This setting ensures that the virtual networks can communicate with each other.

Allow Forwarded Traffic : This setting allows traffic forwarded from a network security appliance in the peered virtual network.

Allow Gateway Transit : This setting allows the peered virtual network to use the gateway in the local virtual network.

By following these steps, you can ensure that hosts on VNET1 and VNET2 can communicate with minimal latency, leveraging the high-speed Microsoft backbone network.

To archive all the metrics of VNET1 to an existing storage account, you can use Azure Monitor’s diagnostic settings. Here’s how you can do it:

Step-by-Step Solution

Step 1: Navigate to VNET1 in the Azure Portal

Ope n the Azure Portal .

Search for “Virtual networks”  and select  VNET1  from the list.

Step 2: Configure Diagnostic Settings

In the VNET1 blade , select  “Diagnostic settings”  under the “Monitoring” section.

Click on “Add diagnostic setting” .

Step 3: Set Up the Diagnostic Setting

Enter a name  for the diagnostic setting (e.g., VNET1-Metrics-Archive).

Select the metrics  you want to archive. You can choose from various metrics like TotalBytesReceived, TotalBytesSent, etc.

Under “Destination details” , select  “Archive to a storage account” .

Choose the existing storage account  where you want to archive the metrics.

Configure the retention period  if needed.

Step 4: Save the Configuration

Review your settings  to ensure everything is correct.

Click on “Save”  to apply the diagnostic setting.

Explanation

Diagnostic Settings : These allow you to collect and route metrics and logs from your Azure resources to various destinations, including storage accounts, Log Analytics workspaces, and Event Hubs.

Metrics : Metrics provide num erical data about the performance and health of your resources. Archiving these metrics helps in long-term analysis and compliance.

Storage Account : Using an existing storage account ensures that the metrics are stored securely and can be accessed for futu re analysis.

By following these steps, you can ensure that all the metrics of VNET1 are archived to your existing storage account, enabling you to monitor and analyze the performance and health of your virtual network over time.