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.
Question 631
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.
- Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
- Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.
- Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
Explanation
Correct Answer
B:Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. This principle directly explains the controlled acceptance rehearsal: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The aligned engineering response is: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design. The result should be established through: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
Incorrect Answers
A:An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. That explanation applies to the different Access VLAN membership scenario rather than this controlled acceptance rehearsal. The current fault evidence is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The controlling mechanism is instead: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The correct response would be: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
C:Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. That explanation applies to the different Provider VLAN customer isolation scenario rather than this controlled acceptance rehearsal. The current fault evidence is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The controlling mechanism is instead: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The correct response would be: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
D: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: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The controlling mechanism is instead: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The correct response would be: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
Question 632
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.
- Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
- Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
- RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
Explanation
Correct Answer
C:Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. This principle directly explains the controlled acceptance rehearsal: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The aligned engineering response is: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment. The result should be established through: The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.
Incorrect Answers
A: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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The controlling mechanism is instead: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The correct response would be: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
B: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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The controlling mechanism is instead: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The correct response would be: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
D: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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The controlling mechanism is instead: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The correct response would be: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
Question 633
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
- IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
- The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
- When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.
Explanation
Correct Answer
B:IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. This principle directly explains the controlled acceptance rehearsal: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The aligned engineering response is: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible. The result should be established through: The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
Incorrect Answers
A:IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. That explanation applies to the different IS-IS narrow metric ceiling scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The controlling mechanism is instead: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The correct response would be: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
C: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 service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The controlling mechanism is instead: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The correct response would be: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
D:When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. That explanation applies to the different IS-IS authentication mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The controlling mechanism is instead: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The correct response would be: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
Question 634
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.
- An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.
- An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
- BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
Explanation
Correct Answer
A:IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. This principle directly explains the controlled acceptance rehearsal: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The aligned engineering response is: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path. The result should be established through: Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.
Incorrect Answers
B:An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. That explanation applies to the different IPv6 over IPv4 transit tunnel scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The controlling mechanism is instead: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. The correct response would be: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
C:An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. That explanation applies to the different IPv6 static link-local next hop scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The controlling mechanism is instead: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. The correct response would be: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
D:BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. That explanation applies to the different IPv6 BGP NLRI family omitted scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The controlling mechanism is instead: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. The correct response would be: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
Question 635
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.
- Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
- Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
- An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.
Explanation
Correct Answer
C:Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. This principle directly explains the controlled acceptance rehearsal: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The aligned engineering response is: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation. The result should be established through: Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view.
Incorrect Answers
A:For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. That explanation applies to the different Administrative preference overrides static scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The controlling mechanism is instead: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The correct response would be: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.
B: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 routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The controlling mechanism is instead: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The correct response would be: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.
D: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 customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The controlling mechanism is instead: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The correct response would be: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.
Question 636
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. 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.
- RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
- 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
C:SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. This principle directly explains the controlled acceptance rehearsal: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The aligned engineering response is: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers. The result should be established through: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.
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: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The controlling mechanism is instead: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The correct response would be: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
B: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: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The controlling mechanism is instead: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The correct response would be: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
D: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: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The controlling mechanism is instead: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The correct response would be: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
Question 637
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. 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.
- 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 address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
Explanation
Correct Answer
D:BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. This principle directly explains the controlled acceptance rehearsal: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. The aligned engineering response is: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context. The result should be established through: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
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: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. The controlling mechanism is instead: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The correct response would be: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
B: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: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. The controlling mechanism is instead: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The correct response would be: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
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: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. The controlling mechanism is instead: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The correct response would be: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
Question 638
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. 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.
- External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
- Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
Explanation
Correct Answer
C:External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. This principle directly explains the controlled acceptance rehearsal: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The aligned engineering response is: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions. The result should be established through: The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
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: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The controlling mechanism is instead: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The correct response would be: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
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: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The controlling mechanism is instead: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The correct response would be: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
D:Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. That explanation applies to the different OSPF LSDB discrepancy scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The controlling mechanism is instead: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The correct response would be: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
Question 639
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
- MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
- RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
- Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
Explanation
Correct Answer
C:RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. This principle directly explains the controlled acceptance rehearsal: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The aligned engineering response is: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design. The result should be established through: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.
Incorrect Answers
A:LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. That explanation applies to the different LDP TCP 646 establishment scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The controlling mechanism is instead: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The correct response would be: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
B: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 customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The controlling mechanism is instead: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The correct response would be: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
D: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 customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The controlling mechanism is instead: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The correct response would be: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests