Microsoft AZ-700 Exam Questions

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

Step-by-Step Solution

Step 1: Create a Traffic Manager Profile

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: SelectGeographic.

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''.

Step 2: Configure Endpoints

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: SelectExternal endpoint.

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

FQDN: Enterny.contoso.com.

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

Click on ''Add''to save the endpoint.

Repeat the processto add the second endpoint:

Type: SelectExternal endpoint.

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

FQDN: Enterde.contoso.com.

Geographic region: SelectEurope.

Step 3: Adjust Geographic Routing

Navigate to the Traffic Manager profile.

Select ''Configuration''from the left-hand menu.

Under ''Geographic routing'', adjust the regions:

For theGermanyEndpoint, ensure that the geographic region is set toEurope.

For theNewYorkEndpoint, ensure that the geographic region is set toWorld(excluding Europe).

Step 4: Test the Configuration

Use a DNS query toolto test the routing.

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

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

Explanation

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 the 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.

By following these steps, you can provide a single host name that routes traffic tode.contoso.comfor users in Germany and tony.contoso.comfor users from other locations, ensuring efficient and appropriate traffic management.

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

Open the Azure Portal.

Search for ''Virtual networks''and selectVNET1from 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 namefor the diagnostic setting (e.g.,VNET1-Metrics-Archive).

Select the metricsyou want to archive. You can choose from various metrics likeTotalBytesReceived,TotalBytesSent, etc.

Under ''Destination details'', select''Archive to a storage account''.

Choose the existing storage accountwhere you want to archive the metrics.

Configure the retention periodif needed.

Step 4: Save the Configuration

Review your settingsto 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 numerical 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 future 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.

Here are the steps and explanations for ensuring that requests for wwwjelecloud.com from any of your Azure virtual networks resolve to frontdoor1.azurefd.net:

To use a custom domain with your Azure Front Door, you need to create a CNAME record with your domain provider that points to the Front Door default frontend host.A CNAME record is a type of DNS record that maps a source domain name to a destination domain name1.

To create a CNAME record, you need to sign in to your domain registrar's website and go to the page for managing DNS settings1.

Create a CNAME record with the following information1:

Source domain name: wwwjelecloud.com

Destination domain name: frontdoor1.azurefd.net

Save your changes and wait for the DNS propagation to take effect1.

To verify the custom domain, you need to go to the Azure portal and select your Front Door profile.Then select Domains under Settings and select Add2.

On the Add a domain page, select Non-Azure validated domain as the Domain type and enter wwwjelecloud.com as the Domain name.Then select Add2.

On the Domains page, select wwwjelecloud.com and select Verify.This will check if the CNAME record is correctly configured2.

Once the domain is verified, you can associate it with your Front Door endpoint. On the Domains page, select wwwjelecloud.com and select Associate endpoint.Then select your Front Door endpoint from the drop-down list and select Associate2.