Question 640
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
- Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.
- MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
- VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.
Explanation
Correct Answer
B:Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. This principle directly explains the controlled acceptance rehearsal: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. The aligned engineering response is: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy. The result should be established through: The intended core device is reported as root and a designated backup root is stable after an election test.
Incorrect Answers
A:RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. That explanation applies to the different RSTP alternate port activation scenario rather than this controlled acceptance rehearsal. The current fault evidence is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. The controlling mechanism is instead: Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. The correct response would be: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.
C:MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. That explanation applies to the different MSTP region mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. The controlling mechanism is instead: Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. The correct response would be: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.
D:VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. That explanation applies to the different Per-VLAN spanning-tree path scenario rather than this controlled acceptance rehearsal. The current fault evidence is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. The controlling mechanism is instead: Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. The correct response would be: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.
Question 641
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- 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.
- NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
- BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
Explanation
Correct Answer
C:NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. This principle directly explains the controlled acceptance rehearsal: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The aligned engineering response is: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover. The result should be established through: The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.
Incorrect Answers
A: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 redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The controlling mechanism is instead: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The correct response would be: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
B: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 redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The controlling mechanism is instead: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The correct response would be: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
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 redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The controlling mechanism is instead: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The correct response would be: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
Question 642
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.
- BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
- BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.
- Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.
Explanation
Correct Answer
D:Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. This principle directly explains the controlled acceptance rehearsal: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The aligned engineering response is: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths. The result should be established through: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
Incorrect Answers
A:BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. That explanation applies to the different BGP import policy leak scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The controlling mechanism is instead: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The correct response would be: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
B:BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. That explanation applies to the different BGP IPv6 family inactive scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The controlling mechanism is instead: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The correct response would be: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
C:BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. That explanation applies to the different BGP peer flap from mismatched hold timers scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The controlling mechanism is instead: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The correct response would be: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
Question 643
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. 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.
- SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.
- RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.
Explanation
Correct Answer
D:RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. This principle directly explains the controlled acceptance rehearsal: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The aligned engineering response is: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. The result should be established through: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
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: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The controlling mechanism is instead: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The correct response would be: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
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: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The controlling mechanism is instead: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The correct response would be: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
C: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 critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The controlling mechanism is instead: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The correct response would be: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
Question 644
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
- Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
- Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.
- 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.
Explanation
Correct Answer
A:ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. This principle directly explains the controlled acceptance rehearsal: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The aligned engineering response is: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP. The result should be established through: The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.
Incorrect Answers
B: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: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The controlling mechanism is instead: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. The correct response would be: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
C:Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. That explanation applies to the different Filter policy overmatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The controlling mechanism is instead: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. The correct response would be: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
D: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: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The controlling mechanism is instead: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. The correct response would be: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
Question 645
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.
- OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
- OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.
- OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
Explanation
Correct Answer
C:OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. This principle directly explains the controlled acceptance rehearsal: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The aligned engineering response is: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design. The result should be established through: An appropriate eligible router becomes DR or BDR after a controlled election and neighbor adjacency remains stable.
Incorrect Answers
A:OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. That explanation applies to the different Stub area external LSA expectation scenario rather than this controlled acceptance rehearsal. The current fault evidence is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The controlling mechanism is instead: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The correct response would be: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
B: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: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The controlling mechanism is instead: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The correct response would be: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
D:OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. That explanation applies to the different OSPF authentication key mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. The controlling mechanism is instead: OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. The correct response would be: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
Question 646
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.
- Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
- Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
- 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.
Explanation
Correct Answer
D: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. This principle directly explains the controlled acceptance rehearsal: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The aligned engineering response is: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. The result should be established through: With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.
Incorrect Answers
A:An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. That explanation applies to the different Aggregate rejection behavior scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The controlling mechanism is instead: 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. The correct response would be: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
B:Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. That explanation applies to the different Martian-address acceptance scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The controlling mechanism is instead: 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. The correct response would be: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
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 static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The controlling mechanism is instead: 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. The correct response would be: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
Question 647
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
- IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
- IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
- The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
Explanation
Correct Answer
B:IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. This principle directly explains the controlled acceptance rehearsal: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The aligned engineering response is: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. The result should be established through: The LSDB advertises compatible wide metrics and SPF selects the intended path across the upgraded links.
Incorrect Answers
A:Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. That explanation applies to the different IS-IS ISO family missing scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The controlling mechanism is instead: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The correct response would be: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
C:IS-IS relies on a unique system ID to identify LSP originators and topology nodes. That explanation applies to the different Duplicate IS-IS system ID scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The controlling mechanism is instead: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The correct response would be: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
D: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 designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. The controlling mechanism is instead: IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. The correct response would be: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
Question 648
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.
- OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
- 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.
Explanation
Correct Answer
A:Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. This principle directly explains the controlled acceptance rehearsal: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The aligned engineering response is: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries. The result should be established through: ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops.
Incorrect Answers
B:OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. That explanation applies to the different OSPF authentication key mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The controlling mechanism is instead: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. The correct response would be: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.
C: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: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The controlling mechanism is instead: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. The correct response would be: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.
D: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: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The controlling mechanism is instead: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. The correct response would be: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.
Question 649
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
- Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.
- BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
- BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
Explanation
Correct Answer
B:Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. This principle directly explains the controlled acceptance rehearsal: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The aligned engineering response is: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate. The result should be established through: The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.
Incorrect Answers
A:When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. That explanation applies to the different BGP AS-path comparison scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The controlling mechanism is instead: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The correct response would be: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
C:BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. That explanation applies to the different BGP peer autonomous system mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The controlling mechanism is instead: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The correct response would be: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
D:BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. That explanation applies to the different BGP MED comparison scope scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The controlling mechanism is instead: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The correct response would be: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests