Exam JN0-649 topic 1 question 13 discussion

C and D looks perfect

The question is asking about the load balancing of BGP Protocol within routing-instance (l3vpn) also the correct answer is "C and D" https://www.juniper.net/documentation/us/en/software/junos/vpn-l3/topics/topic-map/l3-vpns-load-balancing.html#d74e318

Answer is CD. https://www.juniper.net/documentation/us/en/software/junos/vpn-l3/topics/topic-map/l3-vpns-load-balancing.html

c and d it is

CD the question asked for load balancing within routing instance, not just BGP

Should be BC

BC https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/load-balancing-bgp-session.html

should be c n d

i was wrong, actually is CD: To enable these features on a Layer 3 VPN routing instance, include the vpn-unequal-cost equal-external-internal statement at the [edit routing-instances routing-instance-name routing-options multipath] hierarchy level and the vrf-table-label statement at the [edit routing-instances routing-instance-name] hierarchy level.

B,C [edit protocols bgp group external] user@R1# set multipath [edit policy-options policy-statement loadbal] user@R1# set from route-filter 10.0.0.0/16 orlonger user@R1# set then load-balance per-packet Apply the load-balancing policy. content_copy zoom_out_map [edit routing-options] user@R1# set forwarding-table export loadbal

I think should be C and D, because of using multipath inside L3VPN https://www.juniper.net/documentation/us/en/software/junos/vpn-l3/topics/ref/statement/multipath-edit-routing-options.html

Should be B and C.

Fortunately, the Juniper Networks BGP implementation supports the notion of a bandwidth community. This extended community encodes the bandwidth of a given next hop, and when combined with multipath, the load-balancing algorithm distributes flows across the set of next hops proportional to their relative bandwidths. Put another way, if you have a 10-Mbps and a 1-Mbps next hop, on average nine flows will map to the high-speed next hop for every one that uses the low speed. Use of BGP bandwidth community is supported only with per-packet load balancing. The configuration task has two parts: Configure the external BGP (EBGP) peering sessions, enable multipath, and define an import policy to tag routes with a bandwidth community that reflects link speed. Enable per-packet (really per-flow) load balancing for optimal distribution of traffic. https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/load-balancing-bgp-session.html