Pass the Microsoft Microsoft Certified: Azure Network Engineer Associate AZ-700 Questions and answers with CertsForce

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 name 1 .

To create a CNAME r ecor d, you need to sign in to your domain registrar’s website and go to the page for managing DNS settings 1 .

Creat e a CNAME record with the followin g information 1 :

Source domain name: wwwjelecloud.com

Destination domain name: frontdoor1.azurefd.net

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

To verify the custom domain, you need to go to the Azure portal and select your Front Door profile.  Then select Domains un der Settings and select Add 2 .

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

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

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 Associa te 2 .

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:

To connect different virtual networks in Azure, you need to use virtual network peering.  Vir tual network peering allows you to create low-latency, high-bandwidth connections between virtua l networks without using gatew ays or the internet 1 .

To create a virtual network peering, you need to go to the Azure portal and select your virtual network.  The n select Peerings under Settings a nd select + Add 2 .

On the Add peering page, enter or select the following information:

Name: Type a unique name for the peering from the source virt ual 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 sett ings: 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 eit her 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 peering 2 .

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.

To prevent hosts on VNET1 and VNET3 from communicating through VNET2, you need to use network security groups (NSGs) to filter traffic between subnets.  NSGs are r ules that allow or deny inboun d or outbound traffic based on source o r destination IP address, port, or prot ocol 3 .

To create an NSG, you need to go to the Azure portal and select Create a resource. Search for network security group and select Network security group.  Then select Create 4 .

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 crea te your NSG 4 .

To add rules to your NSG, you need to go to the Network security groups service in the Azure portal and select your NSG.  T hen select Inbound security rule s or Outbound security rules under Settings and select + Add 4 .

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 Destinatio n 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 t o 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.

Na me: Type a unique name for your rule.

Select Add to create your rule 4 .

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

To associate your NSG with a subnet, you need to go to the Virtual networks service in the Azure portal a nd select your virtual network.  Then select Subnets under Settings and select the subnet that you want to associ ate with y our NSG 5 .

On the Edit subnet page, under Network security group, select your NSG from the drop-down list.  Then select Save 5 .

Repeat the previous steps to associate your NSG with the subnets in VNET1 and VNET3 that you want to isolate from each other.

To achieve the task of ensuring that virtual machines on VNET1 and VNET2 are included automatically in a DNS zone named contoso.azure, and that they can resolve the names of the virtual machines on either virtual network, you can follow these steps:

Step-by-Step Solution

Step 1: Create a Private DNS Zone

Navigate to the Azure Portal .

Search for “Private DNS zones”  in the search bar and select it.

Click on “Create” .

Enter the DNS zone name  as contoso.azure.

Select the appropriate subscription  and resource group.

Click on “Review + create”  and then  “Create” .

Step 2: Link VNET1 and VNET2 to the DNS Zone

Go to the newly created DNS zone  (contoso.azure).

Select “Virtual network links”  from the left-hand menu.

Click on “Add” .

Enter a name  for the link (e.g., VNET1-link).

Select the subs cription  and  virtual network (VNET1) .

Enable auto-registration  to ensure that VMs are automatically registered in the DNS zone.

Click on “OK” .

Repeat the process  for VNET2.

Step 3: Configure DNS Settings for VNET1 and VNET2

Navigate to VNET1  in the Azure P ortal.

Select “DNS servers”  under the “Settings” section.

Ensure that the DNS server is set to “Default (Azure-provided)” .

Repeat the process  for VNET2.

Step 4: Verify Name Resolution

Deploy a virtual machine  in VNET1 and another in VNET2.

Connect to the v irtual machines  using Remote Desktop Protocol (RDP) or Secure Shell (SSH).

Test name resolution  by pinging the VM in VNET2 from the VM in VNET1 using its hostname (e.g., ping < VM-name > .contoso.azure).

Explanation

Private DNS Zone : This allows you to manage and resolve domain names in a private network without exposing them to the public internet.

Virtual Network Links : Linking VNET1 and VNET2 to the DNS zone ensures that VMs in these networks can register their DNS records automatically.

Auto-registration : This feature automatically registers the DNS records of VMs in the linked virtual networks, simplifying management.

DNS Settings : Using Azure-provided DNS ensures that the VMs can resolve each other’s names without additional configuration.

By following these steps, you ensure that virtual machines on VNET1 and VNET2 are included automatically in the DNS zone contoso.azure and can resolve each other’s names seamlessly.

To deploy Azure virtual machines to the France Central region and ensure they are in a network segment with an IP address range of 10.5.1.0/24, follow these steps:

Step-by-Step Solution

Step 1: Create a Virtual Network in France Central

Navi gate to the Azure Portal .

Search for “Virtual networks”  in the search bar and select it.

Click on “Create” .

Enter the following details :

Subscription : Select your subscription.

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

Name : Enter a name for the virtual network (e.g., VNet-FranceCentral).

Region : Select  France Central .

Click on “Next: IP Addresses” .

Step 2: Configure the Address Space and Subnet

In the IP Addresses tab , enter the address space as 10.5.1.0/24.

Click on “Add sub net” .

Enter the following details :

Subnet name : Enter a name for the subnet (e.g., Subnet-1).

Subnet address range : Enter 10.5.1.0/24.

Click on “Add” .

Click on “Review + create”  and then  “Create” .

Step 3: Deploy Virtual Machines to the Virtual Network

Navi gate to the Azure Portal .

Search for “Virtual machines”  in the search bar and select it.

Click on “Create”  and then  “Azure virtual machine” .

Enter the following details :

Subscription : Select your subscription.

Resource Group : Select the same resource group used for the virtual network.

Virtual machine name : Enter a name for the VM.

Region : Select  France Central .

Image : Select the desired OS image.

Size : Select the appropriate VM size.

Click on “Next: Disks” , configure the disks as needed, and then click on  “Next: Networking” .

In the Networking tab , select the virtual network (VNet-FranceCentral) and subnet (Subnet-1) created earlier.

Complete the remaining configuration steps  and click on  “Review + create”  and then  “Create” .

Explanation

Virtual Network : A vi rtual network in Azure allows you to create a logically isolated network that can host your Azure resources.

Address Space : The address space 10.5.1.0/24 ensures that the VMs are in a specific network segment.

Subnet : Subnets allow you to segment the virtu al network into smaller, manageable sections.

Region : Deploying the virtual network and VMs in the France Central region ensures that the resources are physically located in that region.

By following these steps, you can ensure that your Azure virtual machines in the France Central region are deployed within the specified IP address range of 10.5.1.0/24.