In Microsoft DHCP administration, what is the specific term used for the defined set of IP addresses that a DHCP server can lease to clients on a given subnet?

Difficulty: Easy

Correct Answer: Scopes

Explanation:


Introduction / Context:
Dynamic Host Configuration Protocol (DHCP) automates IP address assignment so administrators do not have to configure each client manually. In Microsoft Windows Server DHCP, the server's addressable space for a particular subnet is organized using a specific object that defines which IPs are eligible to be leased. This question checks whether you know the precise administrative term used by Microsoft for that defined set of addresses.


Given Data / Assumptions:

  • The environment is Microsoft Windows Server DHCP.
  • We are focusing on the defined set of IPs available to lease on a subnet.
  • Terminology varies across vendors; we want Microsoft's canonical term.


Concept / Approach:
In Windows DHCP, a scope is the fundamental configuration object that specifies the IPv4 network ID, subnet mask, start and end of the usable address range, exclusions, lease duration, and options (such as default gateway and DNS servers). Although many engineers informally say “pool” or “range,” those words describe parts of a scope (the contiguous address range or the general idea of available addresses). In Microsoft's console, however, the formal, manageable unit you create and enable for a subnet is called a scope.


Step-by-Step Solution:

Identify the platform: Microsoft DHCP on Windows Server.Determine the administrative object that defines leasable addresses: Scope.Confirm that “pool” and “range” are informal or component ideas, not the canonical object name.Select “Scopes” as the correct term.


Verification / Alternative check:
In the DHCP management console (dhcpmgmt.msc) and documentation, you create a new Scope, specify its address range, optionally configure exclusions and reservations, and activate it. That language confirms the official term as “scope.”


Why Other Options Are Wrong:

  • Pools: colloquial and used by some vendors, but not the formal Windows DHCP object name.
  • Ranges: a subsetting concept inside a scope; not the administrative container itself.
  • Notes: metadata, not an address set.
  • None of the above: incorrect because “Scopes” is correct.


Common Pitfalls:
Mixing cross-vendor terminology; assuming “pool” is universally correct; forgetting that a scope also encapsulates options, lease policies, and exclusions beyond just the start/end IPs.


Final Answer:
Scopes.

More Questions from Networking

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion