Question 5) Managing and Maintaining Windows

Posted on
Share on Google+Share on LinkedInShare on FacebookShare on RedditTweet about this on TwitterEmail this to someone

Objective: Implementing, Managing, and Maintaining Name Resolution
SubObjective : Manage DNS
Single Answer Multiple Choice

You are your company’s network administrator. Your network consists of four subnets contained in a Windows 2003 domain named abccorp.com. You have four file servers located on your network. Each of these servers is configured to maintain exactly the same content as the other file servers by implementing file replication. You have four DNS servers on your network, one primary and three secondary servers, each on a separate subnet. The primary DNS server is named DNS1. The secondary DNS servers are named 2DNS2, 2DNS3, and 2DNS4.

 

You want to configure DNS1 to allow users to use the host name to connect to the file server on the same subnet as the client machine they are using. The host name that all users type will be identical regardless of the subnet on which they are located. The host name used for these four file servers is filesrv.abccorp.com.

 

What should you do?

 

 

  1. On DNS1, create four A records that map a different host name to the IP address of the file server on each subnet.
  2. On DNS1, create four A records that map the filesrv.abccorp.com name to the IP address of the file server on each subnet.
  3. On DNS1, create one A record that maps the filesrv.abccorp.com name to the IP address of the file server on that specific subnet and create three CNAME records for the remaining three file servers on the other subnets.
  4. On DNS1, create one A record that maps the filesrv.abccorp.com name to the IP address of the file server that is on the same subnet as DNS1. On 2DNS2, 2DNS3, and 2DNS4, edit the zone file for the domain on each server to map the filesrv.abccorp.com name to the file server contained on that specific subnet.

 

 

 


Answer:
B. On DNS1, create four A records that map the filesrv.abccorp.com name to the IP address of the file server on each subnet.

Tutorial:
You should create four A records on DNS1 that map the filesrv.abccorp.com name to the IP address of the file server on each subnet. By mapping the same host name to four different IP addresses, you enable the use of subnet prioritization. If a resolver receives multiple host resource records from a DNS server, the resolver will order the records based on the proximity to the computer where the query originated. In a standard DNS zone, all changes are made on the Primary DNS server, and then transferred to the secondary DNS servers.

You should not create four A records on DNS1 that map a different host name to the IP address of the file server on each subnet. This would not allow the host names for the file servers to be identical.

You should not create one A record on DNS1 that maps the filesrv.abccorp.com name to the IP address of the file server on that specific subnet and create three CNAME records for the remaining three file servers on the other subnets. CNAME records are used to register aliases for the same server. These records allow you to use more than one name to point to a single host, making it easy to do such things as host both an FTP server and a Web server on the same computer.

You should not create one A record on DNS1 that maps the filesrv.abccorp.com name to the IP address of the file server that is on the same subnet as DNS1 and edit the zone file for the domain on 2DNS2, 2DNS3, and 2DNS4 to map the filesrv.abccorp.com name to the file server contained on that specific subnet. Secondary DNS servers contain a read-only copy of the DNS zone data. You cannot edit the zone data from a secondary DNS server. Secondary DNS servers will have the DNS zone data replicated from the primary DNS server.

Reference:
1. Windows Server 2003 Help and Support Center – Search
– Prioritizing local subnets

 

These questions are derived from the Self-Test Software Practice Test for 70-292 – Managing and Maintaining a Microsoft Windows Server 2003 Environment for an MCSA Certified on Windows 2000.

Share on Google+Share on LinkedInShare on FacebookShare on RedditTweet about this on TwitterEmail this to someone
cmadmin

ABOUT THE AUTHOR

Posted in Archive|

Comment:

Leave a comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>