SIMULATION
Task 6
You have two servers that are each hosted by a separate service provider in New York and Germany. The server hosted in New York is accessible by using a host name of ny.contoso.com. The server hosted in Germany is accessible by using a host name of de.contoso.com.
You need to provide a single host name to access both servers. The solution must ensure that traffic originating from Germany is routed to de contoso.com. All other traffic must be routed to ny.contoso.com.
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.
You have an Azure subscription that contains an Azure Front Door Premium profile named AFD1 and an Azure Web Application Firewall (WAF) policy named WAF1. AFD1 is associated with WAF1.
You need to configure a rate limit for incoming requests to AFD1.
Solution: You add a rule to the rule set of AFD1.
Does this meet the goal?
SIMULATION
Task 5
You need to archive all the metrics of VNET1 to an existing storage account.
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.
SIMULATION
Task 5
You need to ensure that requests for wwwjelecloud.com from any of your Azure virtual networks resolve to frontdoor1.azurefd.net.
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:
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.
You have an on-premises server named Server1 that runs Windows Server.
You have an Azure subscription that contains a virtual network named VNet1.
You plan to connect Server1 to VNet1 by using Azure Network Adapter.
You need to minimize how long it takes to deploy the adapter to Server1.
What should you create first?
Ashlyn
17 days agoLenna
25 days agoThaddeus
1 months agoCarolann
2 months agoRaylene
2 months agoCordie
2 months agoAdolph
3 months agoStevie
3 months agoAdell
3 months agoLawana
4 months agoDeja
4 months agoTalia
5 months agoLashawna
5 months agoChaya
5 months agoBarb
5 months agoMarcos
5 months agoJerilyn
5 months agoNarcisa
6 months agoLashaunda
7 months agoGabriele
8 months agoMaurine
8 months agoTarra
8 months ago