Examkin

Question

Difficulty: Very hardDocumentation and Diagrams

During a post-incident audit of a multi-tier data center environment, an engineer discovers that inter-VLAN routing failure and unexpected high-availability failovers occurred because secondary database nodes were improperly connected to trunk ports missing native VLAN tags, while hosts were statically configured with individual physical interface IP addresses rather than shared gateway abstractions. Additionally, technicians were unable to physically locate the corresponding patch panel switchports during the outage due to missing physical layout records. Which of the following documentation components and procedural updates must be corrected and updated to fully remediate this environment? (Select TWO.)

  1. Update the logical network topology diagram to clearly reflect VLAN IDs, subnet boundaries, 802.1Q trunking parameters, and the First Hop Redundancy Protocol (FHRP) Virtual IP (VIP) addresses used for default gateways.Answer
  2. Update physical rack elevation diagrams and cable run schedules detailing switch U-positions, patch panel port mappings, and cable labeling standards across all equipment racks.Answer
  3. C
    Reconfigure host IP addressing baselines to point default gateways directly to the physical interface IP address of the primary active router instead of a shared Virtual IP (VIP).
  4. D
    Update the baseline operational security documentation to mandate SNMPv1 with community strings for encrypted active monitoring across all distribution switches.
  5. E
    Modify the wiring schematics to specify simple pinout continuity testers as the primary tool for measuring exact physical cable distance-to-fault locations.

Answer

The correct updates are updating the logical network topology diagram (to document VLANs, subnets, trunking parameters, and FHRP Virtual IPs) and updating the physical rack elevation diagrams and cable run schedules (to detail U-positions, patch panel mappings, and port labeling).
To fully document and remediate the environment, both logical and physical documentation must be updated. Updating the logical network topology diagram ensures that VLAN IDs, subnets, trunk configurations, and FHRP Virtual IP (VIP) addresses are accurately mapped for layer 2/3 operations and high-availability failover. Updating physical rack elevation diagrams and cable run schedules ensures that physical hardware positioning, patch panel terminations, and cable runs can be quickly audited and traced during physical maintenance.

Step-by-Step Solution

1
Analyze the logical network issues in the scenario.
Identified misconfigurations involving VLAN tags, trunking, subnets, and default gateway failovers.
Resolving logical routing and gateway issues requires an accurate logical network topology diagram showing subnets, trunk ports, and FHRP Virtual IPs.
2
Analyze the physical layer issues in the scenario.
Identified missing records for switchport and patch panel physical locations during troubleshooting.
Resolving physical tracing issues requires detailed rack elevation diagrams and cable run schedules mapping switch U-positions and patch panel ports.
3
Evaluate and eliminate distractors.
Rejected assigning physical interface IPs as default gateways, using unencrypted SNMPv1, and selecting simple continuity testers for distance-to-fault measurements.
These options introduce security vulnerabilities, break gateway redundancy, or misapply physical testing tools.

Key Concept

Differentiation between logical network topology diagrams and physical rack/cabling documentation
Estimated Time:3m 0s
Rate this question

Topics

Documentation and Diagrams

More questions from this topic