Question 620
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
- Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
- Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
- Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
Explanation
Correct Answer
C:Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. This principle directly explains the controlled acceptance rehearsal: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. The aligned engineering response is: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change. The result should be established through: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.
Incorrect Answers
A:Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. That explanation applies to the different Generated default route prerequisite scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. The controlling mechanism is instead: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The correct response would be: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
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 customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. The controlling mechanism is instead: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The correct response would be: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
D: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 customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. The controlling mechanism is instead: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The correct response would be: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
Question 621
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
- BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.
- BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
- An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
Explanation
Correct Answer
C:BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. This principle directly explains the controlled acceptance rehearsal: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The aligned engineering response is: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes. The result should be established through: The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.
Incorrect Answers
A: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 route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The controlling mechanism is instead: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. The correct response would be: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.
B: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: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The controlling mechanism is instead: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. The correct response would be: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.
D:An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. That explanation applies to the different EBGP multihop peering scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The controlling mechanism is instead: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. The correct response would be: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.
Question 622
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
- Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.
- OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
- OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
Explanation
Correct Answer
D:OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. This principle directly explains the controlled acceptance rehearsal: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The aligned engineering response is: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange. The result should be established through: Both peers reach Full adjacency in the same area and the intended routes are learned.
Incorrect Answers
A: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: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The controlling mechanism is instead: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The correct response would be: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
B:Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. That explanation applies to the different OSPF passive interface scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The controlling mechanism is instead: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The correct response would be: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
C: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: Two PE routers exchange OSPF Hello packets on the same Ethernet segment but stay Down because one interface belongs to area 0 and the other to area 10. The controlling mechanism is instead: OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. The correct response would be: Place both adjacency interfaces into the intended matching OSPF area, then validate neighbor exchange.
Question 623
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
- GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions.
- NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
- LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
Explanation
Correct Answer
D:LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. This principle directly explains the controlled acceptance rehearsal: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The aligned engineering response is: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation. The result should be established through: All intended members show collecting and distributing state in the correct AE bundle and packet forwarding is stable.
Incorrect Answers
A: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: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The controlling mechanism is instead: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The correct response would be: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
B:GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. That explanation applies to the different GRES forwarding versus routing continuity scenario rather than this controlled acceptance rehearsal. The current fault evidence is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The controlling mechanism is instead: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The correct response would be: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
C:NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. That explanation applies to the different NSR backup routing synchronization scenario rather than this controlled acceptance rehearsal. The current fault evidence is: One aggregated Ethernet member is physically up but never bundles because the link partner's LACP identity or configured aggregation key differs. The controlling mechanism is instead: LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. The correct response would be: Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
Question 624
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
- Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
- Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
- A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
Explanation
Correct Answer
B:Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. This principle directly explains the controlled acceptance rehearsal: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The aligned engineering response is: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership. The result should be established through: The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
Incorrect Answers
A:A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. That explanation applies to the different Unknown unicast flooding behavior scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The controlling mechanism is instead: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. The correct response would be: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
C:Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. That explanation applies to the different MAC move instability scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The controlling mechanism is instead: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. The correct response would be: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
D: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 provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The controlling mechanism is instead: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. The correct response would be: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
Question 625
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
- Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.
- External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
- OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
Explanation
Correct Answer
D:OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. This principle directly explains the controlled acceptance rehearsal: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The aligned engineering response is: Correct the actual transport MTU mismatch across the link, then validate database description exchange. The result should be established through: Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB.
Incorrect Answers
A: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: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The controlling mechanism is instead: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. The correct response would be: Correct the actual transport MTU mismatch across the link, then validate database description exchange.
B:Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. That explanation applies to the different OSPF backbone connectivity scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The controlling mechanism is instead: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. The correct response would be: Correct the actual transport MTU mismatch across the link, then validate database description exchange.
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: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The controlling mechanism is instead: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. The correct response would be: Correct the actual transport MTU mismatch across the link, then validate database description exchange.
Question 626
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
- BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.
- BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
- Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.
Explanation
Correct Answer
A:BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. This principle directly explains the controlled acceptance rehearsal: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The aligned engineering response is: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters. The result should be established through: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
Incorrect Answers
B: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: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The controlling mechanism is instead: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The correct response would be: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
C:BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. That explanation applies to the different BGP TCP transport blocked scenario rather than this controlled acceptance rehearsal. The current fault evidence is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The controlling mechanism is instead: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The correct response would be: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
D:Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. That explanation applies to the different IBGP transit split horizon scenario rather than this controlled acceptance rehearsal. The current fault evidence is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The controlling mechanism is instead: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The correct response would be: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.
Question 627
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
- RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
- Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
- VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.
Explanation
Correct Answer
B:RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. This principle directly explains the controlled acceptance rehearsal: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. The aligned engineering response is: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition. The result should be established through: A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.
Incorrect Answers
A:Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. That explanation applies to the different Root protection against rogue core scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. The controlling mechanism is instead: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The correct response would be: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
C:Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. That explanation applies to the different Unexpected BPDU on edge port scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. The controlling mechanism is instead: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The correct response would be: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
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: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. The controlling mechanism is instead: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The correct response would be: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
Question 628
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.
- RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
- Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.
- Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
Explanation
Correct Answer
C:Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. This principle directly explains the controlled acceptance rehearsal: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The aligned engineering response is: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support. The result should be established through: The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
Incorrect Answers
A:Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. That explanation applies to the different Root bridge election priority scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The controlling mechanism is instead: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The correct response would be: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
B: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: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The controlling mechanism is instead: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The correct response would be: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
D:Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. That explanation applies to the different Root protection against rogue core scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The controlling mechanism is instead: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The correct response would be: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
Question 629
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.
- RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.
- MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
- SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.
Explanation
Correct Answer
A:LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. This principle directly explains the controlled acceptance rehearsal: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The aligned engineering response is: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution. The result should be established through: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
Incorrect Answers
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 provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The controlling mechanism is instead: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The correct response would be: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.
C:MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. That explanation applies to the different Incoming label missing in LFIB scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The controlling mechanism is instead: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The correct response would be: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.
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 provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The controlling mechanism is instead: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The correct response would be: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.
Question 630
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
- BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.
- An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
- 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
C:An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. This principle directly explains the controlled acceptance rehearsal: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. The aligned engineering response is: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends. The result should be established through: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
Incorrect Answers
A: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 remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. The controlling mechanism is instead: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The correct response would be: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
B: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: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. The controlling mechanism is instead: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The correct response would be: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
D:Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. That explanation applies to the different BGP local preference egress scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. The controlling mechanism is instead: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The correct response would be: Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests