100% Latest & Updated Juniper JN0-364 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 490
OSPFv3 interface logs show Hello packets while remote IPv6 service prefixes remain missing from the routing table. Independently, the review flags the potentially unsafe practice “Treat OSPFv2 Type 1 IP subnet information as identical to OSPFv3 LSA layout”. Which validation addresses the risk without assuming a particular cause?
- Set both OSPFv3 routers to the same identifier for easier monitoring
- Inspect OSPFv3 interface and area membership
- Inspect OSPFv3 database prefix entries and inet6 route table
- Inspect peer link-local addresses and Hello counters
Explanation
Correct Answer
C:OSPFv3 uses different prefix-carrying LSAs. OSPFv3 separates prefix reachability from some topology LSA contents.
Incorrect Answers
A:Duplicate router IDs create identity ambiguity.
B:OSPFv3 uses IPv6 link operation and OSPF area membership.
D:OSPFv3 commonly uses link-local addresses for neighbor exchanges.
Question 491
An existing IS-IS core exchanges IPv4 routes and is being extended to advertise native IPv6 customer reachability. The objective is to check IS-IS IPv6 topology participation. Which Junos configuration or design action best satisfies the objective?
- Search only IPv4 reachability TLVs for missing IPv6 destinations
- Treat an Up IS-IS adjacency as conclusive proof inet6.0 is populated
- Verify the relevant IS-IS routing topology supports IPv6 reachability on the device
- Disable healthy IPv4 forwarding to force IPv6 route convergence
Explanation
Correct Answer
C:An IPv4 IS-IS adjacency is not proof of IPv6 prefix distribution.
Incorrect Answers
A:IPv4 reachability TLVs do not carry IPv6 prefixes.
B:Adjacency alone does not install a missing IPv6 prefix.
D:Breaking the existing family is not an IPv6 validation method.
Question 492
An existing IS-IS core exchanges IPv4 routes and is being extended to advertise native IPv6 customer reachability. The objective is to inspect IPv6 reachability TLVs. Which operational choice should be prioritized in this design?
- Treat an Up IS-IS adjacency as conclusive proof inet6.0 is populated
- Confirm remote IPv6 prefixes appear in the intended IS-IS advertisements
- Disable healthy IPv4 forwarding to force IPv6 route convergence
- Assume every IPv4 IS-IS route is automatically duplicated into inet6.0
Explanation
Correct Answer
B:Link-state TLV content determines advertised IPv6 reachability.
Incorrect Answers
A:Adjacency alone does not install a missing IPv6 prefix.
C:Breaking the existing family is not an IPv6 validation method.
D:IPv6 needs its own supported reachability advertisement.
Question 493
An existing IS-IS core exchanges IPv4 routes and is being extended to advertise native IPv6 customer reachability. The objective is to check IPv6 next-hop install. Which routing or switching control best fits the requirement?
- Verify remote IPv6 destinations resolve through suitable outgoing interface reachability
- Search only IPv4 reachability TLVs for missing IPv6 destinations
- Disable healthy IPv4 forwarding to force IPv6 route convergence
- Assume every IPv4 IS-IS route is automatically duplicated into inet6.0
Explanation
Correct Answer
A:Advertised IPv6 routes still require valid forwarding resolution.
Incorrect Answers
B:IPv4 reachability TLVs do not carry IPv6 prefixes.
C:Breaking the existing family is not an IPv6 validation method.
D:IPv6 needs its own supported reachability advertisement.
Question 494
An existing IS-IS core exchanges IPv4 routes and is being extended to advertise native IPv6 customer reachability. The objective is to validate dual-stack isolation. Which verification should be performed before approving the change?
- Treat an Up IS-IS adjacency as conclusive proof inet6.0 is populated
- Search only IPv4 reachability TLVs for missing IPv6 destinations
- Test IPv4 and IPv6 routes independently after rollout
- Assume every IPv4 IS-IS route is automatically duplicated into inet6.0
Explanation
Correct Answer
C:One address family's success does not validate the other.
Incorrect Answers
A:Adjacency alone does not install a missing IPv6 prefix.
B:IPv4 reachability TLVs do not carry IPv6 prefixes.
D:IPv6 needs its own supported reachability advertisement.
Question 495
An existing IS-IS core exchanges IPv4 routes and is being extended to advertise native IPv6 customer reachability. Two objectives apply: (1) inspect IPv6 reachability TLVs; and (2) validate dual-stack isolation. Which TWO controls together satisfy the requirements? Choose TWO.
- Confirm remote IPv6 prefixes appear in the intended IS-IS advertisements
- Treat an Up IS-IS adjacency as conclusive proof inet6.0 is populated
- Assume every IPv4 IS-IS route is automatically duplicated into inet6.0
- Search only IPv4 reachability TLVs for missing IPv6 destinations
- Test IPv4 and IPv6 routes independently after rollout
Explanation
Correct Answers
A:Link-state TLV content determines advertised IPv6 reachability.
E:One address family's success does not validate the other.
Incorrect Answers
B:Adjacency alone does not install a missing IPv6 prefix.
C:IPv6 needs its own supported reachability advertisement.
D:IPv4 reachability TLVs do not carry IPv6 prefixes.
Question 496
An existing IS-IS core exchanges IPv4 routes and is being extended to advertise native IPv6 customer reachability. Three objectives apply: (1) inspect IPv6 reachability TLVs; (2) check IPv6 next-hop install; and (3) validate dual-stack isolation. Which THREE controls together satisfy the requirements? Choose THREE.
- Assume every IPv4 IS-IS route is automatically duplicated into inet6.0
- Verify remote IPv6 destinations resolve through suitable outgoing interface reachability
- Disable healthy IPv4 forwarding to force IPv6 route convergence
- Confirm remote IPv6 prefixes appear in the intended IS-IS advertisements
- Test IPv4 and IPv6 routes independently after rollout
- Treat an Up IS-IS adjacency as conclusive proof inet6.0 is populated
Explanation
Correct Answers
B:Advertised IPv6 routes still require valid forwarding resolution.
D:Link-state TLV content determines advertised IPv6 reachability.
E:One address family's success does not validate the other.
Incorrect Answers
A:IPv6 needs its own supported reachability advertisement.
C:Breaking the existing family is not an IPv6 validation method.
F:Adjacency alone does not install a missing IPv6 prefix.
Question 497
Adjacencies stay Up after adding IPv6, but the target remote PE lacks IPv6 reachability TLVs and routes. Independently, the review flags the potentially unsafe practice “Assume every IPv4 IS-IS route is automatically duplicated into inet6.0”. Which inspection best evaluates that practice?
- Inspect IS-IS IPv6-related configuration and topology
- Search only IPv4 reachability TLVs for missing IPv6 destinations
- Run separate IPv4 and IPv6 reachability probes
- Inspect inet6.0 for the intended remote route
Explanation
Correct Answer
A:IPv6 needs its own supported reachability advertisement. An IPv4 IS-IS adjacency is not proof of IPv6 prefix distribution.
Incorrect Answers
B:IPv4 reachability TLVs do not carry IPv6 prefixes.
C:One address family's success does not validate the other.
D:Advertised IPv6 routes still require valid forwarding resolution.
Question 498
Adjacencies stay Up after adding IPv6, but the target remote PE lacks IPv6 reachability TLVs and routes. Independently, the review flags the potentially unsafe practice “Search only IPv4 reachability TLVs for missing IPv6 destinations”. Which evidence most directly tests the flagged assumption?
- Disable healthy IPv4 forwarding to force IPv6 route convergence
- Inspect originated and received IPv6 prefix TLVs
- Inspect inet6.0 for the intended remote route
- Inspect IS-IS IPv6-related configuration and topology
Explanation
Correct Answer
B:IPv4 reachability TLVs do not carry IPv6 prefixes. Link-state TLV content determines advertised IPv6 reachability.
Incorrect Answers
A:Breaking the existing family is not an IPv6 validation method.
C:Advertised IPv6 routes still require valid forwarding resolution.
D:An IPv4 IS-IS adjacency is not proof of IPv6 prefix distribution.
Question 499
Adjacencies stay Up after adding IPv6, but the target remote PE lacks IPv6 reachability TLVs and routes. Independently, the review flags the potentially unsafe practice “Treat an Up IS-IS adjacency as conclusive proof inet6.0 is populated”. Which diagnostic check tests this potentially unsafe choice?
- Inspect IS-IS IPv6-related configuration and topology
- Inspect inet6.0 for the intended remote route
- Disable healthy IPv4 forwarding to force IPv6 route convergence
- Inspect originated and received IPv6 prefix TLVs
Explanation
Correct Answer
B:Adjacency alone does not install a missing IPv6 prefix. Advertised IPv6 routes still require valid forwarding resolution.
Incorrect Answers
A:An IPv4 IS-IS adjacency is not proof of IPv6 prefix distribution.
C:Breaking the existing family is not an IPv6 validation method.
D:Link-state TLV content determines advertised IPv6 reachability.
Question 500
Adjacencies stay Up after adding IPv6, but the target remote PE lacks IPv6 reachability TLVs and routes. Independently, the review flags the potentially unsafe practice “Disable healthy IPv4 forwarding to force IPv6 route convergence”. Which validation addresses the risk without assuming a particular cause?
- Inspect inet6.0 for the intended remote route
- Assume every IPv4 IS-IS route is automatically duplicated into inet6.0
- Inspect originated and received IPv6 prefix TLVs
- Run separate IPv4 and IPv6 reachability probes
Explanation
Correct Answer
D:Breaking the existing family is not an IPv6 validation method. One address family's success does not validate the other.
Incorrect Answers
A:Advertised IPv6 routes still require valid forwarding resolution.
B:IPv6 needs its own supported reachability advertisement.
C:Link-state TLV content determines advertised IPv6 reachability.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests