Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Juniper Exam JN0-649 Topic 1 Question 16 Discussion

Actual exam question for Juniper's JN0-649 exam
Question #: 16
Topic #: 1
[All JN0-649 Questions]

Your enterprise network is running BGP VPNs to support multitenancy. Some of the devices with which you peer BGP do not support the VPN NLRI. You must ensure that you do not send BGP VPN routes to the remote peer.

Which two configuration steps will satisfy this requirement? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A

transmit rate is set on the scheduler, BA and classifier do not have transmit rate. scheduler-map=maps schedulers to fwd classes


by Annelle at Jul 04, 2023, 12:30 AM

Limited Time Offer

25%

Off

Get Premium JN0-649 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Chan
1 months ago
Ah, the age-old problem of dealing with peers that can't handle your fancy VPN routes. B and D are the way to go, no doubt about it. Though I do wonder if the remote peer is using a Nokia brick phone from the 90s or something...
upvoted 0 times
Maxima
19 hours ago
User 3: It's important to make sure the remote peer does not receive the routes, so configuring an import policy on the remote peer is also necessary.
upvoted 0 times
...
Sharika
10 days ago
D) Configure the apply-vpn-export feature on the local BGP peer.
upvoted 0 times
...
Kerrie
20 days ago
User 2: I think configuring an export policy on the local BGP peer is crucial to ensure the VPN routes are not sent to the remote peer.
upvoted 0 times
...
Nichelle
22 days ago
User 1: Definitely agree, B and D are the way to go to handle this issue.
upvoted 0 times
...
Brett
1 months ago
B) Configure an export policy on the local BGP peer to reject the VPN routes being sent to the remote peer.
upvoted 0 times
...
...
Rossana
1 months ago
Haha, this is an easy one! Just don't send the VPN routes to the remote peer in the first place. B and D are the way to go.
upvoted 0 times
...
Celeste
1 months ago
I'm not sure about that. Maybe we should also configure an import policy on the remote peer to reject the routes when they are received.
upvoted 0 times
...
Julene
1 months ago
I agree with Letha. That sounds like the right approach to ensure we don't send BGP VPN routes to the remote peer.
upvoted 0 times
...
Letha
1 months ago
I think we should configure an export policy on the local BGP peer to reject the VPN routes being sent to the remote peer.
upvoted 0 times
...
Timothy
2 months ago
I'm not sure about that. Maybe we should also configure an import policy on the remote peer to reject the routes when they are received.
upvoted 0 times
...
Marge
2 months ago
Definitely B and D. Blocking the routes at the source is the way to go, rather than trying to handle it on the receiving end.
upvoted 0 times
Antonio
14 days ago
Yes, and also configuring the apply-vpn-export feature on the local BGP peer will ensure the routes are not sent to the remote peer.
upvoted 0 times
...
Coral
20 days ago
I agree, configuring an export policy on the local BGP peer to reject the VPN routes is crucial.
upvoted 0 times
...
...
Jess
2 months ago
I agree with Nieves. That seems like the best way to ensure we don't send BGP VPN routes to the remote peer.
upvoted 0 times
...
Bettyann
2 months ago
Hmm, I think B and D are the correct options here. Configuring an export policy to reject the VPN routes makes sense, and the apply-vpn-export feature sounds like it could be the right tool for the job.
upvoted 0 times
...
Nieves
2 months ago
I think we should configure an export policy on the local BGP peer to reject the VPN routes being sent to the remote peer.
upvoted 0 times
...

Save Cancel