- Home
- Juniper Certification
- JN0-692 Exam
- Juniper.JN0-692.dumpsfiles Dumps
Free Juniper JN0-692 Exam Dumps Questions & Answers
| Exam Code/Number: | JN0-692Join the discussion |
| Exam Name: | Service Provider Routing and Switching Support, Professional |
| Certification: | Juniper |
| Question Number: | 60 |
| Publish Date: | Oct 22, 2026 |
|
Rating
100%
|
|
Total 60 questions
Click the Exhibit button.
-- Exhibit --
[edit]
user@router# show protocols bgp
group ebgp {
import block-martian;
family inet {
unicast;
}
peer-as 65530;
neighbor 172.22.135.37;
}
[edit]
user@router# show policy-options
policy-statement block-martian {
term 1 {
from {
route-filter 0.0.0.0/8 orlonger reject;
route-filter 127.0.0.0/8 orlonger reject;
route-filter 191.255.0.0/16 orlonger reject;
route-filter 192.0.0.0/24 orlonger reject;
route-filter 223.255.255.0/24 orlonger reject;
route-filter 240.0.0.0/4 orlonger reject;
}
}
then reject;
}
[edit]
You have established a peering with an EBGP neighbor, but the peer's 172.0.0.0/8 routes show as hidden.
Referring to the exhibit, what is causing the problem?
You are evaluating a routing policy for an ISP and you find the ^42+ .* (23|9)$ regular expression. Which three AS paths match the regular expression? (Choose three.)

Which two scenarios would explain the error shown in the exhibit? (Choose two.)
R1 and R2 are IS-IS Level 1 routers, but are not forming an adjacency.
Which two reasons would account for this happening? (Choose two.)
Click the Exhibit button.
-- Exhibit -
user@P1# show policy-options policy-statement imp-bgp1 term 1 {
from {
protocol bgp;
route-filter 0.0.0.0/0 orlonger;
}
then {
preference 245;
}
}
user@P1# show protocols bgp group IBGP
local-address 172.24.255.1;
family inet {
unicast; } family inet-vpn {
unicast; } cluster 172.24.255.1; peer-as 50; neighbor 172.24.255.3; neighbor 172.24.255.2 {
local-preference 200;
import imp-bgp1; } neighbor 172.24.255.4; -- Exhibit -
The operator of the network shown in the exhibit wants to make 172.24.255.2 the preferred path for routes. However, the router still prefers a different peer.
What is the problem?