Question 550
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
- Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
- Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
- Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
Explanation
Correct Answer
B:Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design. In the controlled acceptance rehearsal, the reported evidence is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The intervention follows the governing fact that Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. Closure requires the corresponding specific confirmation: The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
Incorrect Answers
A:Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port. This action was designed for the separate Unknown unicast flooding behavior case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Its governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The narrower applicable remedy is: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
C:Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership. This action was designed for the separate Virtual switch instance membership case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Its governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The narrower applicable remedy is: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
D:Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end. This action was designed for the separate Trunk allowed VLAN omission case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Its governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The narrower applicable remedy is: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
Question 551
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
- Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
- Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
- Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.
Explanation
Correct Answer
D:Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation. In the controlled acceptance rehearsal, the reported evidence is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. The intervention follows the governing fact that GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. Closure requires the corresponding specific confirmation: A validated encryption layer protects inner payload on the monitored underlay while GRE routing still functions as designed.
Incorrect Answers
A:Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform. This action was designed for the separate GRE encapsulation MTU overhead case, not the controlled acceptance rehearsal being assessed. The present observation is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. Its governing mechanism is: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. The narrower applicable remedy is: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.
B:Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path. This action was designed for the separate GRE tunnel endpoint mismatch case, not the controlled acceptance rehearsal being assessed. The present observation is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. Its governing mechanism is: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. The narrower applicable remedy is: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.
C:Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself. This action was designed for the separate GRE underlay recursive loss case, not the controlled acceptance rehearsal being assessed. The present observation is: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. Its governing mechanism is: GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. The narrower applicable remedy is: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.
Question 552
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 narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
- Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
- Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
- Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.
Explanation
Correct Answer
D:Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation. In the controlled acceptance rehearsal, the reported evidence is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The intervention follows the governing fact that Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. Closure requires the corresponding specific confirmation: Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view.
Incorrect Answers
A:Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design. This action was designed for the separate Administrative preference overrides static case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. Its governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The narrower applicable remedy is: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.
B:Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior. This action was designed for the separate Generated default route prerequisite case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. Its governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The narrower applicable remedy is: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.
C:Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination. This action was designed for the separate Aggregate rejection behavior case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. Its governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The narrower applicable remedy is: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.
Question 553
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
- Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends.
- Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
- Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
Explanation
Correct Answer
A:Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required. In the controlled acceptance rehearsal, the reported evidence is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The intervention follows the governing fact that When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. Closure requires the corresponding specific confirmation: A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.
Incorrect Answers
B:Configure an approved eBGP multihop arrangement with suitable TTL and reachable peer addresses at both ends. This action was designed for the separate EBGP multihop peering case, not the controlled acceptance rehearsal being assessed. The present observation is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Its governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The narrower applicable remedy is: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
C:Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. This action was designed for the separate BGP import policy leak case, not the controlled acceptance rehearsal being assessed. The present observation is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Its governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The narrower applicable remedy is: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
D:Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context. This action was designed for the separate BGP IPv6 family inactive case, not the controlled acceptance rehearsal being assessed. The present observation is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Its governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The narrower applicable remedy is: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
Question 554
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
- Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
- Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.
- Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.
Explanation
Correct Answer
B:Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement. In the controlled acceptance rehearsal, the reported evidence is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The intervention follows the governing fact that Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. Closure requires the corresponding specific confirmation: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
Incorrect Answers
A:Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF. This action was designed for the separate OSPF LSDB discrepancy case, not the controlled acceptance rehearsal being assessed. The present observation is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Its governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The narrower applicable remedy is: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
C:Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries. This action was designed for the separate OSPF backbone connectivity case, not the controlled acceptance rehearsal being assessed. The present observation is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Its governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The narrower applicable remedy is: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
D:Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state. This action was designed for the separate Duplicate OSPF router identifier case, not the controlled acceptance rehearsal being assessed. The present observation is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Its governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The narrower applicable remedy is: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
Question 555
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
- Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
- Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
- Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
Explanation
Correct Answer
C:Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls. In the controlled acceptance rehearsal, the reported evidence is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The intervention follows the governing fact that LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. Closure requires the corresponding specific confirmation: An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
Incorrect Answers
A:Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the controlled acceptance rehearsal being assessed. The present observation is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. Its governing mechanism is: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The narrower applicable remedy is: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
B:Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress. This action was designed for the separate Explicit-null forwarding case, not the controlled acceptance rehearsal being assessed. The present observation is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. Its governing mechanism is: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The narrower applicable remedy is: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
D:Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth. This action was designed for the separate RSVP reservable bandwidth shortage case, not the controlled acceptance rehearsal being assessed. The present observation is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. Its governing mechanism is: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The narrower applicable remedy is: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
Question 556
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.
- Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
- Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
- Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.
Explanation
Correct Answer
A:Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it. In the controlled acceptance rehearsal, the reported evidence is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. The intervention follows the governing fact that BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. Closure requires the corresponding specific confirmation: The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.
Incorrect Answers
B:Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. This action was designed for the separate BGP import policy leak case, not the controlled acceptance rehearsal being assessed. The present observation is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. Its governing mechanism is: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The narrower applicable remedy is: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.
C:Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context. This action was designed for the separate BGP IPv6 family inactive case, not the controlled acceptance rehearsal being assessed. The present observation is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. Its governing mechanism is: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The narrower applicable remedy is: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.
D:Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy. This action was designed for the separate BGP peer flap from mismatched hold timers case, not the controlled acceptance rehearsal being assessed. The present observation is: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. Its governing mechanism is: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The narrower applicable remedy is: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.
Question 557
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
- Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
- Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
- Correct the actual transport MTU mismatch across the link, then validate database description exchange.
Explanation
Correct Answer
C:Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF. In the controlled acceptance rehearsal, the reported evidence is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. The intervention follows the governing fact that Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. Closure requires the corresponding specific confirmation: Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
Incorrect Answers
A:Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub. This action was designed for the separate Stub area external LSA expectation case, not the controlled acceptance rehearsal being assessed. The present observation is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. Its governing mechanism is: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. The narrower applicable remedy is: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
B:Set the correct point-to-point OSPF interface type where supported and aligned at both ends. This action was designed for the separate Point-to-point OSPF network type case, not the controlled acceptance rehearsal being assessed. The present observation is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. Its governing mechanism is: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. The narrower applicable remedy is: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
D:Correct the actual transport MTU mismatch across the link, then validate database description exchange. This action was designed for the separate OSPF MTU ExStart stall case, not the controlled acceptance rehearsal being assessed. The present observation is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. Its governing mechanism is: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. The narrower applicable remedy is: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
Question 558
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
- Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
- Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
- Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
Explanation
Correct Answer
C:Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design. In the controlled acceptance rehearsal, the reported evidence is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. The intervention follows the governing fact that IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. Closure requires the corresponding specific confirmation: The session establishes using the intended loopback source and destination and stays up after a physical link fails.
Incorrect Answers
A:Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. This action was designed for the separate BGP import policy leak case, not the controlled acceptance rehearsal being assessed. The present observation is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. Its governing mechanism is: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. The narrower applicable remedy is: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
B:Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required. This action was designed for the separate BGP AS-path comparison case, not the controlled acceptance rehearsal being assessed. The present observation is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. Its governing mechanism is: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. The narrower applicable remedy is: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
D:Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context. This action was designed for the separate BGP IPv6 family inactive case, not the controlled acceptance rehearsal being assessed. The present observation is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. Its governing mechanism is: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. The narrower applicable remedy is: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
Question 559
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 narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.
- Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.
- Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
- Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
Explanation
Correct Answer
C:Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity. In the controlled acceptance rehearsal, the reported 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 intervention follows the governing fact that OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. Closure requires the corresponding specific confirmation: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.
Incorrect Answers
A:Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database. This action was designed for the separate IS-IS IPv6 reachability TLVs case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The narrower applicable remedy is: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
B:Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops. This action was designed for the separate IPv6 BGP NLRI family omitted case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The narrower applicable remedy is: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
D:Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable. This action was designed for the separate IPv6 static link-local next hop case, not the controlled acceptance rehearsal being assessed. The present observation 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. Its governing mechanism is: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The narrower applicable remedy is: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
Question 560
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
- Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
- Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
- Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
Explanation
Correct Answer
A:Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information. In the controlled acceptance rehearsal, the reported evidence is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The intervention follows the governing fact that IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. Closure requires the corresponding specific confirmation: LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.
Incorrect Answers
B:Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. This action was designed for the separate IS-IS DIS election surprise case, not the controlled acceptance rehearsal being assessed. The present observation is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Its governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The narrower applicable remedy is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
C:Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone. This action was designed for the separate IS-IS Level 1 exit default case, not the controlled acceptance rehearsal being assessed. The present observation is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Its governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The narrower applicable remedy is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
D:Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established. This action was designed for the separate IS-IS overload-state recovery case, not the controlled acceptance rehearsal being assessed. The present observation is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Its governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The narrower applicable remedy is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests