Question 680
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. 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.
- BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
- OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
- An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
Explanation
Correct Answer
D:An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. This principle directly explains the controlled acceptance rehearsal: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The aligned engineering response is: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable. The result should be established through: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
Incorrect Answers
A:IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. That explanation applies to the different ICMPv6 packet-too-big handling scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The controlling mechanism is instead: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The correct response would be: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
B: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: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The controlling mechanism is instead: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The correct response would be: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
C:OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. That explanation applies to the different OSPFv3 neighbor uses link-local scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The controlling mechanism is instead: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The correct response would be: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
Question 681
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.
- A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
- 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.
- Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.
Explanation
Correct Answer
B:A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. This principle directly explains the controlled acceptance rehearsal: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The aligned engineering response is: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement. The result should be established through: The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.
Incorrect Answers
A: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-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The controlling mechanism is instead: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The correct response would be: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
C: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-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The controlling mechanism is instead: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The correct response would be: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
D:Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. That explanation applies to the different Inactive route versus forwarding entry scenario rather than this controlled acceptance rehearsal. The current fault evidence is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The controlling mechanism is instead: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The correct response would be: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
Question 682
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.
- 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.
- Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
- A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.
Explanation
Correct Answer
D:A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. This principle directly explains the controlled acceptance rehearsal: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The aligned engineering response is: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route. The result should be established through: The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.
Incorrect Answers
A:Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. That explanation applies to the different Filter-based forwarding classification scenario rather than this controlled acceptance rehearsal. The current fault evidence is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The controlling mechanism is instead: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. The correct response would be: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.
B: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-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The controlling mechanism is instead: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. The correct response would be: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.
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: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The controlling mechanism is instead: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. The correct response would be: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.
Question 683
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.
- ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
- Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
- 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:Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. This principle directly explains the controlled acceptance rehearsal: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The aligned engineering response is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path. The result should be established through: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.
Incorrect Answers
B:ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. That explanation applies to the different Equal-cost multipath eligibility scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The controlling mechanism is instead: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The correct response would be: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
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. That explanation applies to the different Per-flow hash expectation scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The controlling mechanism is instead: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The correct response would be: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
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: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The controlling mechanism is instead: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The correct response would be: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
Question 684
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
- External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
- OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
- Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.
Explanation
Correct Answer
A:OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. This principle directly explains the controlled acceptance rehearsal: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The aligned engineering response is: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection. The result should be established through: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
Incorrect Answers
B: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: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The controlling mechanism is instead: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The correct response would be: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
C:OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. That explanation applies to the different Duplicate OSPF router identifier scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The controlling mechanism is instead: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The correct response would be: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
D: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: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The controlling mechanism is instead: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The correct response would be: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
Question 685
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
- IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
- An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
- Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
Explanation
Correct Answer
D:Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. This principle directly explains the controlled acceptance rehearsal: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The aligned engineering response is: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone. The result should be established through: A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.
Incorrect Answers
A:The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. That explanation applies to the different IS-IS DIS election surprise scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The controlling mechanism is instead: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The correct response would be: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
B: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: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The controlling mechanism is instead: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The correct response would be: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
C:An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. That explanation applies to the different IS-IS overload-state recovery scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The controlling mechanism is instead: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The correct response would be: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
Question 686
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
- OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
- BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
- An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
Explanation
Correct Answer
B:OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. This principle directly explains the controlled acceptance rehearsal: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The aligned engineering response is: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity. The result should be established through: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
Incorrect Answers
A:IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. That explanation applies to the different IS-IS IPv6 reachability TLVs scenario rather than this controlled acceptance rehearsal. The current fault evidence is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The controlling mechanism is instead: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The correct response would be: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
C: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: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The controlling mechanism is instead: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The correct response would be: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
D: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: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The controlling mechanism is instead: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The correct response would be: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
Question 687
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.
- GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel.
- GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
- GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
Explanation
Correct Answer
B:GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. This principle directly explains the controlled acceptance rehearsal: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. The aligned engineering response is: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path. The result should be established through: Packet captures show the expected outer GRE addresses and matching decapsulation counts on the peer.
Incorrect Answers
A:GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. That explanation applies to the different GRE underlay recursive loss scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. The controlling mechanism is instead: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The correct response would be: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
C:GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. That explanation applies to the different GRE encapsulation MTU overhead scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. The controlling mechanism is instead: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The correct response would be: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
D:GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. That explanation applies to the different GRE confidentiality misconception scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two routers have interface-based GRE tunnels, but the source address on one end does not match the destination configured on the remote end. The controlling mechanism is instead: GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. The correct response would be: Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
Question 688
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. 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.
- 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.
- 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
D:An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. This principle directly explains the controlled acceptance rehearsal: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The aligned engineering response is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination. The result should be established through: A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
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: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The controlling mechanism is instead: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The correct response would be: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
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: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The controlling mechanism is instead: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The correct response would be: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
C: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-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The controlling mechanism is instead: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The correct response would be: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
Question 689
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. 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.
- IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.
- An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
- BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.
Explanation
Correct Answer
A:BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. This principle directly explains the controlled acceptance rehearsal: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The aligned engineering response is: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. The result should be established through: The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.
Incorrect Answers
B:IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. That explanation applies to the different IBGP loopback source resolution scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The controlling mechanism is instead: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. The correct response would be: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
C: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 BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The controlling mechanism is instead: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. The correct response would be: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
D:BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. That explanation applies to the different BGP next-hop inaccessible scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The controlling mechanism is instead: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. The correct response would be: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
Question 690
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- An IS-IS adjacency needs compatible protocol levels as well as link reachability.
- The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
- IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
- IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
Explanation
Correct Answer
A:An IS-IS adjacency needs compatible protocol levels as well as link reachability. This principle directly explains the controlled acceptance rehearsal: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The aligned engineering response is: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design. The result should be established through: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.
Incorrect Answers
B:The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. That explanation applies to the different IS-IS DIS election surprise scenario rather than this controlled acceptance rehearsal. The current fault evidence is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The controlling mechanism is instead: An IS-IS adjacency needs compatible protocol levels as well as link reachability. The correct response would be: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
C: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: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The controlling mechanism is instead: An IS-IS adjacency needs compatible protocol levels as well as link reachability. The correct response would be: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
D: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: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The controlling mechanism is instead: An IS-IS adjacency needs compatible protocol levels as well as link reachability. The correct response would be: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests