Question 660
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.
- Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
- Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
- Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
Explanation
Correct Answer
A:Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. This principle directly explains the controlled acceptance rehearsal: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The aligned engineering response is: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag. The result should be established through: A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.
Incorrect Answers
B:Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. That explanation applies to the different Native VLAN mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The controlling mechanism is instead: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The correct response would be: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
C: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: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The controlling mechanism is instead: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The correct response would be: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
D:Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. That explanation applies to the different Virtual switch instance membership scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The controlling mechanism is instead: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The correct response would be: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
Question 661
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 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.
- Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
- Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.
- RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
Explanation
Correct Answer
A:LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. This principle directly explains the controlled acceptance rehearsal: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The aligned engineering response is: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls. The result should be established through: An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
Incorrect Answers
B: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: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The controlling mechanism is instead: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The correct response would be: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
C:Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. That explanation applies to the different Explicit-null forwarding scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The controlling mechanism is instead: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The correct response would be: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
D: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: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The controlling mechanism is instead: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The correct response would be: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
Question 662
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.
- BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
- Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.
- BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.
Explanation
Correct Answer
B:BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. This principle directly explains the controlled acceptance rehearsal: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The aligned engineering response is: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability. The result should be established through: A TCP session is established to the correct neighbor address, BGP reaches Established and intended routes are exchanged.
Incorrect Answers
A:BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. That explanation applies to the different BGP import policy leak scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The controlling mechanism is instead: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. The correct response would be: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.
C:Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. That explanation applies to the different IBGP transit split horizon scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The controlling mechanism is instead: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. The correct response would be: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.
D:BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. That explanation applies to the different BGP peer flap from mismatched hold timers scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. The controlling mechanism is instead: BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. The correct response would be: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.
Question 663
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
- Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
- 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.
Explanation
Correct Answer
C: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. This principle directly explains the controlled acceptance rehearsal: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The aligned engineering response is: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes. The result should be established through: Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.
Incorrect Answers
A:Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. That explanation applies to the different Martian-address acceptance scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The controlling mechanism is instead: 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. The correct response would be: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.
B: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 provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The controlling mechanism is instead: 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. The correct response would be: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.
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 provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The controlling mechanism is instead: 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. The correct response would be: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.
Question 664
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
- A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
- An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.
- A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
Explanation
Correct Answer
D:A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. This principle directly explains the controlled acceptance rehearsal: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The aligned engineering response is: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end. The result should be established through: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
Incorrect Answers
A:An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. That explanation applies to the different IRB routed gateway missing scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The controlling mechanism is instead: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The correct response would be: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
B:A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. That explanation applies to the different Unknown unicast flooding behavior scenario rather than this controlled acceptance rehearsal. The current fault evidence is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The controlling mechanism is instead: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The correct response would be: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
C: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: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The controlling mechanism is instead: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The correct response would be: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.
Question 665
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. 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 encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
- GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
Explanation
Correct Answer
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. This principle directly explains the controlled acceptance rehearsal: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The aligned engineering response is: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself. The result should be established through: An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.
Incorrect Answers
B:GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. That explanation applies to the different GRE tunnel endpoint mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The controlling mechanism is instead: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The correct response would be: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
C: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: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The controlling mechanism is instead: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The correct response would be: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
D: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: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The controlling mechanism is instead: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The correct response would be: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
Question 666
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 underlying Junos routing, switching, or protocol principle best explains this specific observation?
- A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
- Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.
- Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
- A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
Explanation
Correct Answer
B:Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. This principle directly explains the controlled acceptance rehearsal: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The aligned engineering response is: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design. The result should be established through: The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.
Incorrect Answers
A:A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. That explanation applies to the different Unknown unicast flooding behavior scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The controlling mechanism is instead: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The correct response would be: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
C:Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. That explanation applies to the different Virtual switch instance membership scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The controlling mechanism is instead: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The correct response would be: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
D:A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. That explanation applies to the different Trunk allowed VLAN omission scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The controlling mechanism is instead: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The correct response would be: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
Question 667
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
- 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.
- LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
Explanation
Correct Answer
A:RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. This principle directly explains the controlled acceptance rehearsal: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The aligned engineering response is: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling. The result should be established through: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.
Incorrect Answers
B: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 RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The controlling mechanism is instead: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The correct response would be: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.
C: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 RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The controlling mechanism is instead: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The correct response would be: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.
D: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: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The controlling mechanism is instead: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The correct response would be: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.
Question 668
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
- IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
- 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.
- Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
Explanation
Correct Answer
D:Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. This principle directly explains the controlled acceptance rehearsal: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. The aligned engineering response is: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation. The result should be established through: IS-IS Hello exchanges appear and the expected level adjacency establishes while IPv4 traffic still functions.
Incorrect Answers
A:IS-IS relies on a unique system ID to identify LSP originators and topology nodes. That explanation applies to the different Duplicate IS-IS system ID scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. The controlling mechanism is instead: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The correct response would be: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
B: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 router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. The controlling mechanism is instead: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The correct response would be: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
C: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. That explanation applies to the different IS-IS Level 1 exit default scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A router interface carries IPv4 traffic and is listed under IS-IS, but no IS-IS Hello packets form because the required ISO protocol family is absent. The controlling mechanism is instead: Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. The correct response would be: Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
Question 669
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
- 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.
- A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints.
Explanation
Correct Answer
B:MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. This principle directly explains the controlled acceptance rehearsal: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The aligned engineering response is: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC. The result should be established through: A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
Incorrect Answers
A: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: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The controlling mechanism is instead: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. The correct response would be: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
C:RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. That explanation applies to the different RSVP LSP directionality scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The controlling mechanism is instead: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. The correct response would be: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
D:A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. That explanation applies to the different SR-MPLS node-SID shortest path scenario rather than this controlled acceptance rehearsal. The current fault evidence is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The controlling mechanism is instead: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. The correct response would be: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
Question 670
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. 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.
- OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
- OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
- External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
Explanation
Correct Answer
B:OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. This principle directly explains the controlled acceptance rehearsal: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The aligned engineering response is: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state. The result should be established through: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
Incorrect Answers
A: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: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The controlling mechanism is instead: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The correct response would be: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.
C:OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. That explanation applies to the different OSPF authentication key mismatch scenario rather than this controlled acceptance rehearsal. The current fault evidence is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The controlling mechanism is instead: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The correct response would be: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.
D:External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. That explanation applies to the different OSPF export policy omission scenario rather than this controlled acceptance rehearsal. The current fault evidence is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The controlling mechanism is instead: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The correct response would be: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests