exam questions

Exam AZ-305 All Questions

View all questions & answers for the AZ-305 exam

Exam AZ-305 topic 4 question 36 discussion

Actual exam question from Microsoft's AZ-305
Question #: 36
Topic #: 4
[All AZ-305 Questions]

HOTSPOT -
You have the Azure resources shown in the following table.

You need to design a solution that provides on-premises network connectivity to SQLDB1 through PE1.
How should you configure name resolution? To answer select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:

Show Suggested Answer Hide Answer
Suggested Answer:
Box 1:In VNET1, configure a custom DNS server set to the Azure provided DNS at 168.63.129.16
Virtual network workloads without custom DNS server.
This configuration is appropriate for virtual network workloads without a custom DNS server. In this scenario, the client queries for the private endpoint IP address to the Azure-provided DNS service 168.63.129.16. Azure DNS will be responsible for DNS resolution of the private DNS zones.
The following screenshot illustrates the DNS resolution sequence from virtual network workloads using the private DNS zone:

Box 2: Forward contoso.com to VM1
Forward to the DNS server VM1.
Note: You can use the following options to configure your DNS settings for private endpoints:
* Use the host file (only recommended for testing). You can use the host file on a virtual machine to override the DNS.
* Use a private DNS zone. You can use private DNS zones to override the DNS resolution for a private endpoint. A private DNS zone can be linked to your virtual network to resolve specific domains.
* Use your DNS forwarder (optional). You can use your DNS forwarder to override the DNS resolution for a private link resource. Create a DNS forwarding rule to use a private DNS zone on your DNS server hosted in a virtual network.
Reference:
https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-dns

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Babonamaki
Highly Voted 2 years, 2 months ago
Box 1 is wrong, VNET default configuration is to use azure DNS. The correct answer for box 1 should be "configure vm1 to forward contoso.com to the azure provided dns at 168.63.129.16" to convert VM1 to a DNS forwarder.
upvoted 99 times
steel72
1 year, 8 months ago
Agreed, I have a production deployment configured like this.
upvoted 7 times
...
...
[Removed]
Highly Voted 1 year, 12 months ago
For anyone else struggling, I found this helpful: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/networking/azure-dns-private-resolver
upvoted 24 times
...
SeMo0o0o0o
Most Recent 3 weeks, 1 day ago
WRONG 1. Configure VM1 to forward contoso.com to the Azure-provided DNS at 168.63.129.16 2. Forward contoso.com to VM1
upvoted 2 times
...
Len83
3 months, 4 weeks ago
This question appeared in the exam, August 2024. For Box 1 I gave the answer "configure vm1 to forward contoso.com to the azure provided dns at 168.63.129.16". For Box 2 I gave "Forward contoso.com to VM1". I scored 870
upvoted 4 times
...
23169fd
5 months, 2 weeks ago
Azure Configuration Option: Configure VM1 to forward contoso.com to the Azure-provided DNS at 168.63.129.16 Reasoning: This setup allows the DNS server on VM1 to forward DNS queries for the contoso.com domain to the Azure-provided DNS. The Azure DNS can resolve the private endpoint (PE1) to its private IP address. On-premises DNS Configuration Option: Forward contoso.com to VM1 Reasoning: By configuring the on-premises DNS to forward requests for contoso.com to VM1, DNS queries for this domain will be directed to the DNS server on VM1, which will then forward them to the Azure-provided DNS.
upvoted 4 times
...
Lazylinux
7 months, 2 weeks ago
Box 1 is wrong but Box 2 is correct and answer as per below Box1. configure vm1 to forward contoso.com to the azure provided dns at 168.63.129.16 Box2. Forward contoso.com to VM1
upvoted 2 times
...
Cg007
8 months ago
Azure configuration: In VNet1, configure a custom DNS server set to the Azure provided DNS at 168.63.129.16: This configuration ensures that all the resources within VNet1, which includes VM1 (configured as a DNS server) and PE1 (Private Endpoint), can resolve names using the Azure-provided DNS which has knowledge of the private endpoints. On-premises DNS configuration: Forward contoso.com to VM1: Since VM1 is configured as a DNS server and it is within VNet1 that has a private DNS zone for contoso.com, forwarding DNS requests for contoso.com to VM1 will allow on-premises systems to resolve the names to the private IP addresses provided by PE1 for SQLDB1. This assumes that VM1 has the necessary DNS forwarders or conditional forwarders set up to resolve queries for contoso.com using the private DNS zone information.
upvoted 1 times
...
177c705
9 months, 1 week ago
1. configure vm1 to forward contoso.com to the azure provided dns at 168.63.129.16 2. Forward contoso.com to VM1
upvoted 1 times
...
Risto83
9 months, 2 weeks ago
nothing in the question says that VM1 is connected to VNET1
upvoted 1 times
...
din4venti
1 year, 5 months ago
Azure configuration: In VNet1, configure a custom DNS server set to Azure provided DNS at 168.63.129.16 On-premises DNS configuration: Forward contoso.com to VM1 Here's the flow 1. on-premise client machine queries for SQLDB1 2. on-premise DNS forward to VM1 3. VM1 query for SQLDB1 to public DNS 4. VM1 recieves CNAME for SQLDB1 5. VM1 query for CNAME of SQLDB1, which resided on Private DNS zone (In order to query Private DNS zone, you need to forward to Azure provided internal DNS) 6. VM1 receives A record from Private DNS zone 7. VM1 returns to on-premise client https://learn.microsoft.com/en-us/azure/architecture/example-scenario/networking/azure-dns-private-resolver#use-a-dns-forwarder-vm
upvoted 8 times
...
VBK8579
1 year, 10 months ago
Azure configuration: c. In VNet1, configure a custom DNS server set to the Azure provided DNS at 168.63.129.16 On-premises DNS configuration: a. Forward contoso.com to VM1
upvoted 2 times
...
OPT_001122
1 year, 10 months ago
1. configure vm1 to forward contoso.com to the azure provided dns at 168.63.129.16 2. Forward contoso.com to VM1
upvoted 13 times
...
vicks1x
2 years ago
Carefully look at the Green arrows in the diagram. Its "configure vm1 to forward contoso.com to the azure provided dns at 168.63.129.16"
upvoted 2 times
...
MountainW
2 years, 1 month ago
Babonamaki is right. The correct answer for box 1 should be "configure vm1 to forward contoso.com to the azure provided dns at 168.63.129.16" to convert VM1 to a DNS forwarder. That's what I am using in our production environment!
upvoted 8 times
...
scottims
2 years, 2 months ago
I think it should be configure VM1 to forward Contoso.com to Public DNS as that is where the CNAME record exists on premises should forward to VM1 since VM1 has the A record for PE1
upvoted 2 times
scottims
2 years, 2 months ago
Update after looking at the table again, the public DNS zone is in Azure so VM1 should forward to the Azure-provided DNS
upvoted 2 times
Paimon
2 years ago
Public DNS does not come into play because of the private endpoint.
upvoted 1 times
...
...
...
codefries
2 years, 2 months ago
Coz they did NOT say VM1(DNS) is in VNET1
upvoted 1 times
Guest
1 year, 11 months ago
That does not really matter. A DNS server uses it's internal forwarders, not the network settings to resolve DNS queries
upvoted 1 times
...
...
examerrr
2 years, 2 months ago
Interestingly done this config at work and we use the AFWs as a DNS proxies and conditionally forward DNS requests from on-prem for stuff like Keyvault and Servicebus to the AFWs which then return the privatelink addresses.
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...