Contoso has a hub-spoke topology in Azure. The hub VNet contains a domain controller running on a VM. Spoke VNets currently use Azure-provided DNS. You need to ensure that VMs in spoke VNets resolve internal DNS names from the domain controller while still resolving public hostnames. You also need to minimize administrative overhead. What should you do?

Create an Azure private DNS zone for the domain and link it to all spoke VNets.

Add a DNS record set in the public Azure DNS zone pointing to the domain controller's private IP.

Change the DNS server setting on each spoke VNet to the private IP address of the domain controller VM.

Configure a DNS forwarder on each VM using a custom script extension.

You have an internal load balancer in a hub virtual network that forwards traffic to a backend pool of VMs in a spoke virtual network. The VMs are healthy and the load balancer rules are configured correctly, but clients in the hub cannot reach the backend. What should you do?

Verify that the spoke virtual network is peered with the hub and that 'Use remote virtual network gateways' is enabled

Check that the backend pool's network security group allows traffic from the hub virtual network's address space

Ensure that the spoke virtual network has a route to the hub virtual network via a virtual network gateway

Add a user-defined route in the hub subnet pointing the load balancer's frontend IP to the backend pool

What is the default DNS behavior for a virtual network that has not been configured with a custom DNS server?

It has no DNS resolution until a custom DNS server is configured.

It uses the DNS server of the first VM in the network.

It uses the Azure-provided DNS service.

It uses the DNS server of the on-premises network.

You have a public load balancer that is not distributing traffic to the backend pool. The backend VMs are running and have the correct application installed. You check the load balancer's metrics and see that the 'Health Probe Status' metric shows 0 for all backend instances. What should you check first?

The VM's operating system firewall for inbound rules on the load balancer's frontend port

The network security group on the backend VMs' subnet for rules that block the health probe's source IP range

The load balancing rule's frontend port and backend port configuration

The backend pool's association with the load balancing rule

Microsoft Certified:Azure Administrator Associate

Domain 4Objective 3

Configure Name Resolution and Load Balancing AZ-104 Practice Questions (Page 4)

Part of the Implement and manage virtual networking domain, which accounts for 15–20% of the AZ-104 exam. Microsoft does not publish an official question count, but from its 100-minute exam (~40–65 total, ~6–13 in this domain), expect 2–4 from this objective — we provide 25 practice questions to prepare you well beyond it. (estimate)

25questions here

5free pages

8concepts

15–20%of the exam

Questions 16–20

16application · medium
Contoso has a hub-spoke topology in Azure. The hub VNet contains a domain controller running on a VM. Spoke VNets currently use Azure-provided DNS. You need to ensure that VMs in spoke VNets resolve internal DNS names from the domain controller while still resolving public hostnames. You also need to minimize administrative overhead. What should you do?
Select an answer first
17foundation · easy
You need to load balance incoming internet traffic to a set of virtual machines. Which Azure load balancer type should you use?
Select an answer first
18application · medium
You have an internal load balancer in a hub virtual network that forwards traffic to a backend pool of VMs in a spoke virtual network. The VMs are healthy and the load balancer rules are configured correctly, but clients in the hub cannot reach the backend. What should you do?
Select an answer first
19foundation · easy
What is the default DNS behavior for a virtual network that has not been configured with a custom DNS server?
Select an answer first
20application · medium
You have a public load balancer that is not distributing traffic to the backend pool. The backend VMs are running and have the correct application installed. You check the load balancer's metrics and see that the 'Health Probe Status' metric shows 0 for all backend instances. What should you check first?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to AZ-104

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “AZ-104” is a trademark of its owner, used for identification only.

Configure Name Resolution and Load Balancing AZ-104 Practice Questions (Page 4)

Questions 16–20

You need to load balance incoming internet traffic to a set of virtual machines. Which Azure load balancer type should you use?

You have an internal load balancer in a hub virtual network that forwards traffic to a backend pool of VMs in a spoke virtual network. The VMs are healthy and the load balancer rules are configured correctly, but clients in the hub cannot reach the backend. What should you do?

What is the default DNS behavior for a virtual network that has not been configured with a custom DNS server?

Keep studying — Implement and manage virtual networking