Pass Juniper JN0-364 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Juniper JN0-364 Practice Test 10
Question 90
A fictional Junos service-provider engineer encounters this scenario: An engineer sees a newly announced router LSA for a remote subnet but believes the prefix must appear in the active forwarding table immediately. Distinguishing evidence: OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: D
A separate release decision would approve only the bounded change (Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.) after independently checking (The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.), without quietly widening the provider or customer network scope. It does not match the current change: Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.
An alternative approval would approve only the bounded change (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.) after independently checking (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination and Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route, respectively.
Another proposed approval would approve only the bounded change (Check approved liveness requirements and align the interface hello and dead parameters on both adjacent devices before committing.) after independently checking (The neighbor remains full through several monitored intervals, while routing reconverges predictably on a controlled link loss.), without quietly widening the provider or customer network scope. The present scope must instead be justified by OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination.
The approval decision should consider OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination. The specific proposal is: Approve only the bounded change (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.) after independently checking (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.), without quietly widening the provider or customer network scope. Its measurable outcome is: Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.
Question 91
A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Distinguishing evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: C
Another proposed action is: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration. That does not directly address the observed condition: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The more targeted correction is: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.
Another proposed action is: Check approved liveness requirements and align the interface hello and dead parameters on both adjacent devices before committing. It targets a different dependency; the evidence here is Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
The issue turns on Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The relevant rule is that Controlled OSPF route redistribution is governed by route policy and explicit eligible prefix matches. The targeted correction is: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.
That alternative concerns: Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters. The relevant evidence is Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The corresponding fix is: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.
Question 92
A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: D
Another piece of evidence concerns OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination. The current incident instead shows: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. This distinction supports the action: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.
Another alternative would address OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned as decisive. The actual evidence in this case is Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
This other option describes: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The problem to explain is different: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
The record points to Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. After confirming the clue, the appropriate response is: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.
Question 93
A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Distinguishing evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
A different principle is: IS-IS LAN DIS election and shortest-path metrics are distinct control-plane mechanisms. Evidence for this case: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The present evidence, however, is Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The relevant rule is: Controlled OSPF route redistribution is governed by route policy and explicit eligible prefix matches.
The relevant principle is: Controlled OSPF route redistribution is governed by route policy and explicit eligible prefix matches. The case evidence is Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The practical response is: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.
The competing option invokes: OSPF link-state advertisement data and active routing-table installation are different diagnostic layers. Evidence for this case: OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination. The present evidence is: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The case-relevant principle is: Controlled OSPF route redistribution is governed by route policy and explicit eligible prefix matches.
That principle concerns another fact pattern: Protocol troubleshooting must use the correct routing-instance and route-table context. Evidence for this case: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. Here the key fact is: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
Question 94
A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Intended bounded correction: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: B
That result would assess another condition: The authorized customer route becomes usable and adjacent unapproved prefixes remain rejected at the policy boundary. The correct criterion is directly linked to the finding: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised. This verifies the required result rather than merely stating the action; the original issue was Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
A different option checks: Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero. The case-specific acceptance condition is instead Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.
Passing that test would not establish resolution of the stated issue. The relevant proof is: Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.
Question 95
A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Distinguishing evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: A
The risk to retain is: Adding a blanket export accept can redistribute routes that are not part of the contracted service. The original evidence is Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term; widening the change beyond it is not justified.
Another caution is: A filter term matching too broadly can redirect critical control-plane and operations traffic to the wrong path. The key risk in this case is: Adding a blanket export accept can redistribute routes that are not part of the contracted service.
Another emphasis concerns: Treating expected two-way neighbor states as faults can trigger unnecessary election changes and route churn. The current change is Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions; the material limitation is Adding a blanket export accept can redistribute routes that are not part of the contracted service.
This limitation concerns another setting: Globally modifying OSPF area design to fix one mismatched interface can disrupt a wider provider routing domain. The observed facts here make a different caution decisive: Adding a blanket export accept can redistribute routes that are not part of the contracted service.
Question 96
A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Distinguishing evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: C
Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned. It does not directly establish the reported condition: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
The pre-change check should compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. That check directly concerns Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. It does not directly establish the reported condition: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
Question 97
A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Distinguishing evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: D
Another action-and-check pairing is: First verify the observed failure (Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.); review and authorize the bounded correction (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.); then independently verify the intended outcome (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.) before production rollout. The evidence here is Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The required action and proof are Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions and Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.
An alternative plan is: First verify the observed failure (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.); review and authorize the bounded correction (Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.); then independently verify the intended outcome (Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.) before production rollout. It does not test the case-specific condition: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
Another possible combination is: First verify the observed failure (The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.); review and authorize the bounded correction (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.); then independently verify the intended outcome (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.) before production rollout. The current record instead supports Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions, verified by Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.
The starting point is Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The proposed action and its separate check are Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions and Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised, respectively.
Question 98
A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Distinguishing evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: A
The bounded proposal is: Observed evidence (Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.), limited correction (Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.), independently measurable result (Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.). The separate acceptance measure remains: Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.
Another approval package concerns: Observed evidence (OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned.), limited correction (Check approved liveness requirements and align the interface hello and dead parameters on both adjacent devices before committing.), independently measurable result (The neighbor remains full through several monitored intervals, while routing reconverges predictably on a controlled link loss.). The present scope must instead be justified by Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
An alternative release decision is: Observed evidence (OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination.), limited correction (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.), independently measurable result (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.). It does not match the current change: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.
Another approval action is: Observed evidence (Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory.), limited correction (Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal.), independently measurable result (Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.). The relevant evidence and acceptance are Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term and Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised, respectively.
Question 99
A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Distinguishing evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: A
A recovery option is to pause changes, preserve the differentiating evidence (Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.), restore the last approved safe network state and reassess ospf import policy blocks a needed external route. The intended change was Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions, and acceptance must still be judged against Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.
Another fallback concerns pausing changes, preserve the differentiating evidence (BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.), restore the last approved safe network state and reassess aggregate route hides a needed more-specific reachability signal. The current change concerns Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
Another recovery route would pause changes, preserve the differentiating evidence (The interface is a broadcast multiaccess network with elected DR and BDR and the newcomer has low priority; neighbor output shows full adjacency to elected routers.), restore the last approved safe network state and reassess dr and bdr expectations are confused on shared ethernet. It does not preserve the condition of this case: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The bounded fallback is: Pause changes, preserve the differentiating evidence (Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.), restore the last approved safe network state and reassess ospf import policy blocks a needed external route.
Another option proposes: Pause changes, preserve the differentiating evidence (OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned.), restore the last approved safe network state and reassess hello and dead interval mismatch causes ospf neighbor instability. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.), restore the last approved safe network state and reassess ospf import policy blocks a needed external route.
Question 100
A fictional Junos service-provider engineer encounters this scenario: A provider edge learns an external prefix from another protocol but its OSPF neighbors never receive the intended authorized service route. Distinguishing evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: D
Another proposed approval would approve only the bounded change (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.) after independently checking (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
A separate release decision would approve only the bounded change (Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal.) after independently checking (Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.), without quietly widening the provider or customer network scope. It does not match the current change: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.
An alternative approval would approve only the bounded change (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.) after independently checking (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term and Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised, respectively.
The change-control boundary is: Approve only the bounded change (Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.) after independently checking (Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.), without quietly widening the provider or customer network scope. The evidence for this scope is Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 8 - 10 Questions (Last Reviewed 11-Nov-2026)
- Juniper JN0-364 Practice Test 9 - 10 Questions (Last Reviewed 10-Nov-2026)
- Juniper JN0-364 Practice Test 10 - 10 Questions (Last Reviewed 09-Nov-2026)
- Juniper JN0-364 Practice Test 11 - 10 Questions (Last Reviewed 08-Nov-2026)
- Juniper JN0-364 Practice Test 12 - 10 Questions (Last Reviewed 07-Nov-2026)