JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
A support escalation at Brookport Finance describes: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. Where should the Junos operator look first for decisive evidence?
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 bridge-domain MAC counts, moves, aging and storm/loop indications before changing routing protocol configuration.
This check may help with another root cause, 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 test the first failed condition; start with: Inspect bridge-domain MAC counts, moves, aging and storm/loop indications before changing routing protocol configuration.
Inspect bridge-domain MAC counts, moves, aging and storm/loop indications before changing routing protocol configuration. The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
This check may help with another root cause, for example: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. It does not test the first failed condition; start with: Inspect bridge-domain MAC counts, moves, aging and storm/loop indications before changing routing protocol configuration.
During a Junos network change at Briarfield Healthcare, the engineer observes: A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. Which remediation most directly fixes the described problem?
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: Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly.
Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service. The case-specific reason is: Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly. A direct acceptance test is: Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain.
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: Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.
This action may apply to a different problem, for example: 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 does not repair the stated failure boundary. The case-specific reason is: Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly.
The Junos team at Briarfield Healthcare needs a success criterion for this defect: A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. Which observed result most precisely confirms the intended repair?
This would be valid for another situation: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. It does not establish that the failing boundary in this scenario works; verify: Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain.
Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain. Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly.
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: Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain.
This would be valid for another situation: 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 does not establish that the failing boundary in this scenario works; verify: Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain.
While analyzing a service failure at Briarfield Healthcare, the following is observed: A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. Which mechanism best explains the underlying control-plane or forwarding behavior?
That principle belongs to a different service stage: 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 directly relevant mechanism is: Junos logical Ethernet service units and bridge-domain membership jointly determine how service frames are classified and forwarded.
This explains a separate protocol behavior: 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 the current facts, the controlling mechanism is: Junos logical Ethernet service units and bridge-domain membership jointly determine how service frames are classified and forwarded.
Junos logical Ethernet service units and bridge-domain membership jointly determine how service frames are classified and forwarded. The key distinction is: Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly. Accordingly the remedy is: Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.
That principle belongs to a different service stage: Two provider-facing switchports both forward the same bridged service and the MAC table shows persistent flapping between ports. The directly relevant mechanism is: Junos logical Ethernet service units and bridge-domain membership jointly determine how service frames are classified and forwarded.
The following provider defect remains uncorrected at Briarfield Healthcare: A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. What is the most direct service or security risk of leaving it unresolved?
That consequence is more closely associated with another deficiency, such as: 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 described fault instead exposes: A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong.
It is a risk in another topology or protocol state: A migration mixes tagged and untagged handoffs on the same service, and operators cannot explain why traffic falls into an unintended VLAN. Here the most direct failure path is: A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong.
A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong. The direct mitigation is: Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.
That consequence is more closely associated with another deficiency, 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. The described fault instead exposes: A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong.
A support escalation at Briarfield Healthcare describes: A logical Ethernet interface is up but no customer frames arrive on the intended VLAN after a maintenance migration. Where should the Junos operator look first for decisive evidence?
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 logical interface configuration, encapsulation, unit VLAN ID, bridge membership and port counters for the exact service.
The check diagnoses a different layer of service. Its source issue is: A provider moved a gateway address to an IRB logical unit yet the bridge domain has no valid association with that IRB interface. 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.
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 provider operations team at Cloverbank Mobile reports: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. Which implementation decision best corrects the cause?
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: Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.
This action may apply to a different problem, for example: After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. It does not repair the stated failure boundary. The case-specific reason is: Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly.
Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service. The case-specific reason is: Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly. A direct acceptance test is: Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain.
That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.
During a post-change check at Cloverbank Mobile, the original condition was: 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 evidence would validate the corrected behavior?
Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain. Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly.
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: Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain.
The observation confirms a different component's behavior. Its source context is: A customer endpoint sends untagged Ethernet frames but the new interface is configured for the wrong untagged VLAN, preventing communication with its gateway. In this case the success criterion is: Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge 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: Ingress and egress tagged frame counters increase for the correct logical interface and expected MAC entries appear within the bridge domain.
At Cloverbank Mobile, an engineer is asked to explain this case: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. Which underlying routing or switching principle accounts for the appropriate solution?
Junos logical Ethernet service units and bridge-domain membership jointly determine how service frames are classified and forwarded. The key distinction is: Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly. Accordingly the remedy is: Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.
That principle belongs to a different service stage: A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. The directly relevant mechanism is: Junos logical Ethernet service units and bridge-domain membership jointly determine how service frames are classified and forwarded.
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: Junos logical Ethernet service units and bridge-domain membership jointly determine how service frames are classified and forwarded.
The statement can be true when After replacing an edge switch, customer traffic arrives with an unexpected outer tag and the provider places it in the wrong broadcast domain. But it does not explain the reported failure. Here: Physical link state alone cannot prove a logical VLAN or bridge-domain handoff is provisioned correctly.
A risk assessment at Cloverbank Mobile identifies: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. Which practical consequence is most specifically tied to this failure?
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: A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong.
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: A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong.
A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong. The direct mitigation is: Verify the logical unit's encapsulation, VLAN/bridge-domain membership and interface counters on both ends of the service.
The concern could occur elsewhere when 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. For the stated scenario, the immediate risk is: A physically healthy Ethernet interface can carry no usable service traffic if logical classification or bridge membership is wrong.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.