ExamTopics Logo
Mail Us[email protected]
Menu
Microsoft Discussions
exam questions

Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam
Go to Exam

Exam AZ-104 topic 5 question 5 discussion

Actual exam question from Microsoft's AZ-104
Question #: 5
Topic #: 5
[All AZ-104 Questions]

HOTSPOT -
You have Azure virtual machines that run Windows Server 2019 and are configured as shown in the following table.

You create a private Azure DNS zone named adatum.com. You configure the adatum.com zone to allow auto registration from VNET1.
Which A records will be added to the adatum.com zone for each virtual machine? 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:
The virtual machines are registered (added) to the private zone as A records pointing to their private IP addresses.
Reference:
https://docs.microsoft.com/en-us/azure/dns/private-dns-overview https://docs.microsoft.com/en-us/azure/dns/private-dns-scenarios
by ihavespoken at Dec. 3, 2020, 4:23 a.m.

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
Submit Cancel
mlantonis
Highly Voted 3 years, 9 months ago
Correct Answer: The virtual machines are registered (added) to the private zone as A records pointing to their private IP addresses. Since both VM1 & VM2 are in same Vnet1 and the Vnet1 is liked under adatum.com domain (Private DNS Zone->Setting->virtual network links). Reference: https://docs.microsoft.com/en-us/azure/dns/private-dns-overview https://docs.microsoft.com/en-us/azure/dns/private-dns-scenarios
upvoted 129 times
mlantonis
3 years, 9 months ago
Box 1: Private Box 2: Private
upvoted 50 times
...
...
fedztedz
Highly Voted 4 years, 2 months ago
Answer is correct. Private/Private check https://docs.microsoft.com/en-us/azure/dns/private-dns-scenarios#scenario-split-horizon-functionality
upvoted 61 times
[Removed]
3 years, 11 months ago
That's it, good reference
upvoted 6 times
...
...
[Removed]
Most Recent 5 months, 1 week ago
CORRECT
upvoted 2 times
...
SkyZeroZx
1 year, 1 month ago
Correct, OS DNS suffix has no affect on this. Both prv ips will be listed on internal dns zone.
upvoted 1 times
...
stonwall12
1 year, 8 months ago
Private and Private See below: https://docs.microsoft.com/en-us/azure/dns/private-dns-scenarios#scenario-split-horizon-functionality
upvoted 3 times
...
CyberKelev
2 years ago
For VM1, the A record added to the adatum.com zone will be the Private IP address only (10.1.0.4), since the DNS suffix configured in Windows Server is Adatum.com and auto-registration is enabled in VNET1. For VM2, no A record will be added to the adatum.com zone, since the DNS suffix configured in Windows Server is Contoso.com and auto-registration is not enabled in VNET1 for the Contoso.com DNS zone.
upvoted 5 times
c75e123
2 months, 1 week ago
I've noticed that the user CyberKelev tends to post intentionally wrong answers. Please be careful and keep this in mind for future discussions! The answer of this question is Private/Private
upvoted 1 times
...
CyberKelev
2 years ago
Answer is : Private Ip address only and none
upvoted 4 times
...
...
DeBoer
2 years ago
Checked in lab; the DNS records in the private zone are created using the " Virtual network links" to the VNet. The DNS name in the VM itself has no impact on this. So yes, Both "Private" is correct.
upvoted 8 times
...
Max_on_neptune
2 years, 3 months ago
Exam Question on 01DEC2022
upvoted 7 times
arifi
2 years, 2 months ago
did u pass?
upvoted 1 times
...
...
EmnCours
2 years, 6 months ago
Answer is correct. Private/Private
upvoted 1 times
...
vsharma041990
2 years, 7 months ago
The virtual machines are registered (added) to the private zone as A records pointing to their private IP addresses. Since both VM1 & VM2 are in same Vnet1 and the Vnet1 is liked under adatum.com domain (Private DNS Zone->Setting->virtual network links).
upvoted 2 times
...
Lazylinux
2 years, 8 months ago
Yep given answer is correct Private/Private VNET and Private DNS: You can only link VNETs to private DNS zones only and accordingly auto register a VNET only to a private DNS zones. Private DNS zones can be linked with VNETs (not public ones). And VM can auto-register to any private DNS zone linked with the Vnet and with auto-registration option set.
upvoted 5 times
...
benvdw
2 years, 11 months ago
on exam 13/3/2022
upvoted 3 times
...
atilla
2 years, 12 months ago
both private because of same vnet1, you add vnet in private dns zone...
upvoted 1 times
...
khengoolman
3 years, 4 months ago
Passed 11 Oct 2021 with 947. This question appeared, correct Answer is private, private.
upvoted 9 times
...
AubinBakana
3 years, 6 months ago
The question is confusing because VM2 has a different DNS connection suffix. But because they are both part of the VNet1, they'd both be exposed to the internal DNS zone at 168.63.129.16. -Private IP for VM1 -Private IP for VM2
upvoted 4 times
...
ZUMY
4 years ago
01.Private IP Address only 02.Private IP Address only Since both VM1 & VM2 are in same Vnet1 and the Vnet1 is liked under adatum.com domain (Private DNS Zone->Setting->virtual network links)
upvoted 7 times
...
PektoTheGreat
4 years ago
The keyword is "auto-registration from VNET1". VM1 and VM2 belongs to the same VNET. So upon VM1 and VM2 creation they will be auto registered on adatum Private DNS Zone having A Record as their Private IPs. Cheeers yo!
upvoted 9 times
Stunomatic
4 months ago
thank you i was sulking if auto registration is open why we need to add private our-self
upvoted 1 times
...
...
Load full discussion...
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
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago