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 24
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.
Question 231
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 specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: B
Another proposed action is: Check the VLAN's Layer 3 interface relationship and correct the scoped IRB binding, address family and eligibility. That does not directly address the observed condition: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The more targeted correction is: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.
The observed condition is: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. This calls for the scoped change: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership. The acceptance measure is: Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.
Another option proposes: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control. The specific correction is: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership. The deciding evidence is: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
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 Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The corresponding fix is: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.
Question 232
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. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: B
Another piece of evidence 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. The current incident instead shows: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. This distinction supports the action: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.
The deciding evidence is: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. This distinguishes the problem because Provider bridging encapsulates customer VLAN traffic using an agreed service VLAN tag boundary. The response it supports is: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.
This other option describes: The neighboring router advertises a different source address from the one in the local configured BGP neighbor statement and logs show connection attempts to the obsolete IP. The problem to explain is different: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
Another proposed finding 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. It is not the recorded discriminator, which is Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
Question 233
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 Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: C
A different principle is: BGP hold timers and KEEPALIVE messages provide session liveness independent of accepted route policies. Evidence for this case: Peer history contains hold timer expirations and packet captures show sporadic missing keepalives during a saturated control-plane event. The present evidence, however, is Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The relevant rule is: Provider bridging encapsulates customer VLAN traffic using an agreed service VLAN tag boundary.
This alternative invokes: 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. The governing distinction for the recorded case is Provider bridging encapsulates customer VLAN traffic using an agreed service VLAN tag boundary.
The observed evidence is: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The governing principle is: Provider bridging encapsulates customer VLAN traffic using an agreed service VLAN tag boundary. Consequently, the targeted action is: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.
That principle concerns another fact pattern: 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. Here the key fact is: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
Question 234
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. Intended bounded correction: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: B
That result would assess another condition: Hosts in the specified VLAN reach their authorized gateway while isolation and route selection for other VLANs remain intact. The correct criterion is directly linked to the finding: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers. This verifies the required result rather than merely stating the action; the original issue was Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
A different option checks: The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation. The case-specific acceptance condition is instead Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.
Passing that test would not establish resolution of the stated issue. The relevant proof is: Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.
Question 235
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 material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: C
Another caution is: Changing ASN or routing policy without verifying the transport endpoint can create a separate outage or route leak. The key risk in this case is: Removing outer tags indiscriminately can merge customer broadcast domains and break provider-bridging isolation.
Another emphasis concerns: An unrelated BGP policy adjustment cannot repair a Layer 2 forwarding-table error and may interrupt transit networks. The current change is Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership; the material limitation is Removing outer tags indiscriminately can merge customer broadcast domains and break provider-bridging isolation.
The relevant boundary is: Removing outer tags indiscriminately can merge customer broadcast domains and break provider-bridging isolation. It matters when applying the specific response: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.
Another caution is: Misaligned port tagging can create a service outage or expose unrelated VLANs through an overly broad trunk. The key risk in this case is: Removing outer tags indiscriminately can merge customer broadcast domains and break provider-bridging isolation.
Question 236
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 focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: C
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Advertised route inspection lists a private customer prefix that is not present in the approved external export inventory. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
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 Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The focused check here is: 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 focused investigation should 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 is tied to the observed evidence: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. It tests the conditions for this response: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership.
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: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
Question 237
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 controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: C
Another action-and-check pairing 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 evidence here is Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The required action and proof are Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership and Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.
An alternative plan is: First verify the observed failure (Received-route visibility shows the customer prefix, while the import policy match excludes its approved prefix length and the RIB lacks the route.); review and authorize the bounded correction (Review the prefix-length and routing-policy terms, allow only the contracted prefix range and verify the actual import result.); then independently verify the intended outcome (The authorized customer route becomes usable and adjacent unapproved prefixes remain rejected at the policy boundary.) before production rollout. It does not test the case-specific condition: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
Provider bridging encapsulates customer VLAN traffic using an agreed service VLAN tag boundary. For this issue, the appropriate bounded intervention is: Check accepted service VLAN and inner-tag preservation requirements, then correct the intended outer tag translation or service membership. The acceptance test is: Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.
Another potential sequence 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. It has no direct link to the distinguishing evidence: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
Question 238
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 set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: C
Another approval package concerns: Observed evidence (Received-route visibility shows the customer prefix, while the import policy match excludes its approved prefix length and the RIB lacks the route.), limited correction (Review the prefix-length and routing-policy terms, allow only the contracted prefix range and verify the actual import result.), independently measurable result (The authorized customer route becomes usable and adjacent unapproved prefixes remain rejected at the policy boundary.). The present scope must instead be justified by Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
An alternative release decision 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.). 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.
The approval decision should consider Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The specific proposal 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.). Its measurable outcome is: Customer inner VLAN traffic crosses the agreed provider service path with the expected outer encapsulation and isolation from unrelated customers.
Another approval package concerns: 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.). The present scope must instead be justified by Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
Question 239
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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: D
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 Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
Another recovery route would pause changes, preserve the differentiating evidence (Bridge-domain membership reveals two customer-facing interfaces accidentally attached to one virtual switch despite separate service contracts.), restore the last approved safe network state and reassess bridge domain configuration allows duplicate customer identifiers. It does not preserve the condition of this case: Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers. The bounded fallback is: 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.
Another option proposes: Pause changes, preserve the differentiating evidence (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.), restore the last approved safe network state and reassess php behavior makes a packet appear unlabeled before the destination. Its assumptions differ from the observed failure; the appropriate recovery is: 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.
A contingency plan 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. This preserves control of the change linked to Packet capture on the provider-facing trunk shows the wrong outer service tag with otherwise correct customer inner VLAN identifiers.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- 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)
- Juniper JN0-364 Practice Test 26 - 10 Questions (Last Reviewed 24-Oct-2026)