Chapter 4 Flashcards
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. You need to configure root hints for Dns2 and Dns3.
What should you do?
Copy the Cache.dns file from Dns1 to Dns2 and Dns3.
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 entries, then
add an entry for Dns1.
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, remove all entries, then
add an entry for Dns1.
Your Active Directory network uses an internal DNS namespace of 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.)
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.
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.
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.
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 with root hints.
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 to use forwarders.
You administer a branch office connected to the main headquarters with a WAN link. Servers in the branch
office provide DNS and DHCP services. The company network has multiple domains, with a single domain
representing the branch office.
A DNS server called DC1 at the branch office holds the primary zone for the branch domain but holds no
other zone files. DNS servers at headquarters provide name resolution for hosts in other domains.
One day, you come to work to find a number of customer service complaints. They all report something
similar-clients can resolve local host names, but cannot resolve host names for other domains on the
network.
You contact the enterprise administrator and are told that the IP address for the DNS server that was being
used previously as a forwarder for the branch office has been changed to 10.155.11.15.
What should you do to fix the problem?
Modify the DHCP scope properties so that clients use 10.155.11.15 for name resolution.
Configure DC1 as a caching-only server.
Manually configure each client to use 10.155.11.15 for name resolution.
Change the primary zone on DC1 to an Active Directory integrated zone.
Configure DC1 to forward name resolution requests to 10.155.11.15.
Configure DC1 to forward name resolution requests to 10.155.11.15.
You manage a network with a main office and one branch office. Each office has its own Internet connection,
and the two offices are connected with a WAN link.
All computers in the main office are members of the westsim.private domain. All computers in the branch
office are members of the tulsa.westsim.private domain.
The DNS1 server in the main office holds a primary zone for the westsim.private domain, while the DNS2
server in the branch office holds the primary zone for the tulsa.westsim.private domain.
Clients in the branch office are able to resolve hostnames for the tulsa.westsim.private domain and for all
Internet hosts. However, they cannot resolve hostnames for hosts in the westsim.private domain.
You need to allow hosts in the branch office to resolve names for hosts in the main office, while still allowing
Internet name resolution and minimizing WAN traffic.
What should you do?
On DNS2, configure a conditional forwarder for the westsim.private domain to forward all requests to
DNS1.
On DNS2, delete the root hints.
On DNS2, add DNS1 as a forwarder. Disable the use of root hints.
On DNS1, add a root zone.
On DNS2, configure a conditional forwarder for the westsim.private domain to forward all requests to
DNS1.
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 have opened a new branch office in Denver. The DNS namespace will use the denver.eastsim.com
domain for the branch office. You want to configure a server in the Denver location to hold all DNS records for
computers in that domain. An administrator in the Denver office will manage the new domain.
What should you do?
In the DNS console on DC1, create a conditional forwarder for denver.eastsim.com.
In the DNS console on DC1, create a zone delegation for denver.eastsim.com.
In the DNS console on DC1, create a secondary zone for denver.eastsim.com.
In the DNS console on DC1, create a primary standard zone for denver.eastsim.com.
In the DNS console on DC1, create a zone delegation for denver.eastsim.com.
You manage the DNS servers for the eastsim.com domain. You have a domain controller named DNSl that
holds a standard primary zone for the eastsim.com zone.
You would like to configure DNSl to use forwarders for all unknown zones.
You edit the DNS server properties for DNSl. On the forwarders tab, you find that the Use root hints if no
forwarders are available option is disabled. You also find you are unable to edit the forwarders list.
What should you do?
Configure root hints on DNSl.
Change the eastsim.com domain to an Active Directory-integrated zone.
Enable recursion on DNSl.
Configure conditional forwarders.
Enable recursion on DNSl.
You are the DNS manager for the southsim.com domain.
You want to configure your single DNS server so that it never uses forwarders for name resolution.
What should you do?
Configure the server’s network connection to use 127.0.0.1 as the only listed DNS server. Remove any other DNS servers.
On the DNS server, disable recursion.
On the DNS server, delete all of the root hint servers from the root hints list.
On the DNS server, disable round robin.
On the DNS server, disable recursion.
You manage the DNS infrastructure for your network. Server Dnsl holds a primary zone for the
westsim.com domain. Server Dns2 holds a primary zone for the sales.westsim.com domain. Both servers
are also domain controllers.
Computers configured to use Dns1 as the preferred DNS server are unable to resolve names for hosts in the
sales.westsim.com domain. You need to enable Dns1 to resolve names for hosts in that domain. Zone data
for the sales.westsim.com domain should not be stored on the Dns1 server.
What should you do?
On Dns2, convert the sales.westsim.com zone to an Active Directory-integrated zone.
On Dns2, create a zone delegation for westsim.com.
On Dns1, create a zone delegation for sales.westsim.com.
On Dns1, configure a secondary zone for the sales.westsim.com zone.
On Dnsl, create a zone delegation for sales.westsim.com.
You manage the DNS infrastructure for your network. Server Dns1 holds a primary zone for the
research.westsim.com domain. Server Dns2 holds a primary zone for the sales.westsim.com domain.
Both servers are also domain controllers.
Computers configured to use Dns1 as the preferred DNS server are unable to resolve names for hosts in the
sales.westsim.com domain. You need to enable Dns1 to resolve names for hosts in that domain. Your
company security policy states that DNS zone transfers are not allowed between Dns1 and Dns2.
What should you do?
On Dns1, configure a zone delegation for sales.westsim.com.
On Dns1, configure a secondary zone for sales.westsim.com.
On Dns1, configure a conditional forwarder for sales.westsim.com.
On Dns1, configure a stub zone for sales.westsim.com.
On Dns1, configure a conditional forwarder for sales.westsim.com.
You have a computer that runs Windows 8 connected to a domain network.
After reconfiguring the static address of an internal Web server named WEB3, your computer can no longer
connect to WEBB. However, other users are still able to connect to the same Web server.
You need to be able to connect to the website on the WEB3 server.
What should you do?
Run ipconfig /flushdns.
Run ipconfig /renew.
Assign an IP address to WEB3 that is not already assigned to another computer.
Enable Network Discovery.
Run ipconfig /flushdns.
Your 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 a public DNS server. All client
computers are members of the westsim.local Active Directory domain, and are configured to use
westsim.local authoritative DNS servers.
Your company has opened one new site in South America. The South America site has its own Internet
connection, and uses a dedicated wide area network (WAN) link to company headquarters in North America
for intranet traffic.
The WAN link between company headquarters in North America and the South America site is expensive and
somewhat unreliable. DNS traffic across this WAN link must be minimized. You need to make appropriate
DNS configurations to meet this requirement.
What should you do? (Choose two. Each choice is part of the correct solution.)
Install a DNS server with no zones in the South America site. Configure the server to forward all DNS
requests to westsim.local authoritative DNS servers.
Configure all client computers in the South America site to use westsim.local authoritative DNS servers at company headquarters.
Install a westsim.local authoritative DNS server in the South America site. Configure the server to
forward all DNS requests that are unrelated to the westsim.local DNS domain to the local Internet
service provider’s DNS server.
Configure all client computers in the South America site to use the new DNS server in the South America
site.
Configure all client computers in the South America site to use the local Internet service provider’s DNS
server.
Install a DNS server with no zones in the South America site. Configure the server to conditionally
forward westsim.local DNS requests to westsim.local authoritative DNS servers and to forward all
other DNS requests to the local Internet service provider’s DNS server.
Configure all client computers in the South America site to use the new DNS server in the South America
site.
Install a DNS server with no zones in the South America site. Configure the server to conditionally
forward westsim.local DNS requests to westsim.local authoritative DNS servers and to forward all
other DNS requests to the local Internet service provider’s DNS server.
Your 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 a public DNS server. All client
computers are members of the westsim.local Active Directory domain, and are configured to use
westsim.local authoritative DNS servers.
A new site in Seattle has just opened. The Seattle site is connected to company headquarters using a virtual
private networking (VPN) connection. Company policy states that all client computers in all sites must receive
Internet access through a high speed Internet connection at company headquarters. You want to minimize
unnecessary DNS traffic across the VPN connection and configure DNS appropriately to meet company policy.
What should you do? (Choose two. Each choice is part of the correct solution.)
Configure the new DNS server to conditionally forward westsim.local DNS requests to westsim.local
authoritative DNS servers at company headquarters and to use root hints to resolve all other DNS requests.
Install a westsim.local authoritative DNS server in the Seattle site.
Configure the new DNS server to forward all DNS requests across the company firewall to a public DNS server.
Install a caching-only DNS server in the Seattle site.
Configure the new DNS server to forward all DNS requests to westsim.local authoritative DNS servers at company headquarters.
Install a caching-only DNS server in the Seattle site.
Configure the new DNS server to forward all DNS requests to westsim.local authoritative DNS servers at company headquarters.
Mary is the network administrator for the Seattle location of the WestSim Corporation. The Seattle location
has a direct connection to the Portland location. The rest of the company’s network is accessible through the
link to the Portland site.
Currently, computers in the Seattle location use the WSDNS4 server in the Portland location for DNS name
resolution. This server hosts secondary zones for the entire network. A DHCP server in the Seattle location
configures each client to use WSDNS4 for name resolution.
Because of network congestion, the enterprise administrator instructs Mary to configure a caching-only server
at the Seattle location. Mary installs the DNS service on the SEA7 server.
What must Mary do to complete the configuration? (Choose two. Each choice is part of the correct solution.)
Configure SEA7 to use WSDNS4 as a root hints server.
Configure SEA7 to use WSDNS4 as a forwarder.
Manually add SEA7 to the list of DNS servers on each client.
Modify the DHCP options so that clients use SEA7 for DNS lookups.
Configure secondary zones on SEA7 to replicate the secondary zones held on WSDNS4.
Configure root hints on SEA7 that point to Internet root zone servers.
Configure SEA7 to use WSDNS4 as a forwarder.
Modify the DHCP options so that clients use SEA7 for DNS lookups.
Your company’s Internet namespace is westsim.com, and your company’s internal namespace is
internal.westsim.com. Your network has two Windows Server 2012 R2 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, add root hints to Internet root DNS servers.
On DNS1, delete the . zone.
You are the network administrator for a company that has just implemented Windows Server 2012 R2. To
provide Internet access for your corporate office, you have decided to use a firewall that provides NAT. On
the private network, you install and configure DNS on a Windows Server 2012 R2 server to provide name
resolution.
After you finish the configuration, you realize that no one is able to access the Internet, but they are able to
contact internal servers by their FQDN. A ping test using the IP address of Internet hosts is successful.
You decide to check the forwarders setting on the DNS server, but the option to configure forwarders is
grayed out.
What should you do?
Delete the root forward lookup zone on the internal DNS server.
Verify the NAT configuration on the firewall.
Configure the internal DNS server to use root hints instead of forward.
Create a reverse lookup zone on the internal DNS server.
Delete the root forward lookup zone on the internal DNS server.
You manage a network with a single location and a single domain, westsim.com. All client computers on the
private network are members of the westsim.com domain. The westsim.com zone is configured as a primary zone on the DNSl server.
You recently opened a branch office. The branch office is connected to the main office with a WAN link. All
client computers in the branch office are members of the westsim.com domain, and use the DNSl server in
the main office for name resolution.
In analyzing WAN link traffic, you notice a lot of traffic from DNS name resolution. You would like to reduce
the name resolution traffic across the WAN link. However, you do not want any replication traffic to cross the WAN link.
What should you do?
Configure a DNS server in the branch office with a secondary copy of the westsim.com zone. Configure
all client computers in the branch office to use the new DNS server.
Configure a DNS server in the branch office with a primary zone for the westsim.com zone. Configure all client computers in the branch office to use the new DNS server.
Configure a DNS server in the branch office without any zones. Configure all client computers in the
branch office to use the new DNS server.
In the main office, convert the westsim.com zone to an Active Directory-integrated zone. Install a domain controller that also runs DNS in the branch office. Configure all client computers in the branch office to use the new DNS server.
Configure a DNS server in the branch office without any zones. Configure all client computers in the branch office to use the new DNS server.
You are the network administrator for westsim.com. The network consists of two Active Directory domains
named westsim.com and sales.westsim.com. The DNS servers in the westsim.com domain are
authoritative for the westsim.com DNS domain. The DNS servers in the sales.westsim.com domain are
authoritative for the sales.westsim.com DNS domain. All the servers run Windows Server 2012 R2. All the
clients run Windows 7 or Windows 8.
The company plans to implement a new domain named private.westsim.com. You need to design the DNS
infrastructure to support the new domain. Your solution must meet the following requirements:
The DNS servers in private.westsim.com must be authoritative for the private.westsim.com DNS
domain.
All clients in the forest must be able to resolve private.westsim.com fully qualified domain names
(FQDNs).
DNS servers in the westsim.com and sales.westsim.com domains should not be authoritative for the
private.westsim.com domain and should not contain any records for nodes in the
private.westsim.com.
You install Active Directory, create the new domain, and verify that DNS is working within the
private.westsim.com domain.
What should you do next?
You should configure a conditional forwarder on one of the DNS servers in the sales.westsim.com
domain. Set the replication scope to All DNS servers in this domain..
You should configure an Active Directory Integrated stub zone for the private.westsim.com domain on one of the DNS servers in the sales.westsim.com domain. Set the replication scope to All DNS servers in this domain..
You should ensure that the private.westsim.com zone is Active Directory Integrated. Set the replication scope to All DNS servers in this forest..
On the DNS servers in westsim.com you should create a delegation for private.westsim.com and point the delegation to the DNS servers that are authoritative for private.westsim.com.
On the DNS servers in westsim.com you should create a delegation for private.westsim.com and point the delegation to the DNS servers that are authoritative for private.westsim.com.
Your network has a single domain named southsim.com. All client computers run Windows 7 or Windows 8.
DNS data for the domain is stored on the following servers:
DNSl holds the primary zone for southsim.com.
DNSZ and DNS3 hold secondary zones for southsim.com.
All three DNS servers are located on domain controllers. The DNS zone for the domain is configured to allow
dynamic updates.
You want to allow client computers to send DNS updates to any of the three servers, and allow any of the
three servers to update DNS records in the zone.
What should you do?
On the primary zone, change the settings to allow zone transfer to only the two secondary servers.
On all three servers, change the zone type of the DNS zone to Active Directory integrated.
On the primary zone, change the dynamic update option to allow only secure updates.
On the primary zone, change the settings so that the two secondary servers are notified when the zone is updated.
On all three servers, change the zone type of the DNS zone to Active Directory integrated.
You are the administrator for the Seattle office of WestSim Corporation. Zone information for the entire
westsim.com domain is stored in a primary zone on the portland.westsim.com server located in the
Portland office.
There is a T1 line between the Seattle and Portland offices, but the line is often saturated with heavy network
traffic, which makes name resolution for those in the Seattle office very slow.
What can you do to improve DNS performance for computers in the Seattle office?
On the portland.westsim.com computer, create a new zone called seattle.westsim.com. Make it a
primary zone, and configure it to use incremental updates.
Install a DNS server in the Seattle location. Configure it with an Active Directory integrated zone of the
westsim.com domain.
Install a DNS server in the Seattle location. Configure it with a secondary zone of the westsim.com
domain.
Install a DNS server in the Seattle location. Configure it with a primary zone of the westsim.com
domain.
Install a DNS server in the Seattle location. Configure it with a secondary zone of the westsim.com
domain.