JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
Before changing configuration at Westhaven Software, an engineer investigates: An upstream customer changes its inner VLAN numbers and the carrier wants to preserve those tags without provisioning each inner VLAN individually. Which first diagnostic most directly tests the suspected cause?
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: Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.
Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges. The service depends on two distinct VLAN tag contexts; ordinary single-tag access mode is insufficient for transparent customer tag transport.
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: Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.
That evidence could be normal while the reported defect persists. It is aimed at: A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. Instead inspect: Capture ingress and egress Ethernet tag stacks and check provider bridging service VLAN and TPID settings at both edges.
At Cascade Hosting, a service provider router shows this failure: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. What is the best targeted configuration or operations action?
That would address a separate configuration fault: Hosts within a VLAN communicate, but traffic to other VLANs fails because the logical Layer 3 gateway is not linked to the bridge VLAN. This stem identifies a different cause, corrected by: Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
The other action is relevant when A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. The current case instead requires: Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop. The distinction is: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop. The case-specific reason is: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection. A direct acceptance test is: Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding.
A change auditor at Cascade Hosting must validate remediation of this finding: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. Which test outcome is the strongest acceptance evidence?
Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding. The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
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: Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding.
The observation confirms a different component's behavior. Its source context is: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. In this case the success criterion is: Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding.
That check proves something else, such as: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. It could pass while the stated problem remains. The targeted evidence here is: Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding.
The operations training team at Cascade Hosting discusses this issue: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. Which technical explanation matches the intended correction?
The statement can be true when A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. But it does not explain the reported failure. Here: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
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: Bridge forwarding databases and learning controls scope MAC state to the service; unchecked churn stresses memory and floods unknown destinations.
Bridge forwarding databases and learning controls scope MAC state to the service; unchecked churn stresses memory and floods unknown destinations. The key distinction is: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection. Accordingly the remedy is: Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop.
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: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
At Cascade Hosting, a service acceptance review considers the unresolved issue: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. Which operational exposure follows most directly?
The concern could occur elsewhere when A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. For the stated scenario, the immediate risk is: An uncontrolled customer loop can exhaust MAC-table resources or cause excessive flooding that affects other services.
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: An uncontrolled customer loop can exhaust MAC-table resources or cause excessive flooding that affects other services.
An uncontrolled customer loop can exhaust MAC-table resources or cause excessive flooding that affects other services. The direct mitigation is: Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop.
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: An uncontrolled customer loop can exhaust MAC-table resources or cause excessive flooding that affects other services.
Before changing configuration at Cascade Hosting, an engineer investigates: A provider Ethernet handoff suddenly experiences massive MAC-learning churn after a customer loop; unrelated customers share the same switching hardware. Which first diagnostic most directly tests the suspected cause?
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.
That evidence could be normal while the reported defect persists. It is aimed at: A port is in the correct trunk mode yet a service still fails because the corresponding bridge domain does not include the logical unit. Instead inspect: Inspect bridge-domain MAC counts, moves, aging and storm/loop indications before changing routing protocol configuration.
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: 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: 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 Brookport Finance, the engineer observes: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. Which remediation most directly fixes the described problem?
The other action is relevant when A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. The current case instead requires: Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop. The distinction is: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop. The case-specific reason is: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection. A direct acceptance test is: Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding.
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: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
The other action is relevant when A redundant bridged customer ring floods broadcasts after a link change because the blocking/forwarding boundary is misconfigured. The current case instead requires: Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop. The distinction is: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
The Junos team at Brookport Finance needs a success criterion for this defect: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. Which observed result most precisely confirms the intended repair?
Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding. The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
That check proves something else, such as: A provider Ethernet service forwards unicast normally until a customer VM migrates; packets for its MAC continue toward the old attachment port. It could pass while the stated problem remains. The targeted evidence here is: Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding.
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: Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding.
The observation confirms a different component's behavior. Its source context 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. In this case the success criterion is: Per-service learned MAC count remains within the approved limit and legitimate customer MACs remain reachable without cross-service flooding.
While analyzing a service failure at Brookport Finance, the following is observed: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. Which mechanism best explains the underlying control-plane or forwarding behavior?
This explains a separate protocol behavior: A bridged VLAN experiences unknown-unicast flooding because no valid source MAC entries are learned on the new access interface after a migration. In the current facts, the controlling mechanism is: Bridge forwarding databases and learning controls scope MAC state to the service; unchecked churn stresses memory and floods unknown destinations.
The statement can be true 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. But it does not explain the reported failure. Here: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection.
Bridge forwarding databases and learning controls scope MAC state to the service; unchecked churn stresses memory and floods unknown destinations. The key distinction is: The issue is Layer 2 learning capacity and loop behavior, not Junos RIB preference or BGP import selection. Accordingly the remedy is: Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop.
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: Bridge forwarding databases and learning controls scope MAC state to the service; unchecked churn stresses memory and floods unknown destinations.
The following provider defect remains uncorrected at Brookport Finance: A wholesale edge receives far more source MAC addresses than the agreed customer-service limit and unknown-unicast flooding increases. What is the most direct service or security risk of leaving it unresolved?
An uncontrolled customer loop can exhaust MAC-table resources or cause excessive flooding that affects other services. The direct mitigation is: Constrain the appropriate customer service bridge domain and enforce a supported MAC-learning/security control while fixing the upstream loop.
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: An uncontrolled customer loop can exhaust MAC-table resources or cause excessive flooding that affects other services.
That consequence is more closely associated with another deficiency, such as: 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 described fault instead exposes: An uncontrolled customer loop can exhaust MAC-table resources or cause excessive flooding that affects other services.
It is a risk in another topology or protocol state: Two wholesale L2 customers use overlapping VLAN identifiers; without separation their Ethernet segments are accidentally bridged together. Here the most direct failure path is: An uncontrolled customer loop can exhaust MAC-table resources or cause excessive flooding that affects other services.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.