Certifiable Q&A for December 29, 2000

Welcome to Certifiable, your exam prep headquarters. Here you'll find questions about some of the tricky areas that are fair game for the certification exams. Following the questions, you'll find the correct answers and explanatory text. Beginning the first week in January, we will change the questions weekly.

Lee Madajczyk wrote last week to point out that the new Windows NT 4.0 exam will serve as an elective for the Windows 2000 MCSE certification. I admit that because the news came out right before the column deadline, I had only 30 minutes to read the news, rewrite that section of the column, and return the column to my editors so they could post it by Friday afternoon. I missed the fact that the new exam will fulfill an elective requirement as well as certify the successful applicant as a Microsoft Certified Professional (MCP).

Because many of you will probably still be working with NT 4.0 well into next year, it seems like a good idea to continue to cover some topics on the NT 4.0 core and elective exams. For this column, I chose another three questions from the NT 4.0 TCP/IP exam (Exam 70-059): the first one because its format resembles the exam's scenario questions and the other two because they cover basic TCP/IP topics.

Usually I wish you luck on the exam. This week, however, I wish you luck finding an open seat! See you at the testing center.

Questions (December 29, 2000)
Answers (December 29, 2000)

Questions (December 29, 2000)

Question 1
Scenario: The Feszchak company has a routed internetwork that consists of 20 UNIX machines, 5 NT 4.0 Servers, 50 NT Workstations, and 250 Windows 95 machines. The company has standardized the Microsoft machine names to a length of 10 characters and the UNIX host names to a length of 20 characters. Each NT Server supports one of five subnets. TCP/IP is the only network protocol. Your goal is to enable communications among all of these machines, and you have the following objectives.

Required Objective:

  • Have the Microsoft client machines obtain their IP addresses dynamically from a central source instead of administrators adding static IP addresses.

Optional Objectives:

  • Have all the Microsoft machines use Windows Explorer to map network drives using machine and share names. You want them to be able to map to all the NT servers.
  • Enable the Microsoft machines to FTP to the UNIX machines using host names.

Proposed Solution:
Install the DHCP server service on two of the Microsoft servers. Configure each server with a scope of addresses for each of the five subnets. Ensure that the scopes don't have overlapping addresses. Configure each Microsoft client machine to obtain an IP address from a DHCP server. Configure the routers to forward BOOTP requests. Install WINS on another of the NT servers to facilitate the resolution of IP addresses to the machine names. On the DHCP servers, under global options, configure the servers as H-nodes, and configure the DHCP servers to provide the clients with the WINS server's IP address. Add the host names of the UNIX computers as static mappings in the WINS database.

Which of the following statements is true about the proposed solution:

  1. It achieves the required objective but doesn't achieve either of the optional objectives.
  2. It achieves the required objective and one of the optional objectives.
  3. It achieves the required objective and both of the optional objectives.
  4. It doesn't achieve the required objective.

Question 2

The table below contains the output of the route print command executed on a Windows NT 4.0 server.

=================================================================

Interface List 0x1 ........................... MS TCP Loopback interface 0x2 ...00 10 4b 38 7f ee ...... Ashley Laurent Virtual Private Network 0x3 ...00 60 08 42 28 9c ...... Ashley Laurent Virtual Private Network

============================================================

============================================================

Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 208.53.170.97 208.53.170.98 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 1 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 1 208.53.170.96 255.255.255.224 208.53.170.98 208.53.170.98 1 208.53.170.98 255.255.255.255 127.0.0.1 127.0.0.1 1 208.53.170.255 255.255.255.255 208.53.170.98 208.53.170.98 1 224.0.0.0 224.0.0.0 192.168.0.2 192.168.0.2 1 224.0.0.0 224.0.0.0 208.53.170.98 208.53.170.98 1 255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1

=================================================================

From the information shown, what are the network addresses, and which interface will be used for general broadcasts? (Choose all that apply.)

  1. 192.168.0.0
  2. 192.168.0.2
  3. 208.53.170.96
  4. 208.53.170.97
  5. 208.53.170.98
  6. 127.0.0.0
  7. 127.0.0.1

Question 3

Which of the following strategies enables UNIX clients to resolve Microsoft NetBIOS names to IP addresses?

  1. Have the UNIX clients issue a NetBIOS Name Resolution Query to the WINS server.
  2. Create IN records for all of the UNIX clients on the Microsoft DNS server and have the records reside in the same zone file as the Microsoft hosts.
  3. On the NT Server machine acting as a DNS server, configure the zone to do WINS lookup.
  4. Configure the DHCP server to provide the UNIX clients with the WINS server address.
  5. On the UNIX machine acting as a DNS server, configure the zone to perform WINS lookup.

Answers (December 29, 2000)

Answer to Question 1
The correct answer is B—It achieves the required objective and one of the optional objectives. You can't add static mappings in the WINS database for the UNIX machines because the host names are more than 15 characters long. If the names had been 15 or fewer characters, this solution would have been viable. The Microsoft clients would have queried the WINS database, and WINS would have returned the IP address of the UNIX hosts.

Answer to Question 2
The correct answers are A—192.168.0.0, B—192.168.0.2, and C—208.53.170.96. One of the facts you must memorize is that 192.168.0.0 is a network address reserved for private networks. 208.53.170.96 is a subnet that my ISP provides. The subnet mask, which you can find in the output from the route command, is 255.255.255.224, which means that the rightmost five bits will be 0 for the network address. Because 96 is the only number that has the rightmost five bits set to 0, 208.53.170.96 must be the network address. The general broadcast address is 255.255.255.255; therefore, the interface that this server will use for general broadcasts will be 192.168.0.2. Notice that the route command also shows 208.53.170.255. This entry identifies which interface handles broadcasts for the 208.53.170.0 network.

Answer to Question 3
The correct answer is C—On the NT Server machine acting as a DNS server, configure the zone to do WINS lookup. The UNIX machines will be able to resolve the Microsoft machine names if the DNS zone is configured to query the WINS server for the IP address of the Microsoft machines. Only the Microsoft implementation of DNS provides the capability to do WINS lookups. The WINS server sends the response to the DNS server, not directly to the resolver.

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish