B is the correct one, also D could be correct but read the last few words... Is saying without causing any impact :) Cause the router ID of LDP will be also the transport adress then if we change the router id we will tear down the LDP session with our LDP peers, so we need to wait and build UP again the LDP session. If the LDP session is down you can no longer advertise the prefixes in mpls with labels so yeah.... There will be a little impact.
Transport address is the same as the LDP router ID. hold-interval is always set to three times the LDP discovery hello-interval. Transport address is the address used for the TCP session over which LDP is running. If the transport address is not configured, the LDP router-id is used as transport address.
Given answer is correct. As for the "force" keyword: The force keyword forces the LDP router ID to change immediately to the specified address without waiting for a restart of the LDP process. This can cause LDP session flaps and potentially disrupt MPLS LDP label bindings temporarily as the LDP sessions need to be re-established with the new router ID.
B
"LDP will use the router ID as the source of TCP session. These IP has to be /32 and be in reachable. To modify the router ID use the command mpls ldp router-id (inteface) [force]. By default router ID is selected with the highest IP of a loopback, if non exist the highest IP of any active interfaces."
This section is not available anymore. Please use the main Exam Page.300-410 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
[Removed]
10 months, 2 weeks agoXBfoundX
11 months, 1 week agoXBfoundX
11 months, 1 week agobk989
11 months, 2 weeks agointeldarvid
1 year, 10 months agoerror_909
3 years, 8 months ago[Removed]
3 years, 9 months ago[Removed]
3 years, 9 months agoCraigB83
4 years, 7 months agoJack1188
4 years, 9 months ago