4

.docx

School

Indiana Institute of Technology *

*We aren’t endorsed by this school

Course

2000

Subject

Information Systems

Date

May 19, 2024

Type

docx

Pages

8

Uploaded by ColonelKnowledgeAlligator16 on coursehero.com

Question 1: Which DHCP high-availability option typically assigns both servers 50% of the IP leases? Splitting the DHCP scope Hot standby Windows failover cluster Load balance Explanation Load balance is the default DHCP failover mode. Both servers are typically assigned 50% of the IP leases, but you can adjust this as needed. Question 2: Which of the following is true regarding the load balance DHCP failover mode? When a client requests an IP configuration, a hash is generated using the client's MAC address. During the MCLT duration, the standby server will issue new leases as long as there are available leases from its reserve pool. It is ideal for smaller networks where one server can easily handle the bulk of the DHCP functions. You manually assign the main server a percentage of IP leases. By default, this is 95%. Explanation With the load balance DHCP failover mode: when a client requests an IP configuration, a hash is generated using the client's MAC address. Each server is assigned a range of hashes to handle, known as the hash bucket. In hot standby mode, you manually assign the main server a percentage of IP leases. By default, this is 95%. Hot standby mode is ideal for smaller networks, where one server can easily handle the bulk of the DHCP functions without getting overloaded. With the hot standby mode, during the MCLT duration, the standby server will issue new leases as long there are available leases from the reserve pool. Question 3:
Which of the following were drawbacks to using the Windows failover cluster feature that was available in Windows Server 2008 and earlier? (Select two.) Backup servers that already had a large number of addresses couldn't handle the additional load. The shared storage was a single point of failure. It was difficult and time consuming to configure. The servers did not share information on active leases. When the main server went down, devices couldn't keep their current IP configuration. Explanation A failover cluster worked well, but did have drawbacks including: It was difficult and time consuming to configure a server cluster. The shared storage was a single point of failure. Backup storage could be used for redundancy, but this involved additional cost and effort. The splitting the DHCP scope option was not too difficult to implement, but did have drawbacks including: Backup servers that already had a large number of addresses couldn't handle the additional load. The servers did not share information on active leases. When the main server went down, devices couldn't keep their current IP configuration because the backup server didn't have that information. Question 4: You are the network administrator for CorpNet.xyz. The company has a main office and a branch office. All the clients use DHCP to obtain IP addresses. There is a local DHCP server in each office configured with the appropriate scope for that location. The DHCP server in the branch office fails, and users are unable to obtain IP addresses. You need to configure DHCP to meet the following requirements: Users must obtain IP addresses from their local DHCP server if it is operational. Users should be able to obtain IP addresses from the other DHCP server only if the DHCP server in their office is offline. Both servers should contain a copy of the database of client leases for both scopes. What should you do? Create a Network Load Balancing (NLB) cluster and add both servers to the cluster. Configure both DHCP servers as hot standby failover partners.
Configure both DHCP servers as load sharing failover partners. Create a failover cluster and add both servers to the cluster. Explanation You should configure both DHCP servers as hot standby failover partners. Windows Server 2016 allows administrators to create failover partners from inside the DHCP management console. There are two modes for DHCP failover, load sharing and hot standby. In a hot standby relationship, the database of leases is replicated between the failover partners. However, only the primary DHCP server leases addresses to the clients. If the primary server becomes unavailable, the hot standby server will begin servicing clients. In a load sharing relationship, both servers will lease addresses to the clients. If one server fails, the other server will service all client requests. Network Load Balancing (NLB) clusters are used to provide high availability for stateless applications where data does not change. NLB would be unsuitable for any application that has a database, such as a DHCP server. Failover clusters provide high availability for stateful applications where data does change, and is good for database applications such as DHCP, SQL, and Exchange. However, failover clusters require one copy of the database be stored on shared storage, such as a Storage Area Network (SAN). Therefore, if the DHCP servers were configured in a failover cluster, there would be one copy of the client database lease stored on the shared storage. When you configure the DHCP servers as failover partners, the database of client leases is replicated between the servers so that each server maintains a copy of the database. Question 5: Incorrect You are the network administrator for CorpNet.xyz. Your environment contains a mix of Windows 10 and non-Microsoft clients. All client computers use DHCP to obtain an IP address. Some Windows 10 clients report that they are experiencing DNS issues. When you investigate in the CorpNet.xyz zone, you notice that the IP addresses in the A records for those clients point to non-Microsoft clients. You need to ensure that non-Microsoft clients cannot overwrite the DNS records for Microsoft clients. Non-Microsoft clients must still be able to register records with the DNS servers. What should you do? Implement DHCP Name Protection on the scope. Convert the corpnet.com zone to Active Directory-Integrated. Convert the scope to a split scope. Implement DNSSEC on the corpnet.com zone.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help