JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
A support escalation at Brightwood Public Works describes: A router has eBGP paths with equal relevant attributes and the operations team assumes both will automatically enter the forwarding table. Where should the Junos operator look first for decisive evidence?
This check may help with another root cause, for example: Two eBGP routes have equal earlier BGP decision attributes and the operator needs to explain why a path with fewer AS numbers is preferred. It does not test the first failed condition; start with: Inspect best-path and alternate path attributes, multipath configuration and the forwarding next-hop group for the exact destination.
That evidence could be normal while the reported defect persists. It is aimed at: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. Instead inspect: Inspect best-path and alternate path attributes, multipath configuration and the forwarding next-hop group for the exact destination.
Inspect best-path and alternate path attributes, multipath configuration and the forwarding next-hop group for the exact destination. Multiple BGP paths in route detail are not equivalent to active multipath forwarding across those paths.
This check may help with another root cause, for example: A provider advertises two links to a neighboring AS and wishes to express a preferred ingress while keeping the links as separate BGP paths. It does not test the first failed condition; start with: Inspect best-path and alternate path attributes, multipath configuration and the forwarding next-hop group for the exact destination.
During a Junos network change at Clearwater Analytics, the engineer observes: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. Which remediation most directly fixes the described problem?
Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces. The case-specific reason is: MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port. A direct acceptance test is: The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing.
That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces.
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: MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.
The other action is relevant when A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. The current case instead requires: Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces. The distinction is: MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.
The Junos team at Clearwater Analytics needs a success criterion for this defect: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. Which observed result most precisely confirms the intended repair?
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: The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing.
That check proves something else, such as: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. It could pass while the stated problem remains. The targeted evidence here is: The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing.
The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing. MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.
The observation confirms a different component's behavior. Its source context is: A provider moved a gateway address to an IRB logical unit yet the bridge domain has no valid association with that IRB interface. In this case the success criterion is: The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing.
While analyzing a service failure at Clearwater Analytics, the following is observed: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. Which mechanism best explains the underlying control-plane or forwarding behavior?
Ethernet bridges associate observed source MACs with ingress ports within a broadcast domain and use learned destination MAC entries for unicast forwarding. The key distinction is: MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port. Accordingly the remedy is: Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces.
The statement can be true when A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. But it does not explain the reported failure. Here: MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.
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 bridges associate observed source MACs with ingress ports within a broadcast domain and use learned destination MAC entries for unicast forwarding.
This explains a separate protocol behavior: 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. In the current facts, the controlling mechanism is: Ethernet bridges associate observed source MACs with ingress ports within a broadcast domain and use learned destination MAC entries for unicast forwarding.
The following provider defect remains uncorrected at Clearwater Analytics: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. What is the most direct service or security risk of leaving it unresolved?
It is a risk in another topology or protocol state: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. Here the most direct failure path is: Stale or missing MAC learning leads to unintended flooding, intermittent reachability or delivery to an old attachment port.
The concern could occur elsewhere when A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. For the stated scenario, the immediate risk is: Stale or missing MAC learning leads to unintended flooding, intermittent reachability or delivery to an old attachment port.
Stale or missing MAC learning leads to unintended flooding, intermittent reachability or delivery to an old attachment port. The direct mitigation is: Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces.
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: Stale or missing MAC learning leads to unintended flooding, intermittent reachability or delivery to an old attachment port.
A support escalation at Clearwater Analytics describes: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. Where should the Junos operator look first for decisive evidence?
The check diagnoses a different layer of service. Its source issue is: A provider uplink carries VLAN 100 but drops VLAN 200 traffic because the trunk's allowed membership omits VLAN 200. The relevant initial check is: Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.
Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces. MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.
That evidence could be normal while the reported defect persists. It is aimed at: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. Instead inspect: Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.
The check diagnoses a different layer of service. Its source issue is: 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. The relevant initial check is: Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.
The provider operations team at Northshore Utilities reports: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. Which implementation decision best corrects the cause?
Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces. The case-specific reason is: MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port. A direct acceptance test is: The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing.
The other action is relevant when A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. The current case instead requires: Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces. The distinction is: MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.
That would address a separate configuration fault: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. This stem identifies a different cause, corrected by: Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces.
This action may apply to a different problem, for example: A carrier must transport a customer's internal VLAN tags across its Metro Ethernet network while isolating each customer service with an outer service tag. It does not repair the stated failure boundary. The case-specific reason is: MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.
During a post-change check at Northshore Utilities, the original condition was: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. What evidence would validate the corrected behavior?
This would be valid for another situation: A provider moved a gateway address to an IRB logical unit yet the bridge domain has no valid association with that IRB interface. It does not establish that the failing boundary in this scenario works; verify: The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing.
The observation confirms a different component's behavior. Its source context is: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. In this case the success criterion is: The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing.
The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing. MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.
This would be valid for another situation: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. It does not establish that the failing boundary in this scenario works; verify: The bridge table learns the expected customer MAC on its current interface and unicast packets are forwarded to that port instead of flooding or blackholing.
At Northshore Utilities, an engineer is asked to explain this case: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. Which underlying routing or switching principle accounts for the appropriate solution?
That principle belongs to a different service stage: 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. The directly relevant mechanism is: Ethernet bridges associate observed source MACs with ingress ports within a broadcast domain and use learned destination MAC entries for unicast forwarding.
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 bridges associate observed source MACs with ingress ports within a broadcast domain and use learned destination MAC entries for unicast forwarding.
The statement can be true 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. But it does not explain the reported failure. Here: MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.
Ethernet bridges associate observed source MACs with ingress ports within a broadcast domain and use learned destination MAC entries for unicast forwarding. The key distinction is: MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port. Accordingly the remedy is: Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces.
A risk assessment at Northshore Utilities identifies: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. Which practical consequence is most specifically tied to this failure?
That consequence is more closely associated with another deficiency, such as: 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 described fault instead exposes: Stale or missing MAC learning leads to unintended flooding, intermittent reachability or delivery to an old attachment port.
Stale or missing MAC learning leads to unintended flooding, intermittent reachability or delivery to an old attachment port. The direct mitigation is: Restore correct VLAN membership and source-MAC learning on the intended ingress ports, clear only stale entries when justified, and verify the learned destination interfaces.
The concern could occur elsewhere when An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. For the stated scenario, the immediate risk is: Stale or missing MAC learning leads to unintended flooding, intermittent reachability or delivery to an old attachment port.
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: Stale or missing MAC learning leads to unintended flooding, intermittent reachability or delivery to an old attachment port.
The on-call engineer at Northshore Utilities receives this fault report: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. What initial check best isolates the actual failing protocol stage?
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.
The check diagnoses a different layer of service. Its source issue is: Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. The relevant initial check is: Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.
Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces. MAC learning concerns Layer 2 location; changing BGP next hop or IGP metric does not select the correct bridged egress port.
That evidence could be normal while the reported defect persists. It is aimed at: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. Instead inspect: Inspect the MAC address table for the VLAN and customer MAC, port state and aging or movement counters on the service interfaces.
Please check your mailbox for a message from support@examlabs.com and follow the directions.