What should you do?

Note: This question-is part of a series of questions that use the same or similar answer choices. An answer choice may be correct for more than one question-in the series. Each question-is independent of the other questions in this series. Information and details provided in a question-apply only to that question.
Your network contains Windows and non-Windows devices.
You have a DHCP server named Server1 that has an IPv4 scope named Scope1.
You need to prevent a client computer that uses the same name as an existing registration from updating the registration.
What should you do?
A. From the properties of Scope1, modify the Conflict detection attempts setting.
B. From the properties of Scope1, configure Name Protection.
C. From the properties of IPv4, configure the bindings.
D. From IPv4, create a new filter.
E. From the properties of Scope1, create an exclusion range.
F. From IPv4 run the DHCP Policy Configuration Wizard.
G. From Control Panel, modify the properties of Ethernet.
H. From Scope1, create a reservation.

microsoft-exams

One thought on “What should you do?

  1. the answer is correct

    the main point is same name

    Explanation/Reference:
    https://blogs.technet.microsoft.com/teamdhcp/2009/01/29/what-is-name-protection/
    Name Protection is based on the DHCID support to the DHCP server, and support for the new DHCID RR (Resource Record) to Microsoft DNS. In addition,
    support for DUID will be added to the IPv4 registration on the DHCP client.
    Therefore DHCID is a resource record stored in DNS like other RRs.
    This RR is intended to be used by DHCP to store an identifier for a machine, along with other information for the name such as a machine’s A/AAAA records.
    DHCID effectively provides a mapping to determine if a name has already been assigned, and if the address of the machine assigned to the name is the same as
    the machine requesting registration with this name.
    DHCP’s unique position in the name registration process allows it to request this match, and then refuse the registration of a machine with a different
    address attempting to register a name with an existing DHCID record.
    Prevents the following name squatting situations:
    – Server name squatting by a client
    – Server name squatting by another server
    – Client name squatting by another client
    – Client name squatting by a server

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.