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?
SIMULATION
Task 7
You need to ensure that hosts on VNET2 can access hosts on both VNET1 and VNET3. The solution must prevent hosts on VNET1 and VNET3 from communicating through VNET2.
Here are the steps and explanations for ensuring that hosts on VNET2 can access hosts on both VNET1 and VNET3, but hosts on VNET1 and VNET3 cannot communicate through VNET2:
On the Add peering page, enter or select the following information:
Name: Type a unique name for the peering from the source virtual network to the destination virtual network.
Virtual network deployment model: Select Resource manager.
Subscription: Select the subscription that contains the destination virtual network.
Virtual network: Select the destination virtual network from the list or enter its resource ID.
Name of the peering from [destination virtual network] to [source virtual network]: Type a unique name for the peering from the destination virtual network to the source virtual network.
Configure virtual network access settings: Select Enabled to allow resources in both virtual networks to communicate with each other.
Allow forwarded traffic: Select Disabled to prevent traffic that originates from outside either of the peered virtual networks from being forwarded through either of them.
Allow gateway transit: Select Disabled to prevent either of the peered virtual networks from using a gateway in the other virtual network.
Use remote gateways: Select Disabled to prevent either of the peered virtual networks from using a gateway in the other virtual network as a transit point to another network.
Select Add to create the peering2.
Repeat the previous steps to create peerings between VNET2 and VNET1, and between VNET2 and VNET3. This will allow hosts on VNET2 to access hosts on both VNET1 and VNET3.
On the Create a network security group page, enter or select the following information:
Subscription: Select your subscription name.
Resource group: Select your resource group name.
Name: Type a unique name for your NSG.
Region: Select the same region as your virtual networks.
Select Review + create and then select Create to create your NSG4.
On the Add inbound security rule page or Add outbound security rule page, enter or select the following information:
Source or Destination: Select CIDR block.
Source CIDR blocks or Destination CIDR blocks: Enter the IP address range of the source or destination subnet that you want to filter. For example, 10.0.1.0/24 for VNET1 subnet 1, 10.0.2.0/24 for VNET2 subnet 1, and 10.0.3.0/24 for VNET3 subnet 1.
Protocol: Select Any to apply the rule to any protocol.
Action: Select Deny to block traffic from or to the source or destination subnet.
Priority: Enter a number between 100 and 4096 that indicates the order of evaluation for this rule. Lower numbers have higher priority than higher numbers.
Name: Type a unique name for your rule.
Select Add to create your rule4.
Repeat the previous steps to create inbound and outbound rules for your NSG that deny traffic between VNET1 and VNET3 subnets. For example, you can create an inbound rule that denies traffic from 10.0.1.0/24 (VNET1 subnet 1) to 10.0.3.0/24 (VNET3 subnet 1), and an outbound rule that denies traffic from 10.0.3.0/24 (VNET3 subnet 1) to 10.0.1.0/24 (VNET1 subnet 1).
Repeat the previous steps to associate your NSG with the subnets in VNET1 and VNET3 that you want to isolate from each other.
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 on-premises DNS server named Server1 that hosts a primary DNS zone named fabrikam.com.
You have an Azure subscription that contains the resources shown in the following table.
Users on the on-premises network access resources on all the virtual networks by using a Site-to-Site (S2S) VPN. You need to deploy an Azure DNS Private Resolver solution that meets the following requirements:
* Resources connected to the virtual networks must be able to resolve DNS names for fabrikam.com.
* Server1 must be able to resolve the DNS names of the resources in contoso.com.
* The solution must minimize costs and administrative effort.
What is the minimum number of resolvers you should deploy?
SIMULATION
Task 1
You plan to deploy a firewall to subnetl-2. The firewall will have an IP address of 10.1.2.4.
You need to ensure that traffic from subnetl-1 to the IP address range of 192.168.10.0/24 is routed through the firewall that will be deployed to subnetl-2. The solution must be achieved without using dynamic routing protocols.
Destination: 192.168.10.0/24
Next hop type: Virtual appliance
Next hop address: 10.1.2.4
Adolph
6 days agoStevie
21 days agoAdell
26 days agoLawana
1 months agoDeja
2 months agoTalia
2 months agoLashawna
2 months agoChaya
2 months agoBarb
3 months agoMarcos
3 months agoJerilyn
3 months agoNarcisa
3 months agoLashaunda
4 months agoGabriele
5 months agoMaurine
5 months agoTarra
6 months ago