JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
The on-call engineer at Cloverbank Mobile receives this fault report: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. What initial check best isolates the actual failing protocol stage?
That evidence could be normal while the reported defect persists. It is aimed at: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. Instead inspect: Inspect logical interface configuration, encapsulation, unit VLAN ID, bridge membership and port counters for the exact service.
Inspect logical interface configuration, encapsulation, unit VLAN ID, bridge membership and port counters for the exact service. Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly.
The check diagnoses a different layer of service. Its source issue is: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. The relevant initial check is: Inspect logical interface configuration, encapsulation, unit VLAN ID, bridge membership and port counters for the exact service.
This check may help with another root cause, for example: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. It does not test the first failed condition; start with: Inspect logical interface configuration, encapsulation, unit VLAN ID, bridge membership and port counters for the exact service.
The provider operations team at Northline Communications reports: A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. Which implementation decision best corrects the cause?
The other action is relevant when A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. The current case instead requires: Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state. The distinction is: The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0.
That would address a separate configuration fault: An operator moves one customer port into a new virtual-switch service but continues to inspect the global bridge table, missing the tenant-specific entries. This stem identifies a different cause, corrected by: Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state.
This action may apply to a different problem, for example: A site access port accidentally belongs to the provider management VLAN, so the attached single-VLAN device receives a DHCP address from the wrong segment. It does not repair the stated failure boundary. The case-specific reason is: The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0.
Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state. The case-specific reason is: The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0. A direct acceptance test is: Broadcast storm rates and MAC-move events return to normal, with one deliberate alternate path blocked or logically isolated where necessary.
During a post-change check at Northline Communications, the original condition was: A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. What evidence would validate the corrected behavior?
Broadcast storm rates and MAC-move events return to normal, with one deliberate alternate path blocked or logically isolated where necessary. The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0.
That check proves something else, such as: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. It could pass while the stated problem remains. The targeted evidence here is: Broadcast storm rates and MAC-move events return to normal, with one deliberate alternate path blocked or logically isolated where necessary.
This would be valid for another situation: Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. It does not establish that the failing boundary in this scenario works; verify: Broadcast storm rates and MAC-move events return to normal, with one deliberate alternate path blocked or logically isolated where necessary.
The observation confirms a different component's behavior. Its source context is: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. In this case the success criterion is: Broadcast storm rates and MAC-move events return to normal, with one deliberate alternate path blocked or logically isolated where necessary.
At Northline Communications, an engineer is asked to explain this case: A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. Which underlying routing or switching principle accounts for the appropriate solution?
This explains a separate protocol behavior: A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. In the current facts, the controlling mechanism is: Ethernet bridging without a loop-prevention mechanism repeatedly floods broadcast and unknown-unicast frames around a cycle.
Ethernet bridging without a loop-prevention mechanism repeatedly floods broadcast and unknown-unicast frames around a cycle. The key distinction is: The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0. Accordingly the remedy is: Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state.
That principle belongs to a different service stage: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. The directly relevant mechanism is: Ethernet bridging without a loop-prevention mechanism repeatedly floods broadcast and unknown-unicast frames around a cycle.
This explains a separate protocol behavior: A provider moved a gateway address to an IRB logical unit yet the bridge domain has no valid association with that IRB interface. In the current facts, the controlling mechanism is: Ethernet bridging without a loop-prevention mechanism repeatedly floods broadcast and unknown-unicast frames around a cycle.
A risk assessment at Northline Communications identifies: A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. Which practical consequence is most specifically tied to this failure?
Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric. The direct mitigation is: Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state.
The concern could occur elsewhere when A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. For the stated scenario, the immediate risk is: Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric.
That consequence is more closely associated with another deficiency, such as: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. The described fault instead exposes: Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric.
It is a risk in another topology or protocol state: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. Here the most direct failure path is: Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric.
The on-call engineer at Northline Communications receives this fault report: A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. What initial check best isolates the actual failing protocol stage?
The check diagnoses a different layer of service. Its source issue is: A site access port accidentally belongs to the provider management VLAN, so the attached single-VLAN device receives a DHCP address from the wrong segment. The relevant initial check is: Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.
This check may help with another root cause, for example: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. It does not test the first failed condition; start with: Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.
Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN. The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0.
The check diagnoses a different layer of service. Its source issue is: A campus-to-provider trunk passes several tagged customer services while a newly provisioned tag fails because the far-end trunk has not allowed it. The relevant initial check is: Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.
A production change request at Briarfield Healthcare includes this finding: Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. What should the engineer change to address it?
This action may apply to a different problem, for example: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. It does not repair the stated failure boundary. The case-specific reason is: The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0.
The other action is relevant when Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. The current case instead requires: Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state. The distinction is: The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0.
That would address a separate configuration fault: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. This stem identifies a different cause, corrected by: Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state.
Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state. The case-specific reason is: The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0. A direct acceptance test is: Broadcast storm rates and MAC-move events return to normal, with one deliberate alternate path blocked or logically isolated where necessary.
After Briarfield Healthcare applies its proposed fix to this problem — Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. — which observation best proves the specific failure has been resolved?
This would be valid for another situation: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. It does not establish that the failing boundary in this scenario works; verify: Broadcast storm rates and MAC-move events return to normal, with one deliberate alternate path blocked or logically isolated where necessary.
The observation confirms a different component's behavior. Its source context is: A provider uplink carries VLAN 100 but drops VLAN 200 traffic because the trunk's allowed membership omits VLAN 200. In this case the success criterion is: Broadcast storm rates and MAC-move events return to normal, with one deliberate alternate path blocked or logically isolated where necessary.
That check proves something else, such as: An operator moves one customer port into a new virtual-switch service but continues to inspect the global bridge table, missing the tenant-specific entries. It could pass while the stated problem remains. The targeted evidence here is: Broadcast storm rates and MAC-move events return to normal, with one deliberate alternate path blocked or logically isolated where necessary.
Broadcast storm rates and MAC-move events return to normal, with one deliberate alternate path blocked or logically isolated where necessary. The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0.
An architecture review at Briarfield Healthcare examines the following symptom: Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. What Junos or protocol mechanism is most directly responsible?
Ethernet bridging without a loop-prevention mechanism repeatedly floods broadcast and unknown-unicast frames around a cycle. The key distinction is: The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0. Accordingly the remedy is: Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state.
This explains a separate protocol behavior: Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. In the current facts, the controlling mechanism is: Ethernet bridging without a loop-prevention mechanism repeatedly floods broadcast and unknown-unicast frames around a cycle.
The statement can be true when A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. But it does not explain the reported failure. Here: The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0.
That principle belongs to a different service stage: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. The directly relevant mechanism is: Ethernet bridging without a loop-prevention mechanism repeatedly floods broadcast and unknown-unicast frames around a cycle.
The team at Briarfield Healthcare defers a fix for this condition: Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. What failure is most likely if no targeted control is applied?
Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric. The direct mitigation is: Restore a loop-free Layer 2 topology using correct spanning-tree or loop-protection design and verify the affected service forwarding state.
The concern could occur elsewhere when A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. For the stated scenario, the immediate risk is: Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric.
The concern could occur elsewhere when A campus-to-provider trunk passes several tagged customer services while a newly provisioned tag fails because the far-end trunk has not allowed it. For the stated scenario, the immediate risk is: Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric.
That consequence is more closely associated with another deficiency, such as: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. The described fault instead exposes: Broadcast storms and unstable MAC learning can consume bandwidth and interrupt multiple tenants sharing the switched fabric.
During provider troubleshooting at Briarfield Healthcare, this symptom is observed: Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. Which targeted inspection should precede remediation?
That evidence could be normal while the reported defect persists. It is aimed at: A campus-to-provider trunk passes several tagged customer services while a newly provisioned tag fails because the far-end trunk has not allowed it. Instead inspect: Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.
The check diagnoses a different layer of service. Its source issue is: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. The relevant initial check is: Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.
This check may help with another root cause, for example: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. It does not test the first failed condition; start with: Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN.
Correlate MAC move counters, spanning-tree port states and broadcast interface counters for the affected VLAN. The immediate fault is a physical or logical Layer 2 cycle, not merely an incorrect route aggregate in inet.0.
Please check your mailbox for a message from support@examlabs.com and follow the directions.