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 19
Question 180
A fictional Junos service-provider engineer encounters this scenario: A service provider accepts a BGP peering session but a customer-specific prefix is absent from active route selection after a new import policy is attached. Distinguishing evidence: Received-route visibility shows the customer prefix, while the import policy match excludes its approved prefix length and the RIB lacks the route. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: C
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: Review the prefix-length and routing-policy terms, allow only the contracted prefix range and verify the actual import result.
An alternative approval would approve only the bounded change (Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.) after independently checking (The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Received-route visibility shows the customer prefix, while the import policy match excludes its approved prefix length and the RIB lacks the route and the authorized customer route becomes usable and adjacent unapproved prefixes remain rejected at the policy boundary, respectively.
The bounded proposal is: 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 separate acceptance measure remains: The authorized customer route becomes usable and adjacent unapproved prefixes remain rejected at the policy boundary.
A separate release decision 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. It does not match the current change: Review the prefix-length and routing-policy terms, allow only the contracted prefix range and verify the actual import result.
Question 181
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 specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: B
Another proposed action is: Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal. That does not directly address the observed condition: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The more targeted correction is: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path.
The evidence is Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The relevant principle is that BGP path selection includes ordered attributes and import policy, not just underlay metric. The correction is: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path. The separate success check is: The chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.
Another option proposes: Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology. The specific correction is: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path. The deciding evidence is: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
That alternative concerns: Verify peering transport addresses, configured peer ASN, reachability and authentication, then correct only the approved BGP neighbor endpoint. The relevant evidence is Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The corresponding fix is: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path.
Question 182
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. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: A
Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. That fact identifies the relevant dependency, rather than a separate issue. BGP path selection includes ordered attributes and import policy, not just underlay metric.
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 Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
Another piece of evidence concerns Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. The current incident instead shows: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. This distinction supports the action: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path.
Another alternative would address Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory as decisive. The actual evidence in this case is Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
Question 183
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 Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: D
The competing option invokes: Integrated routing and bridging requires correct VLAN membership and a corresponding L3 IRB interface. Evidence for this case: MAC learning within the broadcast domain is healthy while the IRB logical interface or VLAN-to-IRB binding is missing or mapped to another tenant VLAN. The present evidence is: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The case-relevant principle is: BGP path selection includes ordered attributes and import policy, not just underlay metric.
That principle concerns another fact pattern: BGP export policy must explicitly control which routing information crosses external administrative boundaries. Evidence for this case: Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory. Here the key fact is: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
A different principle is: BGP hold timers and KEEPALIVE messages provide session liveness independent of accepted route policies. Evidence for this case: Peer history contains hold timer expirations and packet captures show sporadic missing keepalives during a saturated control-plane event. The present evidence, however, is Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The relevant rule is: BGP path selection includes ordered attributes and import policy, not just underlay metric.
The relevant principle is: BGP path selection includes ordered attributes and import policy, not just underlay metric. The case evidence is Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The practical response is: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path.
Question 184
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. Intended bounded correction: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: D
A different option checks: Representative destinations use the intended ring path and link utilization remains within the approved operational envelope. The case-specific acceptance condition is instead the chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.
Passing that test would not establish resolution of the stated issue. The relevant proof is: The chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.
That result would assess another condition: The expected external session reaches Established and exchanges only agreed IPv4 routes with stable uptime. The correct criterion is directly linked to the finding: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
The chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream. This verifies the required result rather than merely stating the action; the original issue was Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
Question 185
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 material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: B
This limitation concerns another setting: Changing reflector scope indiscriminately can create control-plane loops or excess prefix dissemination. The observed facts here make a different caution decisive: Changing OSPF cost to fix a policy-driven BGP preference can disrupt other routes without changing the actual decision factor.
Changing OSPF cost to fix a policy-driven BGP preference can disrupt other routes without changing the actual decision factor. That boundary protects the documented change, Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path, from introducing an unrelated problem.
Another emphasis concerns: Blindly restarting IS-IS on every router can add topology disruption without proving database cause. The current change is Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path; the material limitation is Changing OSPF cost to fix a policy-driven BGP preference can disrupt other routes without changing the actual decision factor.
This limitation concerns another setting: Excessively lengthening timers to mask dropped keepalives can delay detection of real peer failure. The observed facts here make a different caution decisive: Changing OSPF cost to fix a policy-driven BGP preference can disrupt other routes without changing the actual decision factor.
Question 186
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 focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: D
Another investigation would 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. It does not directly establish the reported condition: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: 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 case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: LAN pseudonode and circuit detail show a DIS chosen using election criteria distinct from the SPF metric assigned to traffic paths. The case observation to isolate is Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
The current finding is Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The specific pre-change check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. Use it to distinguish the problem from an unrelated symptom.
Question 187
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 controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: C
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 Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path, verified by the chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.
Another potential sequence is: First verify the observed failure (Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.); review and authorize the bounded correction (Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.); then independently verify the intended outcome (A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.) before production rollout. It has no direct link to the distinguishing evidence: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
The case evidence indicates: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. Apply the scoped action: Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path. Confirm its effect independently: The chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.
An alternative plan is: First verify the observed failure (Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory.); review and authorize the bounded correction (Apply a precise export filter and route-policy tests for public prefixes, then confirm rejected customer-only routes stay internal.); then independently verify the intended outcome (Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.) before production rollout. It does not test the case-specific condition: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
Question 188
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 set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: C
Another approval action is: Observed evidence (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.), limited correction (Verify peering transport addresses, configured peer ASN, reachability and authentication, then correct only the approved BGP neighbor endpoint.), independently measurable result (The expected external session reaches Established and exchanges only agreed IPv4 routes with stable uptime.). 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 approval package concerns: Observed evidence (Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.), limited correction (Verify domain-level design and configure the approved overlapping IS-IS level on the intended interface and routing instance.), independently measurable result (The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.). 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.
The change-control boundary 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.). 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.
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 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.
Question 189
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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: D
Another option proposes: Pause changes, preserve the differentiating evidence (MAC learning within the broadcast domain is healthy while the IRB logical interface or VLAN-to-IRB binding is missing or mapped to another tenant VLAN.), restore the last approved safe network state and reassess irb interface lacks a link to the correct vlan. Its assumptions differ from the observed failure; the appropriate recovery is: 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.
Another fallback concerns pausing changes, preserve the differentiating evidence (Received-route visibility shows the customer prefix, while the import policy match excludes its approved prefix length and the RIB lacks the route.), restore the last approved safe network state and reassess bgp route is received but not imported by policy. The current change concerns Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy.
Another recovery route would pause changes, preserve the differentiating evidence (Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory.), restore the last approved safe network state and reassess bgp export policy reveals a customer-only route to transit. It does not preserve the condition of this case: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The bounded fallback is: 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.
A recovery option is to 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. The intended change was Inspect applicable BGP best-path attributes and local routing policy before modifying any IGP metric or neighboring AS path, and acceptance must still be judged against the chosen path matches the documented policy intent and forwarding probes follow the selected healthy upstream.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 17 - 10 Questions (Last Reviewed 02-Nov-2026)
- 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)