Refer to the exhibit. An engineer is troubleshooting an MPLS LDP session between two routers. The output shows that the LDP session is operational. However, MPLS labels are not being exchanged. What is the most likely cause?
In this mode, labels are only sent on request; if the peer expects unsolicited, labels may not be exchanged.
Why this answer
The exhibit shows that the LDP session is operational (state = Operational), but no labels are being exchanged. In 'downstream on demand' mode, a router does not advertise labels unless explicitly requested by an upstream neighbor via a Label Request message. Since the session is up but no labels are exchanged, this mismatch in label advertisement mode is the most likely cause.
Exam trap
The trap here is that candidates see the LDP session is 'Operational' and assume label exchange must be working, but Cisco tests the subtle distinction that session state and label advertisement are independent processes.
How to eliminate wrong answers
Option A is wrong because the LDP Ident is used to identify the label space and is bound to the router ID; the peer's addresses not being bound would prevent session establishment, not just label exchange. Option B is wrong because LDP uses TCP port 646 by default; if the TCP connection were not using port 646, the session would not be established at all. Option D is wrong because the output explicitly states the LDP session is operational, meaning it is established.