350-401 Practice Question: Runs the following command on Router R6: R6# show…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  This is a link-local LDP session because the discovery source is an interface.

  Why it's wrong here

  The label distribution protocol (LDP) session is not link-local because link-local LDP sessions are formed through interface-based hello messages (multicast to 224.0.0.2) with directly connected neighbors. Here, the output explicitly shows the discovery source as a 'Targeted Hello,' which is a unicast hello sent to a specific IP address, allowing sessions to be established between non-directly connected routers. A link-local session would never be initiated by a targeted hello, so this option misidentifies the discovery type.

• ✓

  This is a targeted LDP session established between two non-directly connected routers.

  Why this is correct

  This is a targeted LDP session because the discovery source is a 'Targeted Hello,' which is used to establish LDP peering between routers that are not directly connected. Targeted hellos are unicast to a configured neighbor's IP address, enabling the LDP peers to form a TCP session and exchange labels even across multiple hops. The output confirms this by showing the discovery source as targeted, and the session state is operational, indicating an established targeted LDP session.

• ✗

  This is a multicast LDP session because the hold time is 15 seconds.

  Why it's wrong here

  The hold time of 15 seconds is a LDP keepalive timer that governs how long a router waits to receive a keepalive message from its LDP peer before declaring the session dead. This timer is unrelated to multicast; multicast LDP (mLDP) is a separate mechanism for signaling multicast Label Switched Paths (LSPs) and does not depend on hold time values. Therefore, inferring that a 15-second hold time implies a multicast session is a fundamental misunderstanding of LDP timer functions.

• ✗

  This is a BGP session because the TCP connection shows port 179.

  Why it's wrong here

  Although the TCP connection in the LDP neighbor output shows port 179, this is not sufficient to identify the session as BGP. LDP uses TCP port 646 by default, but the output may present the local or remote port from the perspective of the session; in some implementations, the port number can be misread or the session might be using a non-standard port. The protocol is identified by the LDP-specific state fields and discovery source, not solely by the TCP port. Because the session is clearly labeled as LDP in the output and the discovery is targeted, it is not a BGP session.