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.
This week's questions cover topics for Exam 70-217: This week's questions cover topics for Exam 70-216: Implementing and Administering a Microsoft Windows 2000 Network Infrastructure.
Enrious wants to set up a Certification Authority (CA) on a Windows 2000 Server machine on his company's network, which consists of one Win2K domain. He decides that an Enterprise Root CA would best serve his company's needs. Which of the following conditions must Enrious meet before he can install an Enterprise Root CA?
- He must install BIND 8.1.2 or higher on one of the domain controllers (DCs).
- He must have Enterprise Administrator privileges.
- He must install Active Directory (AD).
- He must install a WINS server on a DC in the domain.
- He must install Apache 2.0 on a DC in the domain.
- He must install Win2K DNS.
You work for a company that has a central office and three branch offices. The central office is on Subnet A, and the branch offices are on Subnet B, Subnet C, and Subnet D (i.e., one subnet for each branch office). The subnets have the following addresses:
Subnet B: 220.127.116.11 /24
Subnet C: 18.104.22.168 /24
Subnet D: 22.214.171.124 /24
Subnet A hosts a Microsoft IIS server, which runs the company's intranet. Subnet D has a Host Integration Server that connects to a mainframe at the data center. Each subnet has a file server and print server.
You arrive at work late one morning to find that some users are experiencing connectivity problems. Two users on Subnet C can't ping their local file server or any other servers in the organization, but they can ping each other. On Subnet D, five users can ping each other but can't access to their local file server.
The users experiencing problems on Subnet C have the IP addresses 169.254.0.100 and 169.254.0.101. The users experiencing problems on Subnet D have the IP addresses 169.254.0.160, 169.254.0.161, 169.254.0.162, 169.254.0.163, and 169.254.0.164. How would you resolve these problems?
- Make sure that a WINS server is available for all clients on the segment. Windows 2000 clients rely heavily on NetBIOS resolution, and the lack of an available WINS Server could cause connectivity problems.
- The machines are likely configured with static IP addresses. Change the machines over to DHCP clients.
- Some machines might have received Automatic Private IP Addresses (APIPAs). Determine whether a functioning DHCP server is available for the segments that include those machines.
- The switch that the computers are connected to has broken. Replace the switch and reconnect each system to the new switch.
You have installed a new primary Windows 2000 DNS server on your company's network. You set up this DNS server, which has the IP address 126.96.36.199, to host the new Internet domain truthaddict.com.au. You have the following 10 hostnames listed in your database:
dns.truthaddict.com.au IN A 188.8.131.52
mail.truthaddict.com.au IN A 184.108.40.206
dc1.truthaddict.com.au IN A 220.127.116.11
dc2.truthaddict.com.au IN A 18.104.22.168
dc3.truthaddict.com.au IN A 22.214.171.124
dc4.truthaddict.com.au IN A 126.96.36.199
intranet.truthaddict.com.au IN A 188.8.131.52
wkstn1.truthaddict.com.au IN A 184.108.40.206
wkstn2.truthaddict.com.au IN A 220.127.116.11
You have set wkstn1 to use your company's DNS servers to resolve DNS requests. The network is small enough that a hosts file services it adequately. You don't foresee any significant expansion, but you want to move the company to a full Active Directory (AD) environment. This move, of course, requires Win2K DNS (although later versions of BIND that report SRV records would also work)—hence the new Win2K DNS server.
Before you install a secondary DNS server, you want to make sure that everything works correctly on the existing DNS server. You open a command prompt on wrkstn1, which is a Win2K Professional machine, and type
The queries for intranet.truthaddict.com.au and www.certtutor.net come back with the expected IP addresses. However, when you query the IP address 18.104.22.168, you receive an error. What is the most likely cause of this problem?
- Nslookup defaults to one query. When you perform the second and third lookups, you use your ISP's DNS servers, which don't contain the necessary records.
- The forward lookup zone isn't correctly configured for the new DNS server.
- The reverse lookup zone isn't correctly configured for the new DNS server.
- The addresses of the root servers don't include the address of the in-arpa root server for in-arpa.203.250.128. You should include this address in the DNS configuration file, restart the DNS service, and flush the resolver cache.
Answer to Question 1
The correct answers are B—He must have Enterprise Administrator privileges; C—He must install Active Directory (AD); and F—He must install Win2K DNS. BIND is another implementation of DNS that runs on Win2K and also on UNIX and Linux. WINS is irrelevant to installing an Enterprise Root CA. Apache 2.0 is an open source Web Server that can run on Win2K, but it's not required for an Enterprise Root CA to function.
Answer to Question 2
The correct answer is C—Some machines might have received Automatic Private IP Addresses (APIPAs). Determine whether a functioning DHCP server is available for the segments that include those machines. APIPAs are addresses that Windows sets when no DHCP server is available. For some reason, these machines aren't communicating properly with the DHCP server.
Answer to Question 3
The correct answer is C—The reverse lookup zone isn't correctly configured for the new DNS server. When an IP address doesn't resolve to a Fully Qualified Domain Name (FQDN) on your local DNS server, the reverse lookup zone is most likely not configured correctly. You don't need a reverse lookup zone to be properly configured for Active Directory to function but you will need it configured properly if you would like to resolve IP addresses to FQDNs.