Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-510 Topic 11 Question 80 Discussion

Actual exam question for Cisco's 300-510 exam
Question #: 80
Topic #: 11
[All 300-510 Questions]

Refer to the exhibit.

Refer to the exhibit. Unified MPLS is implemented on this network to provide end-to-end services A network engineer noticed that R3 is failing to receive labels from R1 However, R2 is receiving labels from R1 R3 can ping R1 normally Which action resolves the issue?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Diego
7 months ago
I'm inclined to choose option C. Configuring R1 to run Unified MPLS on both interfaces might be the solution.
upvoted 0 times
...
Vivan
7 months ago
But if we disable MPLS IP, wouldn't that impact other parts of the network as well?
upvoted 0 times
...
Simona
7 months ago
I don't agree with that. I believe the correct answer is D. We should disable MPLS IP on the link between R1 and R3.
upvoted 0 times
...
Vivan
7 months ago
I think the answer is B. Adding the send-label keyword in the R1 neighbor statement for R3 should resolve the issue.
upvoted 0 times
...
Vincenza
8 months ago
That's a good point, Nydia. I was also considering that option. It makes sense that we need to explicitly tell R1 to send labels to R3, since it's not happening automatically.
upvoted 0 times
Queenie
7 months ago
Sounds like a plan. Let's go ahead and implement the fix.
upvoted 0 times
...
Theola
8 months ago
After that, we can verify if R3 is now receiving the labels correctly.
upvoted 0 times
...
Roxane
8 months ago
Great, let's make that configuration change on R1 then.
upvoted 0 times
...
Lisha
8 months ago
Once that change is made, R3 should start receiving labels properly.
upvoted 0 times
...
Emmett
8 months ago
I agree. R1 needs to be explicitly configured to send labels to R3.
upvoted 0 times
...
Sueann
8 months ago
That should definitely do the trick.
upvoted 0 times
...
Andrew
8 months ago
B) Add the send-label keyword in the R1 neighbor statement for R3.
upvoted 0 times
...
...
Nydia
8 months ago
I'm leaning towards option B - adding the 'send-label' keyword in the R1 neighbor statement for R3. That seems like it could be the missing piece to get the labels flowing.
upvoted 0 times
...
Paris
8 months ago
Yeah, I agree. It's strange that R3 can ping R1 normally, but not receive the labels. The question is asking about the action to resolve the issue, so we need to carefully consider the options.
upvoted 0 times
...
Murray
8 months ago
Hmm, this seems like a tricky one. I'm not sure why R3 is not receiving labels from R1, but it's good that R2 is getting them. Maybe there's something specific about the configuration between R1 and R3 that's causing the issue.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77