Question 650
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
- IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
- An IS-IS adjacency needs compatible protocol levels as well as link reachability.
- IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
Explanation
Correct Answer
D:IS-IS relies on a unique system ID to identify LSP originators and topology nodes. This principle directly explains the controlled acceptance rehearsal: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. The aligned engineering response is: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state. The result should be established through: The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
Incorrect Answers
A:IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. That explanation applies to the different IS-IS LSP lifetime anomaly scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. The controlling mechanism is instead: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The correct response would be: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
B:IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. That explanation applies to the different IS-IS route export scope scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. The controlling mechanism is instead: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The correct response would be: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
C:An IS-IS adjacency needs compatible protocol levels as well as link reachability. That explanation applies to the different IS-IS level capability mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. The controlling mechanism is instead: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The correct response would be: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
Question 651
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
- Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
- A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
- Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
Explanation
Correct Answer
A:Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. This principle directly explains the controlled acceptance rehearsal: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The aligned engineering response is: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff. The result should be established through: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.
Incorrect Answers
B:Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. That explanation applies to the different Virtual switch instance membership scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The controlling mechanism is instead: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The correct response would be: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.
C:A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. That explanation applies to the different Trunk allowed VLAN omission scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The controlling mechanism is instead: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The correct response would be: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.
D:Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. That explanation applies to the different Native VLAN mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The controlling mechanism is instead: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The correct response would be: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.
Question 652
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
- IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
- When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.
- An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
Explanation
Correct Answer
C:When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. This principle directly explains the controlled acceptance rehearsal: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The aligned engineering response is: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs. The result should be established through: Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current.
Incorrect Answers
A:The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. That explanation applies to the different IS-IS DIS election surprise scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The controlling mechanism is instead: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The correct response would be: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
B:IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. That explanation applies to the different IS-IS route export scope scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The controlling mechanism is instead: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The correct response would be: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
D:An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. That explanation applies to the different IS-IS overload-state recovery scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The controlling mechanism is instead: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The correct response would be: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
Question 653
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
- OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
- External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
- OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
Explanation
Correct Answer
D:OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. This principle directly explains the controlled acceptance rehearsal: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The aligned engineering response is: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state. The result should be established through: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
Incorrect Answers
A:OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. That explanation applies to the different OSPF metric path preference scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The controlling mechanism is instead: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The correct response would be: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
B:OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. That explanation applies to the different OSPF MTU ExStart stall scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The controlling mechanism is instead: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The correct response would be: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
C:External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. That explanation applies to the different OSPF export policy omission scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The controlling mechanism is instead: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The correct response would be: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
Question 654
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
- The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
- IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
- An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
Explanation
Correct Answer
A:IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. This principle directly explains the controlled acceptance rehearsal: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The aligned engineering response is: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended. The result should be established through: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
Incorrect Answers
B:The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. That explanation applies to the different IS-IS DIS election surprise scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The controlling mechanism is instead: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The correct response would be: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
C:IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. That explanation applies to the different IS-IS route export scope scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The controlling mechanism is instead: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The correct response would be: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
D:An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. That explanation applies to the different IS-IS overload-state recovery scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The controlling mechanism is instead: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The correct response would be: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
Question 655
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
- Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
- IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
- An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
Explanation
Correct Answer
C:IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. This principle directly explains the controlled acceptance rehearsal: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The aligned engineering response is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information. The result should be established through: LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.
Incorrect Answers
A:The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. That explanation applies to the different IS-IS DIS election surprise scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The controlling mechanism is instead: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The correct response would be: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
B:Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. That explanation applies to the different IS-IS Level 1 exit default scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The controlling mechanism is instead: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The correct response would be: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
D:An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. That explanation applies to the different IS-IS overload-state recovery scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The controlling mechanism is instead: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The correct response would be: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
Question 656
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.
- VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
- VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.
- BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
Explanation
Correct Answer
A:GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. This principle directly explains the controlled acceptance rehearsal: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The aligned engineering response is: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target. The result should be established through: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
Incorrect Answers
B:VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. That explanation applies to the different VRRP master priority failover scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The controlling mechanism is instead: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The correct response would be: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
C:VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. That explanation applies to the different VRRP preemption oscillation scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The controlling mechanism is instead: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The correct response would be: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
D:BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. That explanation applies to the different BFD detect timer too aggressive scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The controlling mechanism is instead: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The correct response would be: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
Question 657
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
- RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.
- Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.
- SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.
Explanation
Correct Answer
C:Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. This principle directly explains the controlled acceptance rehearsal: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The aligned engineering response is: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress. The result should be established through: A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.
Incorrect Answers
A:RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. That explanation applies to the different RSVP reservable bandwidth shortage scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The controlling mechanism is instead: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The correct response would be: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
B:RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. That explanation applies to the different RSVP link protection plan scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The controlling mechanism is instead: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The correct response would be: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
D:SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. That explanation applies to the different Segment routing SID advertisement scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The controlling mechanism is instead: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The correct response would be: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
Question 658
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.
- Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.
- Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
- Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
Explanation
Correct Answer
D:Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. This principle directly explains the controlled acceptance rehearsal: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The aligned engineering response is: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior. The result should be established through: The generated default becomes active with the expected next hop only when the qualifying contributor exists.
Incorrect Answers
A:A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. That explanation applies to the different Static backup blackhole scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The controlling mechanism is instead: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The correct response would be: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
B:Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. That explanation applies to the different Filter-based forwarding classification scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The controlling mechanism is instead: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The correct response would be: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
C:Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. That explanation applies to the different RIB group forwarding copy scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The controlling mechanism is instead: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The correct response would be: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
Question 659
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
- Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.
- RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
- LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
Explanation
Correct Answer
D:LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. This principle directly explains the controlled acceptance rehearsal: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The aligned engineering response is: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors. The result should be established through: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
Incorrect Answers
A:Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. That explanation applies to the different Penultimate hop popping scenario rather than this controlled acceptance rehearsal. The current fault evidence is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The controlling mechanism is instead: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The correct response would be: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
B:Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. That explanation applies to the different Explicit-null forwarding scenario rather than this controlled acceptance rehearsal. The current fault evidence is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The controlling mechanism is instead: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The correct response would be: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
C:RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. That explanation applies to the different RSVP-TE constrained path missing scenario rather than this controlled acceptance rehearsal. The current fault evidence is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The controlling mechanism is instead: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The correct response would be: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
Question 660
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.
- Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
- Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
- Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
Explanation
Correct Answer
A:Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. This principle directly explains the controlled acceptance rehearsal: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The aligned engineering response is: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag. The result should be established through: A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.
Incorrect Answers
B:Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. That explanation applies to the different Native VLAN mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The controlling mechanism is instead: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The correct response would be: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
C:Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. That explanation applies to the different Flexible VLAN tagging logical units scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The controlling mechanism is instead: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The correct response would be: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
D:Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. That explanation applies to the different Virtual switch instance membership scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The controlling mechanism is instead: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The correct response would be: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests