Question

Difficulty: MediumDocumentation and Diagrams

An IT infrastructure team is performing a post-implementation audit of network documentation following a multi-site network expansion. The lead network architect emphasizes that logical network topologies must be clearly distinguished from physical topology and cabling documentation to assist with Layer 3 routing and traffic flow troubleshooting. Which of the following components should be documented specifically within a logical network diagram? (Select TWO.)

  1. IP addressing schemes, CIDR subnet masks, and assigned VLAN IDs across routing boundariesAnswer
  2. B
    Rack unit height locations and enclosure slot positions for core switch hardware
  3. Virtual IP (VIP) addresses and virtual router identifier numbers used for gateway redundancy protocolsAnswer
  4. D
    T568A vs. T568B pinout color coding standards used for copper patch panel terminations
  5. E
    Physical port designations and fiber optic patch panel port-to-port cross-connect mappings

Answer

Logical network diagrams should document IP addressing schemes with subnet masks/VLAN IDs and Virtual IP addresses associated with gateway redundancy protocols.
Logical topology diagrams depict how data flows through a network at Layer 2 and Layer 3. Therefore, IP addressing schemes with VLAN assignments and Virtual IP addresses for gateway redundancy belong on logical diagrams because they define subnets, logical boundaries, and failover traffic paths.

Step-by-Step Solution

1
Differentiate between logical and physical network documentation requirements.
Logical documentation focuses on data paths, subnets, protocol boundaries, and IP address mappings, whereas physical documentation focuses on hardware locations, cable paths, and pinouts.
Engineers rely on logical diagrams to visualize Layer 2 and Layer 3 traffic forwarding regardless of equipment chassis placement.
2
Identify elements that define logical network structure.
IP addressing schemes, subnets, VLAN IDs, and Virtual IP (VIP) addresses for redundancy protocols (such as HSRP or VRRP) explicitly define logical network boundaries.
These elements govern protocol behavior, routing decisions, and logical gateway failovers.
3
Filter out physical equipment and cabling artifacts.
Rack elevations, physical port cross-connects, and cable pinout schematics are classified as physical documentation.
Physical details do not describe protocol-level address relationships or logical data pathways.

Key Concept

Logical vs. Physical Network Documentation
Rate this question