100% Latest & Updated Juniper JN0-364 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 30
A route change leaves an operator assuming the lowest hop count must win even though a different protocol route is active. Independently, the review flags the potentially unsafe practice “Conclude that a route advertises correctly solely from its configuration stanza”. Which validation addresses the risk without assuming a particular cause?
- Inspect route preference values for competing candidate entries
- Read hidden-route reason and next-hop resolution output
- Inspect forwarding-table entry and actual egress interface
- Pick a BGP path solely because its OSPF link metric is numerically lower
Explanation
Correct Answer
C:Configuration and data-plane installation require separate validation. Control-plane route selection must be reflected in forwarding state.
Incorrect Answers
A:Junos first compares route preferences across protocols.
B:An unusable next hop can make a route ineligible despite preference.
D:IGP metrics and BGP decision attributes are not interchangeable.
Question 31
A core router unexpectedly refuses to learn reachability for a reserved address block used in a test, and a change ticket proposes relaxing checks globally. The objective is to classify blocked prefixes. Which Junos configuration or design action best satisfies the objective?
- Remove every martian protection globally to get one lab prefix working
- Check whether the prefix is treated as martian or reserved by the current routing policy
- Assume absence from the active list proves the peer never sent the prefix
- Leave a permissive martian exception in production indefinitely
Explanation
Correct Answer
B:Martian handling prevents inappropriate addresses becoming ordinary routes.
Incorrect Answers
A:Global suppression can enable unintended reserved route acceptance.
C:Received routes can be hidden or rejected after import.
D:Unreviewed permanent exceptions weaken route acceptance rules.
Question 32
A core router unexpectedly refuses to learn reachability for a reserved address block used in a test, and a change ticket proposes relaxing checks globally. The objective is to avoid global exceptions. Which operational choice should be prioritized in this design?
- Leave a permissive martian exception in production indefinitely
- Treat all missing routes as harmless software display defects
- Limit any justified exception to the explicitly reviewed lab scope
- Assume absence from the active list proves the peer never sent the prefix
Explanation
Correct Answer
C:Broad overrides can make invalid reachability appear routable.
Incorrect Answers
A:Unreviewed permanent exceptions weaken route acceptance rules.
B:A rejected reserved prefix can be an intentional safeguard.
D:Received routes can be hidden or rejected after import.
Question 33
A core router unexpectedly refuses to learn reachability for a reserved address block used in a test, and a change ticket proposes relaxing checks globally. The objective is to check route visibility. Which routing or switching control best fits the requirement?
- Use detailed routing output to locate rejected or hidden route candidates
- Remove every martian protection globally to get one lab prefix working
- Leave a permissive martian exception in production indefinitely
- Treat all missing routes as harmless software display defects
Explanation
Correct Answer
A:A hidden route can explain why configuration and active RIB differ.
Incorrect Answers
B:Global suppression can enable unintended reserved route acceptance.
C:Unreviewed permanent exceptions weaken route acceptance rules.
D:A rejected reserved prefix can be an intentional safeguard.
Question 34
A core router unexpectedly refuses to learn reachability for a reserved address block used in a test, and a change ticket proposes relaxing checks globally. The objective is to validate after rollback. Which verification should be performed before approving the change?
- Restore normal martian filtering and test production prefixes still install
- Treat all missing routes as harmless software display defects
- Remove every martian protection globally to get one lab prefix working
- Assume absence from the active list proves the peer never sent the prefix
Explanation
Correct Answer
A:A temporary lab workaround must not outlive its controlled purpose.
Incorrect Answers
B:A rejected reserved prefix can be an intentional safeguard.
C:Global suppression can enable unintended reserved route acceptance.
D:Received routes can be hidden or rejected after import.
Question 35
A core router unexpectedly refuses to learn reachability for a reserved address block used in a test, and a change ticket proposes relaxing checks globally. Two objectives apply: (1) avoid global exceptions; and (2) validate after rollback. Which TWO controls together satisfy the requirements? Choose TWO.
- Leave a permissive martian exception in production indefinitely
- Limit any justified exception to the explicitly reviewed lab scope
- Assume absence from the active list proves the peer never sent the prefix
- Treat all missing routes as harmless software display defects
- Restore normal martian filtering and test production prefixes still install
Explanation
Correct Answers
B:Broad overrides can make invalid reachability appear routable.
E:A temporary lab workaround must not outlive its controlled purpose.
Incorrect Answers
A:Unreviewed permanent exceptions weaken route acceptance rules.
C:Received routes can be hidden or rejected after import.
D:A rejected reserved prefix can be an intentional safeguard.
Question 36
A core router unexpectedly refuses to learn reachability for a reserved address block used in a test, and a change ticket proposes relaxing checks globally. Three objectives apply: (1) classify blocked prefixes; (2) check route visibility; and (3) validate after rollback. Which THREE controls together satisfy the requirements? Choose THREE.
- Assume absence from the active list proves the peer never sent the prefix
- Check whether the prefix is treated as martian or reserved by the current routing policy
- Leave a permissive martian exception in production indefinitely
- Restore normal martian filtering and test production prefixes still install
- Use detailed routing output to locate rejected or hidden route candidates
- Treat all missing routes as harmless software display defects
Explanation
Correct Answers
B:Martian handling prevents inappropriate addresses becoming ordinary routes.
D:A temporary lab workaround must not outlive its controlled purpose.
E:A hidden route can explain why configuration and active RIB differ.
Incorrect Answers
A:Received routes can be hidden or rejected after import.
C:Unreviewed permanent exceptions weaken route acceptance rules.
F:A rejected reserved prefix can be an intentional safeguard.
Question 37
Operators find the reserved prefix missing from the active route table and plan to disable martian checks without reviewing its classification. Independently, the review flags the potentially unsafe practice “Treat all missing routes as harmless software display defects”. Which inspection best evaluates that practice?
- Inspect post-change policy and test permitted versus blocked destinations
- Inspect the current martian-route classification and matching prefix
- Remove every martian protection globally to get one lab prefix working
- Compare received routes with hidden or rejected route detail
Explanation
Correct Answer
B:A rejected reserved prefix can be an intentional safeguard. Martian handling prevents inappropriate addresses becoming ordinary routes.
Incorrect Answers
A:A temporary lab workaround must not outlive its controlled purpose.
C:Global suppression can enable unintended reserved route acceptance.
D:A hidden route can explain why configuration and active RIB differ.
Question 38
Operators find the reserved prefix missing from the active route table and plan to disable martian checks without reviewing its classification. Independently, the review flags the potentially unsafe practice “Remove every martian protection globally to get one lab prefix working”. Which evidence most directly tests the flagged assumption?
- Review the intended prefix and scope of a proposed exception
- Treat all missing routes as harmless software display defects
- Compare received routes with hidden or rejected route detail
- Inspect post-change policy and test permitted versus blocked destinations
Explanation
Correct Answer
A:Global suppression can enable unintended reserved route acceptance. Broad overrides can make invalid reachability appear routable.
Incorrect Answers
B:A rejected reserved prefix can be an intentional safeguard.
C:A hidden route can explain why configuration and active RIB differ.
D:A temporary lab workaround must not outlive its controlled purpose.
Question 39
Operators find the reserved prefix missing from the active route table and plan to disable martian checks without reviewing its classification. Independently, the review flags the potentially unsafe practice “Assume absence from the active list proves the peer never sent the prefix”. Which diagnostic check tests this potentially unsafe choice?
- Remove every martian protection globally to get one lab prefix working
- Compare received routes with hidden or rejected route detail
- Inspect the current martian-route classification and matching prefix
- Inspect post-change policy and test permitted versus blocked destinations
Explanation
Correct Answer
B:Received routes can be hidden or rejected after import. A hidden route can explain why configuration and active RIB differ.
Incorrect Answers
A:Global suppression can enable unintended reserved route acceptance.
C:Martian handling prevents inappropriate addresses becoming ordinary routes.
D:A temporary lab workaround must not outlive its controlled purpose.
Question 40
Operators find the reserved prefix missing from the active route table and plan to disable martian checks without reviewing its classification. Independently, the review flags the potentially unsafe practice “Leave a permissive martian exception in production indefinitely”. Which validation addresses the risk without assuming a particular cause?
- Compare received routes with hidden or rejected route detail
- Treat all missing routes as harmless software display defects
- Inspect post-change policy and test permitted versus blocked destinations
- Review the intended prefix and scope of a proposed exception
Explanation
Correct Answer
C:Unreviewed permanent exceptions weaken route acceptance rules. A temporary lab workaround must not outlive its controlled purpose.
Incorrect Answers
A:A hidden route can explain why configuration and active RIB differ.
B:A rejected reserved prefix can be an intentional safeguard.
D:Broad overrides can make invalid reachability appear routable.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests