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

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


Contribute your Thoughts:

Chan
2 days 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
...
Rossana
3 days 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
6 days 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
7 days 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
8 days 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
9 days 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
9 days 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
...
Jess
11 days 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
12 days 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
18 days 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
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