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 25
Question 240
A fictional Junos service-provider engineer encounters this scenario: A service provider carries a customer's inner VLANs through an access network but the received service VLAN on an aggregation switch differs from the outer tag specified in the handoff. Distinguishing evidence: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. 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 (Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.) after independently checking (Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.), without quietly widening the provider or customer network scope. It does not match the current change: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.
An alternative approval would approve only the bounded change (Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.) after independently checking (Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers and Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers, respectively.
The bounded proposal is: Approve only the bounded change (Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.) after independently checking (Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.
A separate release decision would approve only the bounded change (Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants.) after independently checking (Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure.), without quietly widening the provider or customer network scope. It does not match the current change: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.
Question 241
A fictional Junos service-provider engineer encounters this scenario: A managed campus uplink has working same-VLAN bridging but customers cannot reach a routed service gateway on the Junos logical IRB interface. Distinguishing 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. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: C
Another proposed action is: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions. That does not directly address the observed condition: 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 more targeted correction is: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.
Another proposed action is: Verify peering transport addresses, configured peer ASN, reachability and authentication, then correct only the approved BGP neighbor endpoint. It targets a different dependency; the evidence here is 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 issue turns on 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 relevant rule is that Integrated routing and bridging requires correct VLAN membership and a corresponding L3 IRB interface. The targeted correction is: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.
That alternative concerns: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership. The relevant evidence is 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 corresponding fix is: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.
Question 242
A fictional Junos service-provider engineer encounters this scenario: A managed campus uplink has working same-VLAN bridging but customers cannot reach a routed service gateway on the Junos logical IRB interface. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: B
This other option describes: MAC forwarding tables on the access switch show the customer source learned on an unexpected access port and no destination learning for the intended bridge domain. The problem to explain is different: 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 record points to 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. After confirming the clue, the appropriate response is: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.
Another piece of evidence concerns Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The current incident instead shows: 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. This distinction supports the action: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.
Another alternative would address Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts as decisive. The actual evidence in this case is 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.
Question 243
A fictional Junos service-provider engineer encounters this scenario: A managed campus uplink has working same-VLAN bridging but customers cannot reach a routed service gateway on the Junos logical IRB interface. Distinguishing 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. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: C
The competing option invokes: 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 is: 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 case-relevant principle is: Integrated routing and bridging requires correct VLAN membership and a corresponding L3 IRB interface.
That principle concerns another fact pattern: Layer 2 forwarding decisions use learned MAC destinations within the appropriate VLAN or virtual switch. Evidence for this case: MAC forwarding tables on the access switch show the customer source learned on an unexpected access port and no destination learning for the intended bridge domain. Here the key fact is: 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.
Integrated routing and bridging requires correct VLAN membership and a corresponding L3 IRB interface. The recorded evidence is: 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 corresponding action is: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.
This alternative 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 governing distinction for the recorded case is Integrated routing and bridging requires correct VLAN membership and a corresponding L3 IRB interface.
Question 244
A fictional Junos service-provider engineer encounters this scenario: A managed campus uplink has working same-VLAN bridging but customers cannot reach a routed service gateway on the Junos logical IRB interface. Intended bounded correction: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: A
The expected outcome is Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact. It links the scoped action to the documented condition: 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.
Passing that test would not establish resolution of the stated issue. The relevant proof is: Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.
That result would assess another condition: Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers. The correct criterion is directly linked to the finding: 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.
Another proposed result is: The session remains established over representative monitored intervals and loss testing confirms appropriate recovery behavior. It would not independently establish the required outcome: Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.
Question 245
A fictional Junos service-provider engineer encounters this scenario: A managed campus uplink has working same-VLAN bridging but customers cannot reach a routed service gateway on the Junos logical IRB interface. Distinguishing 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. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: C
This limitation concerns another setting: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks. The observed facts here make a different caution decisive: Attaching one IRB to multiple unrelated tenant segments can merge routed access and violate boundaries.
Another caution is: Changing reflector scope indiscriminately can create control-plane loops or excess prefix dissemination. The key risk in this case is: Attaching one IRB to multiple unrelated tenant segments can merge routed access and violate boundaries.
The risk to retain is: Attaching one IRB to multiple unrelated tenant segments can merge routed access and violate boundaries. The original evidence is 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; widening the change beyond it is not justified.
This limitation concerns another setting: A VLAN number is not sufficient tenant isolation if bridge domains and virtual-switch mappings are incorrectly shared. The observed facts here make a different caution decisive: Attaching one IRB to multiple unrelated tenant segments can merge routed access and violate boundaries.
Question 246
A fictional Junos service-provider engineer encounters this scenario: A managed campus uplink has working same-VLAN bridging but customers cannot reach a routed service gateway on the Junos logical IRB interface. Distinguishing 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. 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: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. It does not directly establish the reported condition: 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.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed 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.
The pre-change check should compare active Junos routing, protocol and forwarding displays with this differentiating observed 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. That check directly concerns 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.
Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. It does not directly establish the reported condition: 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.
Question 247
A fictional Junos service-provider engineer encounters this scenario: A managed campus uplink has working same-VLAN bridging but customers cannot reach a routed service gateway on the Junos logical IRB interface. Distinguishing 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. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: D
Another possible combination is: First verify the observed failure (Reflector peer listings show one intended client configured as an ordinary peer and the route advertisements lack the expected client reflection behavior.); review and authorize the bounded correction (Confirm route-reflector client groups, cluster design and route-policy boundaries, then correct the selected client relationship only.); then independently verify the intended outcome (The relevant routes propagate to authorized internal BGP clients without duplicating unintended advertisements or exporting customer-private routes.) before production rollout. The current record instead supports Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility, verified by Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.
Another potential sequence is: First verify the observed failure (Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.); review and authorize the bounded correction (Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.); then independently verify the intended outcome (Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.) before production rollout. It has no direct link to the distinguishing 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.
Another action-and-check pairing is: First verify the observed failure (Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.); review and authorize the bounded correction (Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.); then independently verify the intended outcome (The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.) before production rollout. The evidence here is 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 required action and proof are Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility and Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.
The correction is Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility. The matching proof is Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact. Both address the finding that 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.
Question 248
A fictional Junos service-provider engineer encounters this scenario: A managed campus uplink has working same-VLAN bridging but customers cannot reach a routed service gateway on the Junos logical IRB interface. Distinguishing 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. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: B
Another approval action is: Observed evidence (Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.), limited correction (Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.), independently measurable result (Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.). The relevant evidence and acceptance are 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 and Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact, respectively.
The approval decision should consider 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 specific proposal is: Observed 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.), limited correction (Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.), independently measurable result (Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.). Its measurable outcome is: Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.
An alternative release decision is: Observed evidence (Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.), limited correction (Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.), independently measurable result (The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.). It does not match the current change: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.
Another approval action 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 relevant evidence and acceptance are 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 and Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact, respectively.
Question 249
A fictional Junos service-provider engineer encounters this scenario: A managed campus uplink has working same-VLAN bridging but customers cannot reach a routed service gateway on the Junos logical IRB interface. Distinguishing 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. 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 (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. The intended change was Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility, and acceptance must still be judged against Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.
Another fallback concerns pausing changes, preserve the differentiating evidence (MAC forwarding tables on the access switch show the customer source learned on an unexpected access port and no destination learning for the intended bridge domain.), restore the last approved safe network state and reassess mac-learning issue is confused with upstream bgp routing. The current change concerns 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.
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: 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 bounded fallback is: 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.
Another option proposes: Pause changes, preserve the differentiating evidence (Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.), restore the last approved safe network state and reassess access port is accidentally configured to carry multiple tagged services. Its assumptions differ from the observed failure; the appropriate recovery is: 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.
Question 250
A fictional Junos service-provider engineer encounters this scenario: A managed campus uplink has working same-VLAN bridging but customers cannot reach a routed service gateway on the Junos logical IRB interface. Distinguishing 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. 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 (Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.) after independently checking (Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.), without quietly widening the provider or customer network scope. The evidence for this scope is 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.
A separate release decision would approve only the bounded change (Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.) after independently checking (Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.), without quietly widening the provider or customer network scope. It does not match the current change: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.
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 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 and Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact, respectively.
Another proposed approval 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. The present scope must instead be justified by 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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 23 - 10 Questions (Last Reviewed 27-Oct-2026)
- Juniper JN0-364 Practice Test 24 - 10 Questions (Last Reviewed 26-Oct-2026)
- Juniper JN0-364 Practice Test 25 - 10 Questions (Last Reviewed 25-Oct-2026)
- Juniper JN0-364 Practice Test 26 - 10 Questions (Last Reviewed 24-Oct-2026)
- Juniper JN0-364 Practice Test 27 - 10 Questions (Last Reviewed 23-Oct-2026)