100% Latest & Updated Juniper JN0-364 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 110
A remote router sees only intra-area topology records even though an external prefix should be visible through the backbone. Independently, the review flags the potentially unsafe practice “Assume a stub area must receive every Type 5 AS-external LSA”. Which validation addresses the risk without assuming a particular cause?
- Check ABR-originated Type 3 summary routes
- Inspect Type 5 presence and stub or NSSA area behavior
- Inspect Type 1 originator and flooding scope
- Assume every point-to-point interface must create a Type 2 network LSA
Explanation
Correct Answer
B:Stub area design suppresses ordinary external LSA flooding. External route flooding depends on policy and area design.
Incorrect Answers
A:Summary LSAs carry reachability across area boundaries.
C:Router LSAs describe area-local topology.
D:Point-to-point links do not rely on a DR-originated network LSA.
Question 111
An edge PE advertises a customer-facing /30 into OSPF but should not attempt to form routing neighbors with the customer's unmanaged router. The objective is to separate announcement from peering. Which Junos configuration or design action best satisfies the objective?
- Configure the customer interface passive while retaining the intended OSPF reachability
- Treat zero hellos as sufficient proof that destinations still route
- Mark every transport link passive as a blanket security action
- Accept OSPF neighbors from every customer access connection by default
Explanation
Correct Answer
A:Passive mode can advertise connected reachability without neighbor hellos.
Incorrect Answers
B:Passive success alone does not verify route propagation.
C:Passive transit links prevent intended OSPF adjacencies.
D:Unauthorized adjacency can inject incorrect topology.
Question 112
An edge PE advertises a customer-facing /30 into OSPF but should not attempt to form routing neighbors with the customer's unmanaged router. The objective is to check core-facing adjacency. Which operational choice should be prioritized in this design?
- Treat zero hellos as sufficient proof that destinations still route
- Delete the customer prefix entirely so no hello packets are sent
- Accept OSPF neighbors from every customer access connection by default
- Keep neighbor-forming OSPF enabled on the approved internal transport links
Explanation
Correct Answer
D:Core neighbors are necessary for internal route exchange.
Incorrect Answers
A:Passive success alone does not verify route propagation.
B:Removing reachability is not equivalent to suppressing adjacency.
C:Unauthorized adjacency can inject incorrect topology.
Question 113
An edge PE advertises a customer-facing /30 into OSPF but should not attempt to form routing neighbors with the customer's unmanaged router. The objective is to limit untrusted neighbor attempts. Which routing or switching control best fits the requirement?
- Treat zero hellos as sufficient proof that destinations still route
- Block unintended OSPF peering on access-facing boundaries
- Delete the customer prefix entirely so no hello packets are sent
- Mark every transport link passive as a blanket security action
Explanation
Correct Answer
B:Customer links often should not exchange IGP control messages.
Incorrect Answers
A:Passive success alone does not verify route propagation.
C:Removing reachability is not equivalent to suppressing adjacency.
D:Passive transit links prevent intended OSPF adjacencies.
Question 114
An edge PE advertises a customer-facing /30 into OSPF but should not attempt to form routing neighbors with the customer's unmanaged router. The objective is to verify route continues to propagate. Which verification should be performed before approving the change?
- Mark every transport link passive as a blanket security action
- Accept OSPF neighbors from every customer access connection by default
- Check receiving core route tables after changing an interface to passive
- Delete the customer prefix entirely so no hello packets are sent
Explanation
Correct Answer
C:Control-plane silence should not remove needed reachability.
Incorrect Answers
A:Passive transit links prevent intended OSPF adjacencies.
B:Unauthorized adjacency can inject incorrect topology.
D:Removing reachability is not equivalent to suppressing adjacency.
Question 115
An edge PE advertises a customer-facing /30 into OSPF but should not attempt to form routing neighbors with the customer's unmanaged router. Two objectives apply: (1) check core-facing adjacency; and (2) verify route continues to propagate. Which TWO controls together satisfy the requirements? Choose TWO.
- Accept OSPF neighbors from every customer access connection by default
- Keep neighbor-forming OSPF enabled on the approved internal transport links
- Mark every transport link passive as a blanket security action
- Check receiving core route tables after changing an interface to passive
- Delete the customer prefix entirely so no hello packets are sent
Explanation
Correct Answers
B:Core neighbors are necessary for internal route exchange.
D:Control-plane silence should not remove needed reachability.
Incorrect Answers
A:Unauthorized adjacency can inject incorrect topology.
C:Passive transit links prevent intended OSPF adjacencies.
E:Removing reachability is not equivalent to suppressing adjacency.
Question 116
An edge PE advertises a customer-facing /30 into OSPF but should not attempt to form routing neighbors with the customer's unmanaged router. Three objectives apply: (1) separate announcement from peering; (2) check core-facing adjacency; and (3) verify route continues to propagate. Which THREE controls together satisfy the requirements? Choose THREE.
- Configure the customer interface passive while retaining the intended OSPF reachability
- Check receiving core route tables after changing an interface to passive
- Treat zero hellos as sufficient proof that destinations still route
- Keep neighbor-forming OSPF enabled on the approved internal transport links
- Delete the customer prefix entirely so no hello packets are sent
- Accept OSPF neighbors from every customer access connection by default
Explanation
Correct Answers
A:Passive mode can advertise connected reachability without neighbor hellos.
B:Control-plane silence should not remove needed reachability.
D:Core neighbors are necessary for internal route exchange.
Incorrect Answers
C:Passive success alone does not verify route propagation.
E:Removing reachability is not equivalent to suppressing adjacency.
F:Unauthorized adjacency can inject incorrect topology.
Question 117
Operations sees repeated OSPF hellos on a customer link where only prefix reachability was intended, not protocol adjacency. Independently, the review flags the potentially unsafe practice “Delete the customer prefix entirely so no hello packets are sent”. Which inspection best evaluates that practice?
- Treat zero hellos as sufficient proof that destinations still route
- Inspect passive-interface status and advertised network
- Verify internal core-facing neighbors remain Full
- Inspect interface role against authorized OSPF neighbor list
Explanation
Correct Answer
B:Removing reachability is not equivalent to suppressing adjacency. Passive mode can advertise connected reachability without neighbor hellos.
Incorrect Answers
A:Passive success alone does not verify route propagation.
C:Core neighbors are necessary for internal route exchange.
D:Customer links often should not exchange IGP control messages.
Question 118
Operations sees repeated OSPF hellos on a customer link where only prefix reachability was intended, not protocol adjacency. Independently, the review flags the potentially unsafe practice “Mark every transport link passive as a blanket security action”. Which evidence most directly tests the flagged assumption?
- Treat zero hellos as sufficient proof that destinations still route
- Inspect passive-interface status and advertised network
- Inspect interface role against authorized OSPF neighbor list
- Verify internal core-facing neighbors remain Full
Explanation
Correct Answer
D:Passive transit links prevent intended OSPF adjacencies. Core neighbors are necessary for internal route exchange.
Incorrect Answers
A:Passive success alone does not verify route propagation.
B:Passive mode can advertise connected reachability without neighbor hellos.
C:Customer links often should not exchange IGP control messages.
Question 119
Operations sees repeated OSPF hellos on a customer link where only prefix reachability was intended, not protocol adjacency. Independently, the review flags the potentially unsafe practice “Accept OSPF neighbors from every customer access connection by default”. Which diagnostic check tests this potentially unsafe choice?
- Inspect passive-interface status and advertised network
- Mark every transport link passive as a blanket security action
- Inspect interface role against authorized OSPF neighbor list
- Inspect advertised prefix and remote reachability after change
Explanation
Correct Answer
C:Unauthorized adjacency can inject incorrect topology. Customer links often should not exchange IGP control messages.
Incorrect Answers
A:Passive mode can advertise connected reachability without neighbor hellos.
B:Passive transit links prevent intended OSPF adjacencies.
D:Control-plane silence should not remove needed reachability.
Question 120
Operations sees repeated OSPF hellos on a customer link where only prefix reachability was intended, not protocol adjacency. Independently, the review flags the potentially unsafe practice “Treat zero hellos as sufficient proof that destinations still route”. Which validation addresses the risk without assuming a particular cause?
- Verify internal core-facing neighbors remain Full
- Inspect passive-interface status and advertised network
- Inspect advertised prefix and remote reachability after change
- Accept OSPF neighbors from every customer access connection by default
Explanation
Correct Answer
C:Passive success alone does not verify route propagation. Control-plane silence should not remove needed reachability.
Incorrect Answers
A:Core neighbors are necessary for internal route exchange.
B:Passive mode can advertise connected reachability without neighbor hellos.
D:Unauthorized adjacency can inject incorrect topology.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests