Question 6 of 207

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this sections, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

Your network contains an Active Directory domain named contoso.com. The domain contains a DHCP server named Server2 than runs Windows Server 2016.

Users report that their client computers fail to obtain an IP address.

You open the DHCP console as shown in the Exhibit. (Click the Exhibit button.)

Scope1 has an address range of 172.16.0.10 to 172.16.0.100 and a prefix length of 23 bits.

You need to ensure that all of the client computers on the network can obtain an IP address from Server2.

Solution: You run the Set-DhcpServerv4Scope cmdlet.

Does this meet the goal?

    Correct Answer: A

    To resolve the issue of client computers failing to obtain an IP address from the DHCP server, the Set-DhcpServerv4Scope cmdlet is appropriate. The problem appears to be that the DHCP scope has exhausted its available IP addresses, as indicated by the blue icon in the DHCP console. The range of the IP addresses in the scope can be adjusted using the Set-DhcpServerv4Scope cmdlet to include a larger pool of addresses or to modify other properties such as lease duration. This will ensure that all client computers can obtain an IP address.

Question 7 of 207

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this sections, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

Your network contains an Active Directory domain named contoso.com. The domain contains a member server named Server1 that runs Windows Server 2016 and has the DNS Server role installed. Automatic scavenging of stale records is enabled and the scavenging period is set to 10 days.

All client computers dynamically register their names in the contoso.com DNS zone on Server1.

You discover that the names of multiple client computers that were removed from the network several weeks ago can still be resolved.

You need to configure Server1 to automatically remove the records of the client computers that have been offline for more than 10 days.

Solution: You run the dnscmd.exe command and specify the /AgeAllRecords parameter for the zone.

Does this meet the goal?

    Correct Answer: B

    Running the 'dnscmd.exe' command with the /AgeAllRecords parameter sets the current time on the time stamps of all records in the specified zone. This action only updates the time stamps, and as a result, the 10-day scavenging period must elapse again before the records can be considered stale and removed. This method does not directly remove the records of the client computers that have been offline for more than 10 days. Therefore, this solution does not meet the goal.

Question 8 of 207

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this sections, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

Your network contains an Active Directory domain named contoso.com. The domain contains a member server named Server1 that runs Windows Server 2016 and has the DNS Server role installed. Automatic scavenging of stale records is enabled and the scavenging period is set to 10 days.

All client computers dynamically register their names in the contoso.com DNS zone on Server1.

You discover that the names of multiple client computers that were removed from the network several weeks ago can still be resolved.

You need to configure Server1 to automatically remove the records of the client computers that have been offline for more than 10 days.

Solution: You set the Time to live (TTL) value of all of the records in the zone.

Does this meet the goal?

    Correct Answer: B

    Setting the Time to Live (TTL) value of DNS records only affects how long a record is cached by DNS resolvers and does not influence how long records are stored in the DNS zone itself. To remove stale records automatically, the scavenging settings must be configured correctly, including the scavenging period and the record aging settings. Since the goal is to remove records for computers that have been offline for more than 10 days, simply adjusting the TTL would not achieve this goal.

Question 9 of 207

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this sections, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

Your network contains an Active Directory domain named contoso.com. The domain contains a member server named Server1 that runs Windows Server 2016 and has the DNS Server role installed. Automatic scavenging of stale records is enabled and the scavenging period is set to 10 days.

All client computers dynamically register their names in the contoso.com DNS zone on Server1.

You discover that the names of multiple client computers that were removed from the network several weeks ago can still be resolved.

You need to configure Server1 to automatically remove the records of the client computers that have been offline for more than 10 days.

Solution: You modify the Zone Aging/Scavenging properties of the zone.

Does this meet the goal?

    Correct Answer: B

    Modifying the Zone Aging/Scavenging properties alone will not ensure that stale records are automatically removed. In addition to setting the scavenging properties on the zone, scavenging must also be enabled on the DNS server itself. Without enabling scavenging on the server, the records will not be automatically removed even if the zone properties are correctly configured.

Question 10 of 207

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals.

Your network contains an Active Directory domain named contoso.com. The domain contains a DNS server named Server1. All client computers run Windows 10.

On Server1, you have the following zone configuration.

You have the following subnets defined on Server1.

You need to prevent Server1 from resolving queries from DNS clients located on Subnet4. Server1 must resolve queries from all other DNS clients.

Solution: From a Group Policy object (GPO) in the domain, you modify the Network List Manager Policies.

Does this meet the goal?

    Correct Answer: B

    To prevent Server1 from resolving queries from DNS clients located on Subnet4, modifying the Network List Manager Policies in a Group Policy object (GPO) is not the correct solution. Network List Manager Policies are used to manage how Windows classifies networks and does not control DNS query resolution. The appropriate method to achieve this goal is to use the Add-DnsServerQueryResolutionPolicy cmdlet to create a query resolution policy that filters DNS queries based on specific criteria, such as the client subnet. This will allow you to block queries from Subnet4 while allowing queries from other subnets.