JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
The on-call engineer at Baystone Energy receives this fault report: A provider moved a gateway address to an IRB logical unit yet the bridge domain has no valid association with that IRB interface. What initial check best isolates the actual failing protocol stage?
The check diagnoses a different layer of service. Its source issue is: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. The relevant initial check is: Inspect VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance.
This check may help with another root cause, for example: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. It does not test the first failed condition; start with: Inspect VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance.
Inspect VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance. A local bridge can work without an IRB, but inter-VLAN routing requires an attached Layer 3 gateway interface.
The check diagnoses a different layer of service. Its source issue is: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. The relevant initial check is: Inspect VLAN/bridge-domain IRB association, gateway ARP or neighbor entries and resulting connected routes in the correct instance.
The provider operations team at Westhaven Software reports: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. Which implementation decision best corrects the cause?
This action may apply to a different problem, for example: 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 repair the stated failure boundary. The case-specific reason is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
The other action is relevant when A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. The current case instead requires: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries. The distinction is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
That would address a separate configuration fault: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. This stem identifies a different cause, corrected by: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.
Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries. The case-specific reason is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services. A direct acceptance test is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.
During a post-change check at Westhaven Software, the original condition was: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. What evidence would validate the corrected behavior?
The observation confirms a different component's behavior. Its source context is: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. In this case the success criterion is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.
The observation confirms a different component's behavior. Its source context 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. In this case the success criterion is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.
That check proves something else, such as: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. It could pass while the stated problem remains. The targeted evidence here is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.
Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain. Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
At Westhaven Software, an engineer is asked to explain this case: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. Which underlying routing or switching principle accounts for the appropriate solution?
A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain. The key distinction is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services. Accordingly the remedy is: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.
The statement can be true when A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. But it does not explain the reported failure. Here: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
The statement can be true when A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. But it does not explain the reported failure. Here: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
That principle belongs to a different service stage: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. The directly relevant mechanism is: A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain.
A risk assessment at Westhaven Software identifies: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. Which practical consequence is most specifically tied to this failure?
Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context. The direct mitigation is: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.
It is a risk in another topology or protocol state: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. Here the most direct failure path is: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.
The concern could occur elsewhere when After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. For the stated scenario, the immediate risk is: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.
That consequence is more closely associated with another deficiency, such as: Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. The described fault instead exposes: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.
The on-call engineer at Westhaven Software receives this fault report: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. What initial check best isolates the actual failing protocol stage?
That evidence could be normal while the reported defect persists. It is aimed at: Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. Instead inspect: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
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 ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants. Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
That evidence could be normal while the reported defect persists. It is aimed at: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. Instead inspect: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
A production change request at Eastvale MetroNet includes this finding: 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. What should the engineer change to address it?
Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries. The case-specific reason is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services. A direct acceptance test is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
The other action is relevant when Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. The current case instead requires: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries. The distinction is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
That would address a separate configuration fault: A provider uplink carries VLAN 100 but drops VLAN 200 traffic because the trunk's allowed membership omits VLAN 200. This stem identifies a different cause, corrected by: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.
After Eastvale MetroNet applies its proposed fix to this problem — 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. — which observation best proves the specific failure has been resolved?
Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain. Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
This would be valid for another situation: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. It does not establish that the failing boundary in this scenario works; verify: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.
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: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.
That check proves something else, such as: 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 could pass while the stated problem remains. The targeted evidence here is: Each tenant's same-numbered VLAN learns MACs and floods traffic only within its intended virtual switch, without sharing another customer's broadcast domain.
An architecture review at Eastvale MetroNet examines the following symptom: 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. What Junos or protocol mechanism is most directly responsible?
That principle belongs to a different service stage: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. The directly relevant mechanism is: A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain.
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: A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain.
A virtual-switch instance establishes a distinct Layer 2 forwarding context, permitting overlapping VLAN IDs without a shared global bridge domain. The key distinction is: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services. Accordingly the remedy is: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.
The statement can be true when A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. But it does not explain the reported failure. Here: Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
The team at Eastvale MetroNet defers a fix for this condition: 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. What failure is most likely if no targeted control is applied?
The concern could occur elsewhere when Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. For the stated scenario, the immediate risk is: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.
Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context. The direct mitigation is: Place customer bridge domains and interfaces into separate intended virtual-switch/routing-instance contexts and validate forwarding boundaries.
It is a risk in another topology or protocol state: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. Here the most direct failure path is: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.
The concern could occur elsewhere when Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. For the stated scenario, the immediate risk is: Cross-customer broadcast and unknown-unicast traffic can leak between services if same-numbered VLANs share a bridge context.
During provider troubleshooting at Eastvale MetroNet, this symptom is observed: 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. Which targeted inspection should precede remediation?
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: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants. Logical switching separation, not a BGP path preference, is required to isolate overlapping Layer 2 customer services.
The check diagnoses a different layer of service. Its source issue is: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. The relevant initial check is: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
This check may help with another root cause, for example: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. It does not test the first failed condition; start with: Inspect ingress interface's virtual-switch instance, instance-specific bridge domains and MAC tables for both tenants.
Please check your mailbox for a message from support@examlabs.com and follow the directions.