MCSE 70-291 Exam Quiz Test 1

To set up DHCP, DNS, and WINS on a Windows system, you should install the "Networking Services" component. This component includes the necessary tools and services for managing and configuring network-related functions such as DHCP (Dynamic Host Configuration Protocol), DNS (Domain Name System), and WINS (Windows Internet Name Service). By installing the Networking Services component, you can easily set up and manage these essential networking services on your Windows system.

The IP address 169.254.130.13 falls within the range of addresses reserved for Automatic Private IP Addressing (APIPA). APIPA is used when a computer is unable to obtain an IP address from a DHCP server. Therefore, it is most likely that there is no DHCP server on the network, leading to the computer using an automatically assigned IP address.

The resource record used to resolve domain names specified in e-mail addresses to the IP address of the mail server associated with the domain is the MX record. The MX record stands for Mail Exchanger record and it specifies the mail server responsible for accepting incoming e-mail messages on behalf of a domain.

File sharing does not rely on a Public Key Infrastructure. Unlike IPSec and SSL, which both use public key cryptography for secure communication, file sharing typically uses other methods such as access control lists, passwords, or encryption specific to the file sharing application. Public Key Infrastructure is primarily used for authentication, encryption, and digital signatures, which are not essential for file sharing.

The Client for Microsoft Networks is automatically assigned to connections. This component allows the computer to connect to and communicate with Microsoft networks. It provides the necessary protocols and services for network communication, such as file and printer sharing. This component is essential for accessing resources on a Microsoft network and is automatically included in the network configuration.

A requirement for networking on a Windows Server 2003 network is a network protocol. Network protocols are essential for communication between devices on a network. They define the rules and procedures for transmitting data across the network. Without a network protocol, devices would not be able to communicate with each other effectively. DHCP and WINS are also important components of a network, but they are not specifically mentioned as requirements for networking on a Windows Server 2003 network in the given options.

The given binary address can be converted to dotted-decimal notation by dividing it into four octets. The first octet is 11001100, which is equivalent to 204 in decimal. The second octet is 00001010, which is equivalent to 10 in decimal. The third octet is 11001000, which is equivalent to 200 in decimal. The fourth octet is 00000100, which is equivalent to 4 in decimal. Therefore, the dotted-decimal notation equivalent of the binary address is 204.10.200.4.

Configuring NS2 and NS3 to use NS1 as a forwarder would require the least amount of administrative effort to enable network users to connect to Internet host names. By setting NS1 as a forwarder, NS2 and NS3 will forward DNS queries for external host names to NS1, which is directly connected to the Internet. This allows NS1 to resolve the queries and provide the necessary information to NS2 and NS3, allowing network users to connect to Internet destinations using host names. Disabling recursion on NS2 and NS3, enabling netmask ordering on NS1, or disabling round robin on NS1 would not address the issue of network users being unable to connect to Internet host names.

Workgroup security does not rely on certificates and public key cryptography. Workgroup security refers to the security measures implemented within a small group or network of computers that share resources and information. It typically involves the use of passwords, access controls, and user permissions to protect the network and its resources. Unlike SSL, EFS, and IPSec, workgroup security does not involve the use of certificates and public key cryptography for authentication and encryption purposes.

The Routing and Remote Access console allows for the configuration of various features related to network connectivity, such as dial-up networking, packet filtering, and Internet Connection Sharing. However, it does not provide configuration options for Active Directory, which is a separate service used for managing and organizing network resources, such as users, groups, and computers. Therefore, the correct answer is Active Directory.

When the host determines that the destination network ID of a packet is the same as its own network ID, it broadcasts an ARP request to determine the Media Access Control (MAC) address of the destination host. This is done to ensure that the packet is delivered to the correct host on the local network. Once the MAC address is determined, the host then transmits the packet on the local network using that MAC address. This allows for proper delivery of the packet within the local network.

NetBIOS is a protocol that provides names and name resolution for workgroups in Windows. It allows computers on a local area network (LAN) to communicate with each other using names instead of IP addresses. NetBIOS enables the identification and location of resources, such as shared folders and printers, within a workgroup. It also facilitates the establishment of connections and the sharing of data between computers in a Windows network. NetBIOS is commonly used in older versions of Windows, but newer versions have transitioned to more modern protocols like DNS.

UDP (User Datagram Protocol) is a transport-layer protocol. It is a connectionless protocol that provides a simple and unreliable method of delivering datagrams from one host to another. UDP is often used for applications that require fast transmission and minimal overhead, such as real-time streaming or online gaming. Unlike TCP (Transmission Control Protocol), UDP does not provide error-checking, flow control, or retransmission of lost packets. Therefore, it is considered less reliable but faster than TCP.

Running Ipconfig with the /all switch will provide detailed information about the network configuration of the computer, including the IP address, subnet mask, default gateway, and DNS servers. By examining this information, you can verify if the computer has the correct IP address and subnet mask for the local subnet. If there is a misconfiguration, you can then troubleshoot and correct it accordingly.

In Windows Server 2003, local area connections are automatically configured. This means that when a network adapter is installed, Windows Server 2003 will automatically detect and configure the local area connection settings, such as IP address, subnet mask, and default gateway. This allows for easy setup and connection to a local network. Dial-up networking and routing tables, on the other hand, are not automatically configured and require manual configuration by the administrator.

The resolver first checks its local cache to see if it already has the IP address associated with the DNS name. If the information is found in the cache, it can be quickly retrieved without needing to perform any further steps. This helps to improve the efficiency of the DNS resolution process by avoiding unnecessary network traffic.

The subnet mask is used by the local host to determine the destination network ID of a particular packet. The subnet mask is a binary pattern that is applied to the IP address to determine the network portion of the address. By comparing the IP address with the subnet mask, the local host can determine which network the packet belongs to. This allows the local host to properly route the packet to the correct destination.

Another manually configured address is taking precedence over the alternate address.

The given answer, 131.107.10.0/23, is correct because it represents a subnet mask of 23 bits, which allows for a larger number of hosts to be accommodated in the network. By using this subnet mask, both the network addresses 131.107.10.0 and 131.107.11.0 can be combined into a single network, as it provides enough address space for the 400 hosts required.

The next step should be to check for errors in the ARP cache. The ARP cache is used to map IP addresses to MAC addresses on a local network. If there are errors in the ARP cache, it could be preventing the computer from being pinged by other computers on the local subnet. By checking the ARP cache, any incorrect or outdated entries can be identified and cleared, allowing for successful communication between the computers.

A stub zone is a copy of a zone that contains only the resource records necessary to identify the authoritative DNS servers for that zone. It does not store the entire zone's information. While stub zones provide benefits such as improving name resolution performance, keeping foreign zone information current, and simplifying DNS administration, they do not directly increase fault tolerance for DNS servers. Fault tolerance refers to the ability of a system to continue operating even in the event of a failure. Stub zones do not provide redundancy or backup for DNS servers in case of failure, so they do not increase fault tolerance.

To capture frames from a network adapter on a remote computer, the Network Monitor Driver needs to be installed on both the remote computer and the local computer. The full version of Network Monitor only needs to be installed on the local computer for analysis and viewing purposes. Therefore, the correct answer is "Install the full version of Network Monitor on the remote computer" as it is not a requirement to capture frames from a remote computer.

The correct answer is "host1_local". NetBIOS computer names can consist of up to 15 characters and can include letters, numbers, and underscores. The name "host1_local" meets these criteria and is therefore a legal NetBIOS computer name.

not-available-via-ai

To interoperate with a NetWare network containing servers running both NetWare 3.11 and NetWare 4.1, the NWLink protocol should be configured to allow both 802.2 and 802.3 frame types in the Registry. This will ensure compatibility with both versions of NetWare, allowing the Windows Server 2003 computer to communicate effectively with the NetWare network.

The next step should be to check for hardware errors on C1. Since both computers can ping themselves and C2 can ping other computers, it suggests that there may be an issue with the network adapter or other hardware on C1 that is preventing it from successfully pinging C2. Checking for hardware errors on C1 will help identify and resolve any hardware-related issues that may be causing the problem.

PathPing is a tool that combines the functionality of both Ping and Traceroute. It provides information about the latency and packet loss at each hop along the network path. By using PathPing, you can determine whether particular routers are causing the delay by analyzing the round-trip time and packet loss statistics.

The server will be unable to resolve Internet names because it is not able to cache names.

The network interface layer is the only layer of the TCP/IP reference model that does not contain any TCP/IP protocols. This layer is responsible for the physical transmission of data over the network and handles tasks such as encoding and decoding data into bits. It interacts directly with the hardware and network devices, such as network interface cards (NICs), to send and receive data. Unlike the other layers, which have specific protocols assigned to them, the network interface layer does not have any TCP/IP protocols associated with it.

Adding an NS (Name Server) resource record to the treyresearch.net zone pointing to the computer ns5.treyresearch.net will enable name resolution for clients at the Syracuse branch. This record specifies that ns5.treyresearch.net is authoritative for the treyresearch.net domain and is responsible for resolving names within that domain. By adding this record, clients at the Syracuse branch will be able to query ns5.treyresearch.net for name resolution.

The correct answer is 11001111 11010001 01000100 01100100. This is the binary equivalent of the dotted-decimal address 207.209.68.100.

Increasing the refresh interval on the primary DNS server would help resolve the problem with the least effort. This would reduce the frequency at which zone transfers are initiated, giving more time for the transfers to complete before new ones are started. By increasing the refresh interval, the primary DNS server will not send zone updates as frequently, reducing the network bandwidth usage and alleviating the saturation issue. This solution does not require any additional hardware or configuration changes, making it the least effort option.

The most likely effect of adjusting the default TTL value to 5 minutes is that DNS clients will have to query the server more frequently to resolve names for which the server is authoritative. The TTL (Time to Live) value determines how long a DNS record can be cached before it expires. By setting it to 5 minutes, the DNS clients will need to query the server every 5 minutes to get the most up-to-date information, increasing the frequency of queries.

Clearing the BIND Secondaries check box on Server1 will decrease the network burden of zone transfers between the primary and secondary servers. By clearing this check box, Server1 will not send zone transfer requests to any secondary servers, reducing the amount of traffic generated during zone transfers. This will help alleviate the strain on network resources.

The correct answer is "DC=ForestDnsZones,DC=treyresearch,DC=net". This is the partition in Replication Monitor that should be used to force replication of the zone data for the syr.treyresearch.net domain. The reason for this is that the syr.treyresearch.net domain is an Active Directory-integrated zone, and the replication scope for the zone has been set to All DNS Servers in The Active Directory Forest. Therefore, the replication needs to occur within the ForestDnsZones partition, which is specific to the forest, rather than the DomainDnsZones partition, which is specific to the domain.

To view a list of all SRV resource records in a domain, you should execute the command "ls -t srv" at the Nslookup prompt. This command sets the query type to SRV (service) and lists all the SRV resource records in the domain.

The root domain of a namespace is the highest level domain in the hierarchy. In this case, the FQDN (Fully Qualified Domain Name) is first.domain1.local. The root domain is the part that comes before the first dot. In this case, there is no text before the first dot, so the root domain is an empty string.

Storing DNS zones in the Active Directory database does not provide the benefit of less frequent transfers. This means that the DNS zones would still need to be transferred regularly between DNS servers, regardless of whether they are stored in the Active Directory database or not.

The correct answer is to configure the DNS server in Rochester to host a standard primary zone for the proseware.com domain. Then, configure the DNS servers in both Buffalo and Syracuse to each host a standard primary zone for a subdomain of proseware.com. Finally, create a delegation from the DNS server in Rochester to each of these subdomains. This solution allows the central office in Rochester to maintain control over the main domain while delegating responsibility for the subdomains to the branch offices in Buffalo and Syracuse.

DNS1 hosts a zone named ".". This means that DNS1 is configured to be authoritative for the root zone, which is not allowed. The root zone should only be hosted by the root servers on the Internet. This misconfiguration is causing the failure of the recursive test on DNS1.

NetBT (NetBIOS over TCP/IP) is the session-layer interface used to connect Client for Microsoft Networks to the TCP/IP protocol. NetBT allows the client to communicate with other devices on the network using the NetBIOS (Network Basic Input/Output System) protocol over TCP/IP. This enables the client to access shared resources, such as files and printers, on other devices in the network that also support NetBIOS. The NetBT interface handles the session establishment, data transfer, and session termination between the client and the TCP/IP protocol.

TCP does not function at the internet layer. The internet layer is responsible for routing packets across different networks, while TCP operates at the transport layer and is responsible for establishing and maintaining reliable connections between devices. TCP relies on the services provided by the internet layer, such as IP, to transport its data packets. Therefore, TCP is not a protocol that functions directly at the internet layer.

NetBIOS and DNS are the services that connect to UDP ports. NetBIOS (Network Basic Input/Output System) is a protocol that allows applications on different computers to communicate over a local area network (LAN). It uses UDP for its transport layer protocol. DNS (Domain Name System) is responsible for translating domain names into IP addresses. It also uses UDP for communication between DNS servers and clients. Ethernet and Telnet are not services that directly connect to UDP ports. Ethernet is a networking technology, while Telnet is a protocol that allows remote login to a computer.

To capture and analyze XTXA traffic in Network Monitor, you need to perform two steps. First, you should copy the Xtxa.dll file to the \System32\Netmon\Parsers folder. This will enable Network Monitor to parse the proprietary protocol used by the application. Second, you need to add an entry for the Xtxa.dll file to the \System32\Netmon\Parser.ini file. This will ensure that Network Monitor recognizes and includes the XTXA protocol in its analysis. By completing these two steps, you will be able to troubleshoot and solve problems related to the application's network traffic.

Configuring a single Active Directory domain for all four locations and a single Active Directory-integrated DNS zone that replicates through the entire domain is the best option to meet the goals of implementing a single Active Directory forest and minimizing response times for users. This configuration ensures that all domain controllers in each location have a copy of the DNS zone, allowing for faster access to resources anywhere on the network. Additionally, having a single domain simplifies management and reduces administrative overhead.

When a DNS client first submits a recursive query to a local DNS server to resolve an Internet name for which the server is not authoritative, the first step that takes place is the DNS server contacts root servers configured in the Cache.dns file. This is because the local DNS server does not have the requested information in its cache, so it needs to reach out to the root servers to start the process of resolving the name.

The correct answer is to execute the Ipconfig /registerdns command and to shut down and restart c1.lucernepublishing.com. By executing the Ipconfig /registerdns command, the computer will attempt to register its DNS records with the DNS server. Shutting down and restarting the computer will also trigger a DNS registration process. These actions will allow c1.lucernepublishing.com to reregister itself in DNS and be contacted by name instead of just by IP address.

The first event, "The Internet root servers have changed," could serve as a legitimate reason to modify the default root hints. If the root servers have changed, the DNS server needs to be updated with the new root hints information to ensure proper resolution of domain names.

The fourth event, "Your server is not used to resolve Internet names," could also be a reason to modify the default root hints. If the server is not being used to resolve internet names, it may not need the default root hints. Modifying the root hints in this case could help optimize the DNS server's performance and resources.

The command "ls -d contoso.com" should be executed at the Nslookup prompt to view all contents of the zone contoso.com.

The first DHCP server on a network can be any server that meets the requirements for hosting a DHCP server. In this case, the Windows Server 2003 domain controller in an Active Directory network, the Windows 2000 Server workgroup server in a network with no domains, and the Windows 2000 Server member server in an Active Directory network all meet the requirements and can be the first DHCP server on the network.