Examkin

Question

Difficulty: Very hardIP Addressing Services

A network security architect is reviewing enterprise core IP addressing service configurations to harden multi-VLAN operations and directory service integration. Match each specific service capability or deployment requirement on the left with its corresponding network protocol, DNS record type, or service mechanism on the right.

  • Injecting access switch attachment details (Circuit ID and Remote ID) into client lease requests before forwarding them across layer 3 boundaries to a centralized server.DHCP Option 82 (Relay Agent Information)
  • Advertising server locations by specifying targeted hostnames, protocol ports, priority, and weight metrics for directory service discovery.DNS SRV Record
  • Securing name resolution responses against spoofing and cache poisoning by validating public-key cryptographic signatures attached to resource record sets.DNSSEC (DNS Security Extensions)
  • Distributing UTC synchronization metrics from hierarchical reference clocks across network devices to guarantee consistent event logging order.NTP (Network Time Protocol)

Answer

1. Injecting switch attachment details pairs with DHCP Option 82. 2. Advertising server hostnames, ports, priority, and weight pairs with DNS SRV Record. 3. Securing name resolution using cryptographic signatures pairs with DNSSEC. 4. Distributing UTC clock synchronization metrics pairs with NTP.
The pairings are correct because each IP service mechanism directly addresses the stated technical requirement: DHCP Option 82 appends switch attachment metadata to relay requests; DNS SRV records specify target hostnames along with port numbers, priority, and weight; DNSSEC adds cryptographic signature verification to DNS records; and NTP distributes synchronized stratum-based clock references for precise logging across network nodes.

Step-by-Step Solution

1
Analyze the requirement for attaching switch port metadata into DHCP requests across subnets.
Identify that DHCP Relay Agent Information Option (Option 82) allows intermediate Layer 3 relay switches to append subscriber circuit IDs and remote IDs before relaying queries.
Option 82 provides security and targeted IP assignment based on physical switch port locations.
2
Examine service locator requirements that include port, priority, weight, and target hostname information.
Match with the DNS SRV (Service) record specification.
SRV records explicitly publish transport port numbers along with priority and load-balancing weights for service endpoint discovery.
3
Evaluate the cryptographic authentication mechanism for protecting DNS records against tampering and cache poisoning.
Match with DNSSEC (DNS Security Extensions).
DNSSEC adds digital signatures to DNS records to provide origin authority and data integrity verification.
4
Determine the service responsible for propagating accurate hierarchical UTC time synchronization across enterprise logs.
Match with Network Time Protocol (NTP).
NTP uses hierarchical stratum reference clocks to align time values across distributed systems.

Key Concept

Core Enterprise IP Addressing Services and Features
Rate this question

Topics

IP Addressing Services

More questions from this topic