9.2.8 Server Pro Practice Questions

You are the systems administrator for WestSim Corporation. You have been assigned to set up a new branch office in Tulsa. The branch will be represented by a single domain. You install a single DNS server called TulsaDNS and configure a primary zone for the branch office domain. You test name resolution and find that hosts can only resolve names for hosts within the domain. You need to enable clients in the Tulsa location to resolve names for hosts in other domains within your private network. You would like to minimize traffic across the WAN link between the sites. What should you do? Configure TulsaDNS as a caching-only server. Configure network clients to use a DNS server located on the rest of the network. Configure TulsaDNS to use forwarders. Configure TulsaDNS with root hints.

Configure TulsaDNS to use forwarders. EXPLANATION Configure TulsaDNS to use forwarders. When TulsaDNS receives a request for a host name on another domain, it forwards the request to another DNS server. The TulsaDNS server submits a recursive request so that only the single request and response travels across the WAN link. Configuring TulsaDNS with root hints pointing to root servers on the rest of the network would enable name resolution. However, TulsaDNS would refer to the root zone servers and perform iterative queries to resolve all host names outside of its own domain. This would result in multiple requests crossing the WAN link to resolve a single host name. Configuring TulsaDNS as a caching-only server would increase WAN link traffic, as the domain for the Tulsa location would need to be placed on the other side of the WAN link. Name resolution requests for hosts within the domain in Tulsa would need to cross the WAN link once for each host until the server cached the host names of all other hosts. REFERENCES LabSim for Server Pro 2016, Section 9.2.

Your Active Directory network uses the internal DNS namespace private.westsim.com. Several other Active Directory domains also exist, which are children to the private.westsim.com domain. On the Internet, your company uses westsim.com for its public domain name. Your company manages its own DNS servers that are authoritative for the westsim.com zone. The private.westsim.com zone has been delegated to your company's Active Directory domain controllers, which are also DNS servers. Computers that are members of the private.westsim.com domain and all child domains must be able to resolve DNS names of Internet resources. However, to help secure your network, DNS queries for resources in the private.westsim.com domain and all child domains must never be sent to Internet DNS servers. Queries for Internet names must go first to your public DNS server that is authoritative for the westsim.com domain. You need to configure your company's DNS servers to meet these requirements. What should you do? (Choose two. Each correct choice is part of the solution.) Configure root hints to Internet DNS servers on all DNS servers that are authoritative for the private.westsim.com zone or any child zone. On all DNS servers that are authoritative for the private.westsim.com zone or any child zone, create a forwarders list. Forward to DNS servers that are authoritative for the parent zone. Delete root hints to Internet DNS servers on all DNS servers that are authoritative for the private.westsim.com zone or any child zone. Delete root hints to Internet DNS servers on all DNS servers that are authoritative for the westsim.com zone. On all DNS servers that are authoritative for the westsim.com zone or any child zone, create a forwarders list. Forward to DNS servers that are authoritative for the child zone.

Delete root hints to Internet DNS servers on all DNS servers that are authoritative for the private.westsim.com zone or any child zone. On all DNS servers that are authoritative for the private.westsim.com zone or any child zone, create a forwarders list. Forward to DNS servers that are authoritative for the parent zone. EXPLANATION To prevent private.westsim.com DNS servers from contacting Internet DNS servers directly, delete root hints to Internet servers on all DNS servers that are authoritative for the private.westsim.com zone or any child zone. Instead, forward all unresolved DNS requests to parent zone DNS servers. Requests that get forwarded to westsim.com DNS servers will not be related to the private namespace. Therefore, it is safe to configure root hints to Internet DNS servers on these DNS servers. REFERENCES LabSim for Server Pro 2016, Section 9.2.

Your company uses westsim.com as its public Internet domain name. Your private network has a single Active Directory domain named westsim.local. All westsim.local authoritative DNS servers are configured to forward DNS requests across a firewall to external westsim.com authoritative DNS servers. Based on your security policy, the westsim.local authoritative DNS servers are not to contact other computers across the firewall. You manage all DNS servers that are authoritative for the westsim.com and westsim.local DNS domains. All client computers are members of the westsim.local Active Directory domain and are configured to use westsim.local authoritative DNS servers. Currently, all DNS servers have a root zone. Also, all DNS servers have the default configured cache.dns file in their %systemroot%\dns folder. Client computers on your network must resolve names in the Internet namespace and names in the westsim.local domain. You need to configure your company's DNS servers to meet these requirements. What should you do? (Select three. Each correct answer is part of the correct solution.) Reconfigure the cache.dns file on all westsim.local authoritative DNS servers so it contains names and IP addresses of all westsim.com authoritative DNS servers. Delete the cache.dns file on all westsim.com authoritative DNS servers. Delete the cache.dns file on all westsim.local authoritative DNS servers. Delete the root zone on all westsim.local authoritative DNS servers. Reconfigure the cache.dns file on all westsim.com authoritative DNS servers so it contains the names and IP addresses of all westsim.local authoritative DNS servers. Delete the root zone on all westsim.com authoritative DNS servers.

Delete the root zone on all westsim.local authoritative DNS servers. Delete the cache.dns file on all westsim.local authoritative DNS servers. Delete the root zone on all westsim.com authoritative DNS servers EXPLANATION To complete the configuration, take the following actions: - Delete the root zone on all westsim.local authoritative DNS servers. Otherwise, the server will not forward addresses (unless conditional forwarding is configured). There is no need to have a private root domain in this scenario. - Delete the root zone on all westsim.com authoritative DNS servers. Only root Internet servers should have a public root zone. - Delete the cache.dns file on all westsim.local authoritative DNS servers. The cache.dns file contains root hints (references to DNS servers that are authoritative for the root zone). Internal DNS servers cannot contact Internet root servers due to the firewall (nor should they, for security's sake). Therefore, the internal DNS servers should not have root hints. Do not reconfigure the cache.dns file on all westsim.local authoritative DNS servers so it contains the names and IP addresses of all westsim.com authoritative DNS servers. Doing so will make the westsim.com authoritative DNS servers appear as root servers to the internal DNS servers, which is an inappropriate configuration because the westsim.com servers do not host a root zone. Do not reconfigure the cache.dns file on all westsim.com authoritative DNS servers so it contains names and IP addresses of all westsim.local authoritative DNS servers. Doing so will make it impossible for the westsim.com authoritative DNS servers to resolve most Internet DNS names because they will not have access to the Internet root zone servers. REFERENCES LabSim for Server Pro 2016, Section 9.2.

You manage the DNS servers for the eastsim.com domain. You have a domain controller named DC1 that holds an Active Directory-integrated zone for the eastsim.com zone. You would like to configure DC1 to use forwarders and root name servers to resolve all DNS name requests for unknown zones. You edit the DNS server properties for DC1. On the Forwarders tab, you find that the Use root hints if no forwarders are available option is disabled. You also find that the entire Root Hints tab is disabled, and you are unable to add any root hint servers. How can you configure the server to use the Internet root name servers for name resolution? Create a stub zone for the root zone that points to the root servers. Delete the zone named . on DC1. Configure a conditional forwarder to forward requests to the root servers. Change the eastsim.com domain to a primary standard zone.

Delete the zone named . on DC1. EXPLANATION In this scenario, DC1 has been configured with a root zone. The root zone is named . (dot). When the server has a root zone, it will not (and cannot) use root hints because it thinks that it is a root server. Deleting the root zone allows you to configure the root hints options. You will not be able to configure a stub zone or conditional forwarders for the root zone because the server has a primary copy of the root zone. REFERENCES LabSim for Server Pro 2016, Section 9.2.

You are the administrator for the corp.westsim.com domain. The network has two child domains, acct.corp.westsim.com and sales.corp.westsim.com. You need to configure DNS name resolution properties on the Srv2.sales.corp.westsim.com server. When a single label name is submitted for name resolution, you want the server to search using the following suffixes: - sales.corp.westsim.com - acct.corp.westsim.com - corp.westsim.com - westsim.com What should you do? Edit the DNS suffix search list policy to configure the custom search suffixes of acct.corp.westsim.com, corp.westsim.com, and westsim.com. On the DNS tab, configure a connection-specific suffix of acct.corp.westsim.com. Edit the DNS suffix search list policy to configure the custom search suffixes of sales.corp.westsim.com, acct.corp.westsim.com, corp.westsim.com, and westsim.com. On the DNS tab, enable Append parent suffixes of the primary DNS suffix. Configure an additional custom suffix of acct.corp.westsim.com.

Edit the DNS suffix search list policy to configure the custom search suffixes of sales.corp.westsim.com, acct.corp.westsim.com, corp.westsim.com, and westsim.com. EXPLANATION In this scenario, you will need edit the DNS suffix search list policy to configure custom suffixes for sales.corp.westsim.com, acct.corp.westsim.com, corp.westsim.com, and westsim.com. When you configure custom DNS suffixes, the primary and connection-specific suffixes are ignored. For this reason, configuring only acct.corp.westsim.com, corp.westsim.com, and westsim.com as suffixes will be insufficient to meet the requirements. Configuring only acct.corp.westsim.com as a custom suffix would mean that only that domain is searched. Configuring acct.corp.westsim.com as a connection-specific suffix would work only if you also enabled the Append parent suffixes of the primary DNS suffix option. REFERENCES LabSim for Server Pro 2016, Section 9.2.

Your company's internal namespace is westsim.local. This domain has two additional child domains named support.westsim.local and research.westsim.local. Due to security concerns, your company's internal network is not connected to the Internet. Following are the DNS servers that you manage for your company: - Dns1, authoritative for . and westsim.local, IP address = 192.168.1.1 - Dns2, authoritative for support.westsim.local, IP address = 192.168.2.1 - Dns3, authoritative for research.westsim.local, IP address = 192.168.3.1 All internal DNS domains are Active Directory-integrated domains. You have configured Dns1 with appropriate delegation records for the child zones. How should you configure root hints for Dns2 and Dns3? Copy the Cache.dns file from Dns1 to Dns2 and Dns3. Edit the Cache.dns file on Dns1. Delete all entries in the file. In DNS Manager, edit the properties for Dns2 and Dns3. On the Root Hints tab, select the Copy from server option and specify 192.168.1.1 as the server to copy from. In DNS Manager, edit the properties for Dns2 and Dns3. On the Root Hints tab, remove all default root hints entries and then add an entry for Dns1.

In DNS Manager, edit the properties for Dns2 and Dns3. On the Root Hints tab, remove all default root hints entries and then add an entry for Dns1. EXPLANATION The Dns2 and Dns3 servers need a root hint to Dns1, which is an internal root zone server. You can configure root hints through the properties of a DNS server or by configuring the DNS server's Cache.dns file. Make sure to remove the default root hints entries to the Internet root servers. Copying root hints from another server adds to the existing root hints rather than replacing them. In addition, if you copied root hints from Dns1, Dns2 and Dns3 would have root hints to all root Internet servers. In this configuration, you want Dns2 and Dns3 to have a single root hint to Dns1. REFERENCES LabSim for Server Pro 2016, Section 9.2.

Your company's Internet namespace is westsim.com, and your company's internal namespace is internal.westsim.com. Your network has two DNS servers, DNS1 and DNS2. DNS1 is configured with a root zone and is authoritative for the internal.westsim.com domain. DNS2 is authoritative for the westsim.com domain. All client computers are members of the internal.westsim.com domain and are configured to use DNS1 as the primary DNS server. Client computers on your internal network cannot resolve Internet DNS names. You verify that client computers can resolve internal DNS names successfully. You also verify that the internal DNS server is configured to forward all unresolvable DNS names to the company's Internet DNS server. You must keep your internal network as secure as possible while making sure that all client computers can resolve Internet DNS names successfully. What should you do? On an Active Directory domain controller, perform an authoritative restore of the root hints data. Then trigger the Update Server Data Files action on DNS1. On DNS2, copy the Cache.dns file from the DNS\Backup folder to the DNS folder. On DNS1, delete the . zone. On DNS1, copy the Cache.dns file from the DNS\Backup folder to the DNS folder. On DNS1, add root hints to Internet root DNS servers.

On DNS1, delete the . zone. EXPLANATION In this scenario, you need to delete the . zone on DNS1. A server with a root zone considers itself authoritative. Such a DNS server will not forward DNS queries (unless they are conditionally forwarded), and it will not use root hints to contact other DNS root servers. If a server is configured with a root zone, the root hints are not used. You cannot edit root hints in the DNS snap-in if the server hosts a root zone. REFERENCES LabSim for Server Pro 2016, Section 9.2.

You are the administrator for the corp.westsim.com domain. The network has two child domains, acct.corp.westsim.com and sales.corp.westsim.com. You need to configure DNS name resolution properties on the Srv2.sales.corp.westsim.com server. When an unqualified name is submitted for name resolution, you want the server to search using the following suffixes: - sales.corp.westsim.com - corp.westsim.com - westsim.com You want to configure the solution with the least amount of effort possible. What should you do? On the DNS tab, configure custom search suffixes of sales.corp.westsim.com, corp.westsim.com, and westsim.com. On the DNS tab, configure a connection-specific DNS suffix of sales.corp.westsim.com. Select Append parent suffixes of the primary and connection-specific DNS suffixes. On the DNS tab, configure custom DNS suffixes for corp.westsim.com and westsim.com. On the DNS tab, select Append parent suffixes of the primary DNS suffix.

On the DNS tab, select Append parent suffixes of the primary DNS suffix. EXPLANATION All that is required in this situation is to select the Append parent suffixes of the primary DNS suffix option. The primary suffix for the computer is sales.corp.westsim.com. By enabling parent suffixes, the computer will search all parent domains of the primary suffix in order (removing a domain for each subsequent search). Configuring custom search suffixes for sales.corp.westsim.com, corp.westsim.com, and westsim.com would work, but would require more effort than just enabling the parent suffixes. Configuring custom suffixes for corp.westsim.com and westsim.com would not work because when custom suffixes are used, neither the primary nor the connection-specific suffix is used. This would mean that sales.corp.westsim.com would never get searched. Configuring a connection suffix for sales.corp.westsim.com and enabling parent suffixes would work, but involves an unnecessary step because the computer already uses sales.corp.westsim.com as the primary suffix. REFERENCES LabSim for Server Pro 2016, Section 9.2.

Your company has an Internet domain of westsim.com. Your internal network has three Active Directory domains named westsim.local, support.westsim.local, and research.westsim.local. You install a server named SL-SRV1 as a member of the westsim.local domain. You configure SL-SRV1 with a static IP address of 192.168.0.23. You configure the server to dynamically register its DNS name. Clients in the support.westsim.local domain need to access the SL-SRV1 server. Some users in the support.westsim.local domain are accustomed to using the support.westsim.local suffix when accessing network resources. To accommodate these users, you want to dynamically register the name SL-SRV1.support.westsim.local in addition to the SL-SRV1.westsim.local name in DNS. What should you do? On the SL-SRV1 server, edit the advanced TCP/IP properties of the server's local area connection. Add a connection-specific suffix of support.westsim.local. Apply the changes and then run ipconfig /registerdns. On the SL-SRV1 server, edit the system properties. On the Computer Name tab, add support.westsim.local as a new DNS suffix. Apply the changes and then run ipconfig /registerdns. Configure the SL-SRV1 server to use DHCP. Then configure the network's DHCP server(s) to always update A and PTR records of DHCP clients. On the primary DNS server used by the SL-SRV1 server, create an alias record for SL-SRV1.support.westsim.local. Then, on SL-SRV1, run ipconfig /registerdns. On the SL-SRV1 server, edit the TCP/IP properties of the server's local area connection. Define an alternate configuration. Apply the changes and then run ipconfig /registerdns.

On the SL-SRV1 server, edit the advanced TCP/IP properties of the server's local area connection. Add a connection-specific suffix of support.westsim.local. Apply the changes and then run ipconfig /registerdns. EXPLANATION On the SL-SRV1 server, edit the advanced TCP/IP properties of the server's local area connection. Add a connection-specific suffix of support.westsim.local. Apply the changes and then run ipconfig /registerdns. In addition to the primary DNS suffix, the server's name using the connection-specific suffix will also be registered in DNS. The scenario indicates that the server is already configured to use dynamic registration, so Register this connection's addresses in DNS should already be enabled. Otherwise, you should enable it. You cannot add a DNS suffix by changing the computer's name using system properties or by creating an alternate TCP/IP configuration. Configuring the DHCP server to always update the A and PTR records of DHCP clients is another method for configuring dynamic DNS updates. However, the computer must first be configured with the appropriate name. Creating an alias record will also not configure dynamic DNS registration. REFERENCES LabSim for Server Pro 2016, Section 9.2.

Drag the DNS term on the left to the appropriate definition on the right. (Each term may be used once, more than once, or not at all.) Drag Forward lookup Reverse lookup Recursion Delegation Drop Uses the IP address to find the host name (or FQDN). Client computers submit a DNS request to the DNS server and wait for a complete response. The process by which a DNS server or host uses root name servers and subsequent servers to perform name resolution. Uses the hostname (or the FQDN) to find the IP address.

Uses the IP address to find the host name (or FQDN). Reverse lookup Client computers submit a DNS request to the DNS server and wait for a complete response. Recursion The process by which a DNS server or host uses root name servers and subsequent servers to perform name resolution. Recursion Uses the hostname (or the FQDN) to find the IP address. Forward lookup EXPLANATION Forward lookup: uses the host name (or the FQDN) to find the IP address. Reverse lookup: uses the IP address to find the host name (or FQDN). Recursion: the process by which a DNS server or host uses root name servers and subsequent servers to perform name resolution. Most client computers do not perform recursion; rather, they submit a DNS request to the DNS server and wait for a complete response. Many DNS servers will perform recursion. Delegation: the process by which a DNS server hands responsibility for the request to another DNS server. REFERENCES LabSim for Server Pro 2016, Section 9.2.