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 26
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.
Question 251
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Distinguishing 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. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: D
Another proposed action is: Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again. That does not directly address the observed condition: 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 more targeted correction is: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.
Another proposed action is: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility. It targets a different dependency; the evidence here is 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.
Another option proposes: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership. The specific correction is: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions. The deciding evidence is: 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 evidence is 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 relevant principle is that Layer 2 forwarding decisions use learned MAC destinations within the appropriate VLAN or virtual switch. The correction is: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions. The separate success check is: Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.
Question 252
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: B
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: 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. This distinction supports the action: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.
The deciding evidence is: 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. This distinguishes the problem because Layer 2 forwarding decisions use learned MAC destinations within the appropriate VLAN or virtual switch. The response it supports is: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.
This other option describes: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The problem to explain is different: 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.
Another proposed finding is: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. It is not the recorded discriminator, which is 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.
Question 253
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Distinguishing 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. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
A different principle is: IBGP route reflection relies on explicit client relationships and correct propagation semantics. Evidence for 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 present evidence, however, is 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 relevant rule is: Layer 2 forwarding decisions use learned MAC destinations within the appropriate VLAN or virtual switch.
The relevant principle is: Layer 2 forwarding decisions use learned MAC destinations within the appropriate VLAN or virtual switch. The case evidence is 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 practical response is: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.
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: 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 case-relevant principle is: Layer 2 forwarding decisions use learned MAC destinations within the appropriate VLAN or virtual switch.
That principle concerns another fact pattern: 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. Here the key fact is: 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.
Question 254
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Intended bounded correction: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: C
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 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.
Another proposed result is: Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries. It would not independently establish the required outcome: Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.
The expected outcome is Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers. It links the scoped action to the documented condition: 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.
Passing that test would not establish resolution of the stated issue. The relevant proof is: Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.
Question 255
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Distinguishing 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. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: A
The risk to retain is: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks. The original evidence is 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; widening the change beyond it is not justified.
This limitation concerns another setting: Removing outer tags indiscriminately can merge customer broadcast domains and break provider-bridging isolation. The observed facts here make a different caution decisive: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks.
Another caution is: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration. The key risk in this case is: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks.
Another emphasis concerns: Attaching one IRB to multiple unrelated tenant segments can merge routed access and violate boundaries. The current change is Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions; the material limitation is an unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks.
Question 256
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Distinguishing 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. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: B
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. The case observation to isolate is 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 focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed 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.
The pre-change check should compare active Junos routing, protocol and forwarding displays with this differentiating observed 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. That check directly concerns 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.
That check concerns a different signal: 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. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed 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.
Another check would 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 case observation to isolate is 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 focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed 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.
Question 257
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Distinguishing 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. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: B
Another action-and-check pairing is: First verify the observed failure (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.); review and authorize the bounded correction (Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility.); then independently verify the intended outcome (Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact.) before production rollout. The evidence here is 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 required action and proof are Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions and Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.
The correction is Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions. The matching proof is Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers. Both address the finding that 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.
Another possible combination 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. The current record instead supports Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions, verified by Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.
Another potential sequence 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. It has no direct link to the distinguishing 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.
Question 258
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Distinguishing 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. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: D
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: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.
Another approval action is: Observed evidence (Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.), limited correction (Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.), independently measurable result (The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.). The relevant evidence and acceptance are 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 and Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers, respectively.
Another approval package concerns: Observed evidence (Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.), limited correction (Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.), independently measurable result (Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.). The present scope must instead be justified by 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 approval decision should consider 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 specific proposal is: Observed 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.), limited correction (Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.), independently measurable result (Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.). Its measurable outcome is: Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.
Question 259
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Distinguishing 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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: C
Another recovery route would pause changes, preserve the differentiating evidence (Layer 2 logs show RSTP topology change and port role transition while BGP sessions remain established and their route tables are stable.), restore the last approved safe network state and reassess rstp convergence is blamed on an unrelated route policy. It does not preserve the condition of 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. The bounded fallback is: Pause 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.
Another option proposes: Pause changes, preserve the differentiating evidence (Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.), restore the last approved safe network state and reassess q-in-q outer tag does not match provider bridge service. Its assumptions differ from the observed failure; the appropriate recovery is: Pause 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.
A recovery option is to pause 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 intended change was Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions, and acceptance must still be judged against Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.
Another recovery route would 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. It does not preserve the condition of 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. The bounded fallback is: Pause 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.
Question 260
A fictional Junos service-provider engineer encounters this scenario: A wholesale Layer 2 customer reports one-way Ethernet delivery even though upstream BGP peers are healthy on the transport provider edge. Distinguishing 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. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: D
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 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 and Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers, respectively.
Another proposed 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 present scope must instead be justified by 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.
A separate release decision would 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. It does not match the current change: Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.
The bounded proposal is: 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. The separate acceptance measure remains: Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- 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)
- Juniper JN0-364 Practice Test 28 - 10 Questions (Last Reviewed 22-Oct-2026)