DRAG DROP
Your network contains an Active Directory domain named contoso.com. The domain
contains a domain controller named DC1 that has the DNS Server server role installed. DC1
hosts an Active Directory-integrated zone for the domain. The domain contains a member
server named Server1.
You install the DNS Server server role on Server1.
You need to ensure that Server1 can respond authoritatively to queries for the existing
contoso.com namespace.
Which cmdlets should you run on each server? (To answer, drag the appropriate cmdlets to
the correct servers. Each cmdlet may be used once, more than once, or not at all. You may
need to drag the split bar between panes or scroll to view content.)
Answer: 
Explanation:
The Set-DnsServerPrimaryZonecmdlet changes settings for an existing Domain Name
System (DNS) primary zone. You can change values that are relevant for either Active
Directory-integrated zones or file-backed zones. This cmdlet should be run on Server1 to
make it authoritative. The Add-DnsServerSecondaryZonecmdlet adds a specified secondary
zone on a Domain Name System (DNS) server. You can create either a forward lookup zone
or a reverse lookup zone. This cmdlet should be run on DC1.
The explanation doesn’t match the answer. If I “add a specified secondary zone on a DNS server” and per the scenario, Server 1 is the DNS server, then “Add-DnsServerSecondaryZone” cmdlet goes on Server1, right? But the explanation says it goes on DC1…
I guess the answer is right but the explanation is wrong.
0
0
Seems like it cause on DC1 using Set-DnsserverPrimaryZone with -secondaryservers parameter you allow the server1 to work as authoritative DNS server. And on server1 you run Add-DnsserverSecondaryZone with -master parameter to confirm this. This is a Zone Transfer matter – https://technet.microsoft.com/en-us/library/cc781340(v=ws.10).aspx although it might seem as delegation at first, but for delegation there are no viable cmdlets.
0
0