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 20
Question 190
A fictional Junos service-provider engineer encounters this scenario: Two upstream paths reach one destination but the selected BGP route does not match the shortest interface-level IGP metric that an operator expected. Distinguishing evidence: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: A
The change-control boundary is: Approve only the bounded change (Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path.) after independently checking (The chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.), without quietly widening the provider or customer network scope. The evidence for this scope is Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
A separate release decision would approve only the bounded change (Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only.) after independently checking (The relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes.), without quietly widening the provider or customer network scope. It does not match the current change: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path.
An alternative approval would approve only the bounded change (Verify peering transport addresses, configured peer ASN, reachability and authentication, then correct only the approved BGP neighbor endpoint.) after independently checking (The expected external session reaches Established and exchanges only agreed IPv4 routes with stable uptime.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy and the chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream, respectively.
Another proposed approval would approve only the bounded change (Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.) after independently checking (The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
Question 191
A fictional Junos service-provider engineer encounters this scenario: A regional provider migrates to route-reflector topology but some clients fail to receive routes from other clients despite established sessions. Distinguishing evidence: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: D
Another proposed action is: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology. That does not directly address the observed condition: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. The more targeted correction is: Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only.
Another proposed action is: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path. It targets a different dependency; the evidence here is Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
Another option proposes: Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal. The specific correction is: Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only. The deciding evidence is: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
The evidence is Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. The relevant principle is that IBGP route reflection relies on explicit client relationships and correct propagation semantics. The correction is: Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only. The separate success check is: The relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes.
Question 192
A fictional Junos service-provider engineer encounters this scenario: A regional provider migrates to route-reflector topology but some clients fail to receive routes from other clients despite established sessions. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: B
Another piece of evidence concerns Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory. The current incident instead shows: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. This distinction supports the action: Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only.
The deciding evidence is: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. This distinguishes the problem because IBGP route reflection relies on explicit client relationships and correct propagation semantics. The response it supports is: Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only.
This other option describes: Level-specific database comparisons show an expected peer LSP missing or stale while adjacency counters remain stable and reachable next hops persist. The problem to explain is different: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
Another proposed finding is: Received-route visibility shows the customer prefix, while the import policy match excludes its approved prefix length and the RIB lacks the route. It is not the recorded discriminator, which is Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
Question 193
A fictional Junos service-provider engineer encounters this scenario: A regional provider migrates to route-reflector topology but some clients fail to receive routes from other clients despite established sessions. Distinguishing evidence: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: D
A different principle is: BGP peering requires correctly addressed reachable transport endpoints and compatible session parameters. Evidence for this case: The neighboring router advertises a different source address from the one in the local configured BGP neighbor statement and logs show connection attempts to the obsolete IP. The present evidence, however, is Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. The relevant rule is: IBGP route reflection relies on explicit client relationships and correct propagation semantics.
This alternative invokes: BGP received routes are subject to policy before their acceptance and installation. Evidence for this case: Received-route visibility shows the customer prefix, while the import policy match excludes its approved prefix length and the RIB lacks the route. The governing distinction for the recorded case is IBGP route reflection relies on explicit client relationships and correct propagation semantics.
The competing option invokes: Junos access and trunk port behavior must align with the expected frame tagging of the attached peer. Evidence for this case: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The present evidence is: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. The case-relevant principle is: IBGP route reflection relies on explicit client relationships and correct propagation semantics.
IBGP route reflection relies on explicit client relationships and correct propagation semantics. This distinction accounts for Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior; another unrelated mechanism would not address the same condition.
Question 194
A fictional Junos service-provider engineer encounters this scenario: A regional provider migrates to route-reflector topology but some clients fail to receive routes from other clients despite established sessions. Intended bounded correction: Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: D
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: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
Another proposed result is: Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately. It would not independently establish the required outcome: The relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes.
A different option checks: The session remains established over representative monitored intervals and loss testing confirms appropriate recovery behavior. The case-specific acceptance condition is instead the relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes.
The independent verification condition is: The relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes. That result checks whether the original evidence—Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior—has been addressed.
Question 195
A fictional Junos service-provider engineer encounters this scenario: A regional provider migrates to route-reflector topology but some clients fail to receive routes from other clients despite established sessions. Distinguishing evidence: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: A
The risk to retain is: Changing reflector scope indiscriminately can create control-plane loops or excess prefix dissemination. The original evidence is Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior; widening the change beyond it is not justified.
This limitation concerns another setting: Editing MSTP instance mappings without confirming region consistency can cause boundary behavior and a wider service outage. The observed facts here make a different caution decisive: Changing reflector scope indiscriminately can create control-plane loops or excess prefix dissemination.
Another caution is: Changing OSPF cost to fix a policy-driven BGP preference can disrupt other routes without changing the actual decision factor. The key risk in this case is: Changing reflector scope indiscriminately can create control-plane loops or excess prefix dissemination.
Another emphasis concerns: Excessively lengthening timers to mask dropped keepalives can delay detection of real peer failure. The current change is Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only; the material limitation is Changing reflector scope indiscriminately can create control-plane loops or excess prefix dissemination.
Question 196
A fictional Junos service-provider engineer encounters this scenario: A regional provider migrates to route-reflector topology but some clients fail to receive routes from other clients despite established sessions. Distinguishing evidence: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: A
The focused investigation should 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 is tied to the 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 tests the conditions for this response: Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only.
Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Peer history contains hold timer expirations and packet captures show sporadic missing keepalives during a saturated control-plane event. It does not directly establish the reported condition: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory. The case-relevant check is: 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.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The case observation to isolate is Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. The focused check here is: 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.
Question 197
A fictional Junos service-provider engineer encounters this scenario: A regional provider migrates to route-reflector topology but some clients fail to receive routes from other clients despite established sessions. Distinguishing evidence: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: A
The case evidence indicates: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. Apply the scoped action: Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only. Confirm its effect independently: The relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes.
An alternative plan is: First verify the observed failure (Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.); review and authorize the bounded correction (Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path.); then independently verify the intended outcome (The chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.) before production rollout. It does not test the case-specific condition: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
Another possible combination is: First verify the observed failure (The neighboring router advertises a different source address from the one in the local configured BGP neighbor statement and logs show connection attempts to the obsolete IP.); review and authorize the bounded correction (Verify peering transport addresses, configured peer ASN, reachability and authentication, then correct only the approved BGP neighbor endpoint.); then independently verify the intended outcome (The expected external session reaches Established and exchanges only agreed IPv4 routes with stable uptime.) before production rollout. The current record instead supports Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only, verified by the relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes.
Another potential sequence is: First verify the observed failure (Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.); review and authorize the bounded correction (Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.); then independently verify the intended outcome (Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.) before production rollout. It has no direct link to the distinguishing evidence: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
Question 198
A fictional Junos service-provider engineer encounters this scenario: A regional provider migrates to route-reflector topology but some clients fail to receive routes from other clients despite established sessions. Distinguishing evidence: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: A
The approval decision should consider Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. The specific proposal is: Observed evidence (Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.), limited correction (Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only.), independently measurable result (The relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes.). Its measurable outcome is: The relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes.
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 Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior and the relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes, respectively.
Another approval package concerns: Observed evidence (RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.), limited correction (Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.), independently measurable result (The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.). The present scope must instead be justified by Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
An alternative release decision is: Observed evidence (Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.), limited correction (Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path.), independently measurable result (The chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.). It does not match the current change: Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only.
Question 199
A fictional Junos service-provider engineer encounters this scenario: A regional provider migrates to route-reflector topology but some clients fail to receive routes from other clients despite established sessions. Distinguishing evidence: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: A
If the change fails acceptance, the bounded recovery is: Pause changes, preserve the differentiating evidence (Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.), restore the last approved safe network state and reassess ibgp full-mesh assumption breaks after adding a route reflector. The case-specific risk is Changing reflector scope indiscriminately can create control-plane loops or excess prefix dissemination. The original evidence remains: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
Another option proposes: Pause changes, preserve the differentiating evidence (Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.), restore the last approved safe network state and reassess bgp best path differs from an operator's simple metric assumption. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.), restore the last approved safe network state and reassess ibgp full-mesh assumption breaks after adding a route reflector.
Another fallback concerns pausing changes, preserve the differentiating evidence (Peer history contains hold timer expirations and packet captures show sporadic missing keepalives during a saturated control-plane event.), restore the last approved safe network state and reassess bgp keepalive hold-time expectations do not match session state. The current change concerns Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
Another recovery route would pause changes, preserve the differentiating evidence (MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration.), restore the last approved safe network state and reassess mstp instance mapping creates an unexpected blocked path. It does not preserve the condition of this case: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. The bounded fallback is: Pause changes, preserve the differentiating evidence (Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.), restore the last approved safe network state and reassess ibgp full-mesh assumption breaks after adding a route reflector.
Question 200
A fictional Junos service-provider engineer encounters this scenario: A regional provider migrates to route-reflector topology but some clients fail to receive routes from other clients despite established sessions. Distinguishing evidence: Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: C
An alternative approval would approve only the bounded change (Review the prefix-length and routing-policy terms, allow only the contracted prefix range and verify the actual import result.) after independently checking (The authorized customer route becomes usable and adjacent unapproved prefixes remain rejected at the policy boundary.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior and the relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes, respectively.
Another proposed approval 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. The present scope must instead be justified by Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
The change-control boundary is: Approve only the bounded change (Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only.) after independently checking (The relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes.), without quietly widening the provider or customer network scope. The evidence for this scope is Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.
An alternative approval would approve only the bounded change (Investigate transport reliability, control-plane load and negotiated timer behavior before adjusting route filters or hold time.) after independently checking (The session remains established over representative monitored intervals and loss testing confirms appropriate recovery behavior.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior and the relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes, respectively.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 18 - 10 Questions (Last Reviewed 01-Nov-2026)
- Juniper JN0-364 Practice Test 19 - 10 Questions (Last Reviewed 31-Oct-2026)
- Juniper JN0-364 Practice Test 20 - 10 Questions (Last Reviewed 30-Oct-2026)
- Juniper JN0-364 Practice Test 21 - 10 Questions (Last Reviewed 29-Oct-2026)
- Juniper JN0-364 Practice Test 22 - 10 Questions (Last Reviewed 28-Oct-2026)