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 23
Question 220
A fictional Junos service-provider engineer encounters this scenario: A managed service provider detects a customer RFC1918 reachability prefix advertised toward a public upstream during an emergency peer change. Distinguishing evidence: Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: B
Another proposed approval would approve only the bounded change (Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.) after independently checking (Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory.
The bounded proposal is: 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 separate acceptance measure remains: Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance.
An alternative approval would 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 relevant evidence and acceptance are Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory and Upstream advertised-route output contains only approved prefixes and the private customer destination remains available in its intended instance, respectively.
Another proposed approval would approve only the bounded change (Review the prefix-length and routing-policy terms, allow only the contracted prefix range and verify the actual import result.) after independently checking (The authorized customer route becomes usable and adjacent unapproved prefixes remain rejected at the policy boundary.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory.
Question 221
A fictional Junos service-provider engineer encounters this scenario: A wholesale handoff intended for one untagged customer VLAN starts dropping frames after a field technician changes the physical interface to tagged trunk mode. Distinguishing evidence: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: D
Another proposed action is: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership. That does not directly address the observed condition: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The more targeted correction is: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.
Another proposed action is: Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants. It targets a different dependency; the evidence here is Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
Another option proposes: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility. The specific correction is: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership. The deciding evidence is: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
The evidence is Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The relevant principle is that Junos access and trunk port behavior must align with the expected frame tagging of the attached peer. The correction is: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership. The separate success check is: The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.
Question 222
A fictional Junos service-provider engineer encounters this scenario: A wholesale handoff intended for one untagged customer VLAN starts dropping frames after a field technician changes the physical interface to tagged trunk mode. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: B
This other option describes: Routing table attributes show unequal local preference or other policy-driven BGP path attributes, while transport paths remain healthy. The problem to explain is different: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
The record points to Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. After confirming the clue, the appropriate response is: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.
Another piece of evidence concerns Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The current incident instead shows: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. This distinction supports the action: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.
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 Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
Question 223
A fictional Junos service-provider engineer encounters this scenario: A wholesale handoff intended for one untagged customer VLAN starts dropping frames after a field technician changes the physical interface to tagged trunk mode. Distinguishing evidence: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: C
The competing option invokes: Junos virtual-switch and bridge-domain scoping determine the actual Layer 2 forwarding boundary. Evidence for this case: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. The present evidence is: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The case-relevant principle is: Junos access and trunk port behavior must align with the expected frame tagging of the attached peer.
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: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
Junos access and trunk port behavior must align with the expected frame tagging of the attached peer. The recorded evidence is: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The corresponding action is: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.
This alternative invokes: Spanning-tree BPDU protection is a deliberate safety mechanism against unexpected bridge advertisements. Evidence for this case: Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error. The governing distinction for the recorded case is Junos access and trunk port behavior must align with the expected frame tagging of the attached peer.
Question 224
A fictional Junos service-provider engineer encounters this scenario: A wholesale handoff intended for one untagged customer VLAN starts dropping frames after a field technician changes the physical interface to tagged trunk mode. Intended bounded correction: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: D
A different option checks: Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure. The case-specific acceptance condition is instead the customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.
Passing that test would not establish resolution of the stated issue. The relevant proof is: The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.
That result would assess another condition: Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries. The correct criterion is directly linked to the finding: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs. This verifies the required result rather than merely stating the action; the original issue was Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
Question 225
A fictional Junos service-provider engineer encounters this scenario: A wholesale handoff intended for one untagged customer VLAN starts dropping frames after a field technician changes the physical interface to tagged trunk mode. Distinguishing evidence: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: D
Another emphasis concerns: A VLAN number is not sufficient tenant isolation if bridge domains and virtual-switch mappings are incorrectly shared. The current change is Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership; the material limitation is Misaligned port tagging can create a service outage or expose unrelated VLANs through an overly broad trunk.
This limitation concerns another setting: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration. The observed facts here make a different caution decisive: Misaligned port tagging can create a service outage or expose unrelated VLANs through an overly broad trunk.
Another caution is: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks. The key risk in this case is: Misaligned port tagging can create a service outage or expose unrelated VLANs through an overly broad trunk.
A necessary safeguard is: Misaligned port tagging can create a service outage or expose unrelated VLANs through an overly broad trunk. The proposed correction remains: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.
Question 226
A fictional Junos service-provider engineer encounters this scenario: A wholesale handoff intended for one untagged customer VLAN starts dropping frames after a field technician changes the physical interface to tagged trunk mode. Distinguishing evidence: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. 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: Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts. The case observation to isolate is Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The focused check here is: 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 pre-change check should 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. That check directly concerns Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
That check concerns a different signal: 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 case-relevant check is: 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.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. The case observation to isolate is Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The focused check here is: 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.
Question 227
A fictional Junos service-provider engineer encounters this scenario: A wholesale handoff intended for one untagged customer VLAN starts dropping frames after a field technician changes the physical interface to tagged trunk mode. Distinguishing evidence: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: B
Another possible combination is: First verify the observed failure (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.); review and authorize the bounded correction (Validate VLAN and virtual-switch boundaries, physical member state and MAC learning before changing upstream BGP sessions.); then independently verify the intended outcome (Bidirectional test frames learn on the expected ports and remain within the authorized bridge domain without affecting route peers.) before production rollout. The current record instead supports Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership, verified by the customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.
The starting point is Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The proposed action and its separate check are Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership and the customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs, respectively.
Another action-and-check pairing is: First verify the observed failure (Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.); review and authorize the bounded correction (Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.); then independently verify the intended outcome (The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.) before production rollout. The evidence here is Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The required action and proof are Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership and the customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.
An alternative plan is: First verify the observed failure (Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.); review and authorize the bounded correction (Separate the tenant virtual switches and bridge-domain scopes while preserving the contracted tag translation on each handoff.); then independently verify the intended outcome (Broadcast and unknown-unicast tests remain isolated to each customer and independent service port traffic follows expected boundaries.) before production rollout. It does not test the case-specific condition: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
Question 228
A fictional Junos service-provider engineer encounters this scenario: A wholesale handoff intended for one untagged customer VLAN starts dropping frames after a field technician changes the physical interface to tagged trunk mode. Distinguishing evidence: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. 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 (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.). It does not match the current change: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.
Another approval action 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.). The relevant evidence and acceptance are Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding and the customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs, respectively.
Another approval package concerns: Observed evidence (Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.), limited correction (Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.), independently measurable result (The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.). The present scope must instead be justified by Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
The approval decision should consider Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The specific proposal 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.). Its measurable outcome is: The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.
Question 229
A fictional Junos service-provider engineer encounters this scenario: A wholesale handoff intended for one untagged customer VLAN starts dropping frames after a field technician changes the physical interface to tagged trunk mode. Distinguishing evidence: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: B
Another recovery route would 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. It does not preserve the condition of this case: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The bounded fallback is: 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.
A contingency plan 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. This preserves control of the change linked to Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
Another fallback concerns pausing 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 current change concerns Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding.
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: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The bounded fallback is: 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.
Question 230
A fictional Junos service-provider engineer encounters this scenario: A wholesale handoff intended for one untagged customer VLAN starts dropping frames after a field technician changes the physical interface to tagged trunk mode. Distinguishing evidence: Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: B
An alternative approval 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. The relevant evidence and acceptance are Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding and the customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs, respectively.
The approval decision should consider Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding. The specific proposal is: 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. Its measurable outcome is: The customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs.
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: Verify the handoff contract and bridge interface port mode, then restore only the intended tag treatment and VLAN membership.
An alternative approval would approve only the bounded change (Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.) after independently checking (The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Ethernet frame captures show customer untagged traffic while the bridge interface membership expects an 802.1Q VLAN tag for forwarding and the customer CE exchanges untagged frames successfully without gaining access to other wholesale service VLANs, respectively.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 21 - 10 Questions (Last Reviewed 29-Oct-2026)
- Juniper JN0-364 Practice Test 22 - 10 Questions (Last Reviewed 28-Oct-2026)
- 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)