Juniper JN0-661 Exam Practice Questions (P. 2)
- Full Access (65 questions)
- Six months of Premium Access
- Access to one million comments
- Seamless ChatGPT Integration
- Ability to download PDF files
- Anki Flashcard files for revision
- No Captcha & No AdSense
- Advanced Exam Configuration
Question #6
Click the Exhibit button.
[edit] [edit]
lab@r1# show protocols lab@r2# show protocols
ospf3 { ospf3 {
area 0.0.0.0 { area 0.0.0.0 {
interface 1o0.0; interface 1o0.0;
interface ge-1/0/6.0; interface ge-1/0/7.0;
}
}
lo0 = 172.16.100.1/32 [edit]
fc00:1000::1/128 lab@r2# show protocols
ospf3 {
area 0.0.0.0 {
interface 1o0.0;
interface ge-1/1/7.0;
interface ge-1/1/6.0;
}
}
You must ensure that r1's IPv4 loopback address exists in r3's inet 0 routing table.
Referring to the exhibit, which statement is true?
[edit] [edit]
lab@r1# show protocols lab@r2# show protocols
ospf3 { ospf3 {
area 0.0.0.0 { area 0.0.0.0 {
interface 1o0.0; interface 1o0.0;
interface ge-1/0/6.0; interface ge-1/0/7.0;
}
}
lo0 = 172.16.100.1/32 [edit]
fc00:1000::1/128 lab@r2# show protocols
ospf3 {
area 0.0.0.0 {
interface 1o0.0;
interface ge-1/1/7.0;
interface ge-1/1/6.0;
}
}
You must ensure that r1's IPv4 loopback address exists in r3's inet 0 routing table.
Referring to the exhibit, which statement is true?
- AAn IPv4 unicast realm can be enabled on each router.
- BA policy can be configured on r1 to redistribute 172.16.100.1/32 into OSPFv2, which would cause r3 to eventually learn the route and place it into inet 0.
- CA RIB group can be configured on r3 to copy that route into inet 0 because 172.16.100.1/32 exists in r3's inet6.0 table.
- DA policy can be configured on r1 to redistribute 172.16.100.1/32 into OSPFv3, which would cause r3 to eventually learn the route and place it into inet 0.
Correct Answer:
C
A RIB group is a way to have a routing protocol, in most cases, place information in multiple route tables.
Each RIB group is named and told where to place and retrieve route information. An example of a RIB group is: routing-options { rib-groups { test { import-rib [ inet.0 test.inet.0 ];
}
}
References:
https://kb.juniper.net/InfoCenter/index?page=content&id=kb16133&actp=search
C
A RIB group is a way to have a routing protocol, in most cases, place information in multiple route tables.
Each RIB group is named and told where to place and retrieve route information. An example of a RIB group is: routing-options { rib-groups { test { import-rib [ inet.0 test.inet.0 ];
}
}
References:
https://kb.juniper.net/InfoCenter/index?page=content&id=kb16133&actp=search
send
light_mode
delete
Question #7
Click the Exhibit button.

Referring to the exhibit, you have a network that uses PIM-SM and you need to block certain PIM register messages.
Which two statements are correct in this situation? (Choose two.)

Referring to the exhibit, you have a network that uses PIM-SM and you need to block certain PIM register messages.
Which two statements are correct in this situation? (Choose two.)
- AYou should apply a policy that blocks PIM register messages from the source on R4.
- BYou should apply a policy that blocks PIM register messages from the source on R3.
- CYou should apply a policy that blocks PIM register messages from the source on R2.
- DYou should apply a policy that blocks PIM register messages from the source on R1.
Correct Answer:
A
You can filter Protocol Independent Multicast (PIM) register messages sent from the designated router (DR) or to the rendezvous point (RP).
Note: In a shared tree, the root of the distribution tree is a router, not a host, and is located somewhere in the core of the network. In the primary sparse mode multicast routing protocol, Protocol Independent Multicast sparse mode (PIM SM), the core router at the root of the shared tree is the rendezvous point (RP).
References:
http://www.juniper.net/documentation/en_US/junos15.1/topics/example/ospf-designated-router-election-configuring.html
A
You can filter Protocol Independent Multicast (PIM) register messages sent from the designated router (DR) or to the rendezvous point (RP).
Note: In a shared tree, the root of the distribution tree is a router, not a host, and is located somewhere in the core of the network. In the primary sparse mode multicast routing protocol, Protocol Independent Multicast sparse mode (PIM SM), the core router at the root of the shared tree is the rendezvous point (RP).
References:
http://www.juniper.net/documentation/en_US/junos15.1/topics/example/ospf-designated-router-election-configuring.html
send
light_mode
delete
Question #8
Which statements are true about NG MVPNs? (Choose two.)
- ANG MVPN membership is signaled between PEs using PIM?
- BEvery NG MVPN PE router builds a selective provider multicast service interface tunnel to every other router in the same NG MVPN
- CNG MVPN membership is signaled between PEs using MP-BGP.
- DCustomer multicast traffic can be transported over the provider network using point-to-multipoint MPLS LSPs.
Correct Answer:
BD
Inter-AS MVPN Membership Discovery (Type 2 Routes), via BGP MCAST-VPN address family, are used for membership discovery between PE routers that belong to different autonomous systems (ASs).
The service provider uses RSVP-TE point-to-multipoint LSPs for transmitting VPN multicast data across the network.
References: Technology Overview, Understanding Junos OS Next-Generation Multicast VPN, pages 2, 8 https://www.juniper.net/techpubs/en_US/release-independent/nce/information-products/topic-collections/nce/nce0090-ng-mvpn-understanding/ng-mvpn- understanding.pdf
BD
Inter-AS MVPN Membership Discovery (Type 2 Routes), via BGP MCAST-VPN address family, are used for membership discovery between PE routers that belong to different autonomous systems (ASs).
The service provider uses RSVP-TE point-to-multipoint LSPs for transmitting VPN multicast data across the network.
References: Technology Overview, Understanding Junos OS Next-Generation Multicast VPN, pages 2, 8 https://www.juniper.net/techpubs/en_US/release-independent/nce/information-products/topic-collections/nce/nce0090-ng-mvpn-understanding/ng-mvpn- understanding.pdf
send
light_mode
delete
Question #9
A service provider wants to start using all of their LSPs for internal traffic and not just their MPLS VPNs. Any solution must ensure that existing VPNs and routing policies will continue to function properly.
Which MPLS traffic engineering parameter would accomplish this task?
Which MPLS traffic engineering parameter would accomplish this task?
- Abgp
- Bbgp-igp-both-ribs
- Cbgp-igp
- Dmpls-forwarding
Correct Answer:
B
Using LSPs for Forwarding in Virtual Private Networks
VPNs require that routes remain in the inet.3 routing table to function properly. For VPNs, configure the bgp-igp-both-ribs option of the traffic-engineering statement to cause BGP and the IGPs to use LSPs for forwarding traffic destined for egress routers.
Incorrect Answers:
C: You can configure BGP and the IGPs to use LSPs for forwarding traffic destined for egress routers by including the bgp-igp option for the traffic-engineering statement.
References:
https://www.juniper.net/documentation/en_US/junos15.1/topics/usage-guidelines/mpls-configuring-traffic-engineering-for-lsps.html
B
Using LSPs for Forwarding in Virtual Private Networks
VPNs require that routes remain in the inet.3 routing table to function properly. For VPNs, configure the bgp-igp-both-ribs option of the traffic-engineering statement to cause BGP and the IGPs to use LSPs for forwarding traffic destined for egress routers.
Incorrect Answers:
C: You can configure BGP and the IGPs to use LSPs for forwarding traffic destined for egress routers by including the bgp-igp option for the traffic-engineering statement.
References:
https://www.juniper.net/documentation/en_US/junos15.1/topics/usage-guidelines/mpls-configuring-traffic-engineering-for-lsps.html
send
light_mode
delete
Question #10
Click the Exhibit button.
user@router# run show route 2.0.0.0/8
inet.0: 101 destinations, 198 routes (100
active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
2.0.0.0/8 *[BGP/170] 00: 12:06, MED
1000, Localpref 100, from 10.220.1.2
As path: 2000 I,
validation-state: unverified
> to 10.220.15.2 via ge-
1/0/0.0, label-switched-path r1-to-r3
to 10.220.12.2 via ge-
1/1/0.0, label-switched-path r1-to-r3
[BGP/170] 00 10, MED
1000, localpref 100, from 10.220.1.5
AS path: 2000 I,
validation-state: unverified
> to 10.220.15.2 via ge-
1/0/0.0, label-switched-path r1-to-r3
to 10.220.12.2 via ge-
1/1/0.0, label-switched-path r1-to-r3
2.6.6.6/32 *[BGP/170] 00:12:06, MED
1000, localpref 100, from 10.220.1.2
AS path: 2000 I,
validation-state: unverified
> to 10.220.15.2 via ge-
1/0/0.0, label-switched-path r1-tor3
to 10.220.12.2 via ge-
1/1/0.0, label-switched-path r1-to-r3
[BGP/170] 00:12:10, MED
1000, localpref 100, from 10.220.1.5
AS path: 2000 I,
validation-state: unverified
> to 10.220.15.2 via ge-
1/0/0.0, label-switched-path r1-to-r3
to 10.220.12.2 via ge-
1/1/0.0, label-switched-path r1-to-r3
user@router# run show route advertising-protocol
bgp 192.168.11.0
inet.0: 101 destinations, 198 routes (100
active, 0 holddown, 1 hidden)
Prefix Nexthop
MED Lclpref AS path
* 2.6.6.6/32 Self
2000 I
[edit protocols bgp]
user@router# show
export reject;
group peer {
export as1000;
neighbor 192.168.11.0 {
family inet {
unicast;
}
peer-as 1000;
}
}
[edit policy-options]
user@router# show
policy-statement as1000 {
term 1 {
from {
route-filter 2.0.0.0/8 longer;
}
then accept;
}
term 2 {
then reject;
}
}
policy-statement reject {
term 1 {
from {
route-filter 2.0.0.0/8 exact;
}
then reject
}
}
You want to advertise routes 2.0.0.0/8 and 2.6.6.6/32 to BGP peer 192.168.11.0.
Referring to the exhibit, which configuration change would satisfy this requirement?
user@router# run show route 2.0.0.0/8
inet.0: 101 destinations, 198 routes (100
active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
2.0.0.0/8 *[BGP/170] 00: 12:06, MED
1000, Localpref 100, from 10.220.1.2
As path: 2000 I,
validation-state: unverified
> to 10.220.15.2 via ge-
1/0/0.0, label-switched-path r1-to-r3
to 10.220.12.2 via ge-
1/1/0.0, label-switched-path r1-to-r3
[BGP/170] 00 10, MED
1000, localpref 100, from 10.220.1.5
AS path: 2000 I,
validation-state: unverified
> to 10.220.15.2 via ge-
1/0/0.0, label-switched-path r1-to-r3
to 10.220.12.2 via ge-
1/1/0.0, label-switched-path r1-to-r3
2.6.6.6/32 *[BGP/170] 00:12:06, MED
1000, localpref 100, from 10.220.1.2
AS path: 2000 I,
validation-state: unverified
> to 10.220.15.2 via ge-
1/0/0.0, label-switched-path r1-tor3
to 10.220.12.2 via ge-
1/1/0.0, label-switched-path r1-to-r3
[BGP/170] 00:12:10, MED
1000, localpref 100, from 10.220.1.5
AS path: 2000 I,
validation-state: unverified
> to 10.220.15.2 via ge-
1/0/0.0, label-switched-path r1-to-r3
to 10.220.12.2 via ge-
1/1/0.0, label-switched-path r1-to-r3
user@router# run show route advertising-protocol
bgp 192.168.11.0
inet.0: 101 destinations, 198 routes (100
active, 0 holddown, 1 hidden)
Prefix Nexthop
MED Lclpref AS path
* 2.6.6.6/32 Self
2000 I
[edit protocols bgp]
user@router# show
export reject;
group peer {
export as1000;
neighbor 192.168.11.0 {
family inet {
unicast;
}
peer-as 1000;
}
}
[edit policy-options]
user@router# show
policy-statement as1000 {
term 1 {
from {
route-filter 2.0.0.0/8 longer;
}
then accept;
}
term 2 {
then reject;
}
}
policy-statement reject {
term 1 {
from {
route-filter 2.0.0.0/8 exact;
}
then reject
}
}
You want to advertise routes 2.0.0.0/8 and 2.6.6.6/32 to BGP peer 192.168.11.0.
Referring to the exhibit, which configuration change would satisfy this requirement?
- ADelete the as1000 export policy.
- BChange the as1000 policy to orlonger.
- CDelete the reject export policy.
- DChange the reject policy to longer.
Correct Answer:
B
We must change the match type from longer to orlonger in the as1000 policy. The match type Orlonger matches if the prefix-length is equal to or greater than the routes prefix length, while the Longer match type only matches if the prefix-length is greater than the routes prefix length.
References:
http://www.juniper.net/documentation/en_US/junos15.1/topics/example/policy-prefix-list.html
B
We must change the match type from longer to orlonger in the as1000 policy. The match type Orlonger matches if the prefix-length is equal to or greater than the routes prefix length, while the Longer match type only matches if the prefix-length is greater than the routes prefix length.
References:
http://www.juniper.net/documentation/en_US/junos15.1/topics/example/policy-prefix-list.html
send
light_mode
delete
All Pages