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 AddDnsServerSecondaryZonecmdlet 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.
Answer doesn’t match Explanation.
Can anyone explain this?
Since the zone is Active Directory integrated, the server must be a Domain Controller, in order to store the zone in the AD. Server1 isn’t a DC, so, the primary zone will remain on DC1. Despite that Secondary Zone is a read-only zone, it grants that the DNS Server respond Authoritatively for that zone, so it secondary zone must be configured on server1.
Cheers.
Theles.