Your network contains multiple subnets.
On one of the subnets, you deploy a server named Server1 that runs Windows Server 2012 R2.
You install the DNS Server server role on Server1, and then you create a standard primary zone
named contoso.com.
You need to ensure that client computers can resolve single-label names to IP addresses.
What should you do first?
A.
Create a reverse lookup zone.
B.
Convert the contoso.com zone to an Active Directory-integrated zone.
C.
Configure dynamic updates for contoso.com.
D.
Create a GlobalNames zone.
Explanation:
Although a GlobalNames zone is required in order to resolve single-label names, GNZs must be ADintegrated.
Since this is a standard primary zone (as opposed to an ADDS primary zone), we must first integrate
the zone into Active Directory.
References:
Exam Ref: 70-410: Installing and Configuring Windows Server 2012 R2, Chapter4: Deploying and
configuring core network services, Objective 4.3: Deploy and Configure the DNS service, p.233
http://technet.microsoft.com/en-us/library/cc731744.aspx
D
Answer is D
Yep
why? can you explain please?
50 questions in total.
About 8 new questions, around 4 new questions on Access-Based and SMB-Share and Synchronizing Work Folders With AD Users.
And, 4 questions about RODC, 2 questions about Azure and NO IPv6 questions.
All questions now are available in PassLeader 70-410 Exam Dumps (Both VCE and PDF Files Are Available Here: https://tr.im/758Ht). All Answers Have Been Corrected By PassLeader.
Good Luck!
I found this answer somewhere else
D. use GlobalNames zones in Windows Server 2008 to take advantage of single-label names Providing Single-Label DNS Name Resolution:
While Domain Name System (DNS) is the predominant name-resolution technology in TCP/IP networks, Windows Internet Name Service (WINS) is deployed in many networks as an alternative name-resolution protocol.
GlobalNames Zone (GNZ) feature: The GNZ feature is designed to enable DNS resolution of these single-label, static, global names. You can deploy a GNZ in a single forest or across multiple forests.
GNZ is intended to aid the retirement of WINS. It is not a replacement for WINS. GNZ is not intended to support the single-label name resolution of records that are registered dynamically and therefore not managed by IT administrators. GNZ does make it possible for you to provide single-label name resolution of a fixed set of host computers whose names are guaranteed to be both global and unique.
http://technet.microsoft.com/en-us/library/cc731744.aspx
http://technet.microsoft.com/en-us/library/cc816610(v=ws.10).aspx
READ THE QUESTION!!!
What should you do first?
Step 1: Create the GlobalNames zone
The first step in deploying a GlobalNames zone is to create the zone on a DNS server that is a domain controller running Windows Server 2008. The GlobalNames zone is not a special zone type; rather, it is simply an AD DS-integrated forward lookup zone that is called GlobalNames. For information about creating a primary forward lookup zone, see Add a Forward Lookup Zone.
http://technet.microsoft.com/en-us/library/cc731744.aspx
B is correct.
I agree with Special K. Yes the overall solution for single-label name resolution is to create a GlobalName zone. BUT, the FIRST STEP is the zone must be Active Directory Integrated.
If you go straight to answer D and “Create a GlobalName zone” – as part of the wizard you can make the zone Active Directory Integrated, HOWEVER – you are then creating a BRAND NEW ZONE. Nowhere does the question ask you to create a new zone. It implies you need to use the existing CONSTOSO.COM zone – in which case the zone must be AD integrated first.
Special K is correct. Answer is B.
B
C
F
Very funny.
D – official explanation by MS and users on this link (v.1):
http://www.aiotestking.com/microsoft/you-need-to-ensure-that-client-computers-can-resolve-single-label-names-to-ip-addresses/