Question 850
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. An engineer suggests the shortcut: "Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag." Which critique explains the specific risk of that shortcut?
- A duplicate name does not move frames into the intended instance and can increase configuration confusion.
- Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership.
- Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved.
- Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs.
Explanation
Correct Answer
C:Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It fails to resolve the underlying problem that Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. A sound alternative is the targeted engineering action: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.
Incorrect Answers
A:A duplicate name does not move frames into the intended instance and can increase configuration confusion. That critique concerns a shortcut from the unrelated Virtual switch instance membership case. The shortcut actually proposed in this controlled acceptance rehearsal is: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It should be rejected for the narrower reason that Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. This distinction matters because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
B:Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. That critique concerns a shortcut from the unrelated Trunk allowed VLAN omission case. The shortcut actually proposed in this controlled acceptance rehearsal is: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It should be rejected for the narrower reason that Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. This distinction matters because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
D:Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. That critique concerns a shortcut from the unrelated Native VLAN mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Rewrite the customer inner VLAN identifiers to mask the mismatched service outer tag. It should be rejected for the narrower reason that Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. This distinction matters because Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
Question 851
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. An engineer suggests the shortcut: "Add an extra prefix advertisement to the export policy while the TCP session is blocked." Which critique explains the specific risk of that shortcut?
- Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session.
- Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
- Session liveness timers do not change IBGP route propagation rules.
- Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers.
Explanation
Correct Answer
A:Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add an extra prefix advertisement to the export policy while the TCP session is blocked. It fails to resolve the underlying problem that BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. A sound alternative is the targeted engineering action: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.
Incorrect Answers
B:Remote-side policy is outside local control and does not enforce an explicit receiving security boundary. That critique concerns a shortcut from the unrelated BGP import policy leak case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add an extra prefix advertisement to the export policy while the TCP session is blocked. It should be rejected for the narrower reason that Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session. This distinction matters because BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
C:Session liveness timers do not change IBGP route propagation rules. That critique concerns a shortcut from the unrelated IBGP transit split horizon case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add an extra prefix advertisement to the export policy while the TCP session is blocked. It should be rejected for the narrower reason that Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session. This distinction matters because BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
D:Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers. That critique concerns a shortcut from the unrelated BGP peer flap from mismatched hold timers case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add an extra prefix advertisement to the export policy while the TCP session is blocked. It should be rejected for the narrower reason that Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session. This distinction matters because BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
Question 852
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. An engineer suggests the shortcut: "Apply an export policy accepting every direct and static route." Which critique explains the specific risk of that shortcut?
- Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
- OSPF election settings are unrelated to IS-IS DIS selection on the LAN.
- Broad deactivation removes protections and can expose the link-state domain to untrusted control packets.
- Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops.
Explanation
Correct Answer
D:Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Apply an export policy accepting every direct and static route. It fails to resolve the underlying problem that IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. A sound alternative is the targeted engineering action: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
Incorrect Answers
A:Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. That critique concerns a shortcut from the unrelated IS-IS narrow metric ceiling case. The shortcut actually proposed in this controlled acceptance rehearsal is: Apply an export policy accepting every direct and static route. It should be rejected for the narrower reason that Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. This distinction matters because IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
B:OSPF election settings are unrelated to IS-IS DIS selection on the LAN. That critique concerns a shortcut from the unrelated IS-IS DIS election surprise case. The shortcut actually proposed in this controlled acceptance rehearsal is: Apply an export policy accepting every direct and static route. It should be rejected for the narrower reason that Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. This distinction matters because IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
C:Broad deactivation removes protections and can expose the link-state domain to untrusted control packets. That critique concerns a shortcut from the unrelated IS-IS authentication mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Apply an export policy accepting every direct and static route. It should be rejected for the narrower reason that Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. This distinction matters because IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
Question 853
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. An engineer suggests the shortcut: "Add more IPv4 static routes without fixing the VLAN-tag-to-unit mapping." Which critique explains the specific risk of that shortcut?
- Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding.
- IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong.
- An aging change cannot prevent contradictory source-MAC observations on multiple ports.
- Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs.
Explanation
Correct Answer
B:IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add more IPv4 static routes without fixing the VLAN-tag-to-unit mapping. It fails to resolve the underlying problem that Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. A sound alternative is the targeted engineering action: Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.
Incorrect Answers
A:Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. That critique concerns a shortcut from the unrelated Unknown unicast flooding behavior case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add more IPv4 static routes without fixing the VLAN-tag-to-unit mapping. It should be rejected for the narrower reason that IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong. This distinction matters because Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
C:An aging change cannot prevent contradictory source-MAC observations on multiple ports. That critique concerns a shortcut from the unrelated MAC move instability case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add more IPv4 static routes without fixing the VLAN-tag-to-unit mapping. It should be rejected for the narrower reason that IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong. This distinction matters because Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
D:Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. That critique concerns a shortcut from the unrelated Native VLAN mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add more IPv4 static routes without fixing the VLAN-tag-to-unit mapping. It should be rejected for the narrower reason that IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong. This distinction matters because Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
Question 854
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. An engineer suggests the shortcut: "Add an IPv6 address to the physical interface but leave BGP family negotiation unchanged." Which critique explains the specific risk of that shortcut?
- OSPF LAN DR election settings do not modify the BGP path attributes being compared.
- Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy.
- Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI.
- Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers.
Explanation
Correct Answer
C:Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add an IPv6 address to the physical interface but leave BGP family negotiation unchanged. It fails to resolve the underlying problem that BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. A sound alternative is the targeted engineering action: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
Incorrect Answers
A:OSPF LAN DR election settings do not modify the BGP path attributes being compared. That critique concerns a shortcut from the unrelated BGP AS-path comparison case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add an IPv6 address to the physical interface but leave BGP family negotiation unchanged. It should be rejected for the narrower reason that Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI. This distinction matters because BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
B:Router IDs are late tie-breakers and duplicating them cannot replace proper MED comparison or policy. That critique concerns a shortcut from the unrelated BGP MED comparison scope case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add an IPv6 address to the physical interface but leave BGP family negotiation unchanged. It should be rejected for the narrower reason that Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI. This distinction matters because BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
D:Suppressing logs hides liveness evidence and cannot repair lost control traffic or poorly chosen timers. That critique concerns a shortcut from the unrelated BGP peer flap from mismatched hold timers case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add an IPv6 address to the physical interface but leave BGP family negotiation unchanged. It should be rejected for the narrower reason that Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI. This distinction matters because BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
Question 855
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. An engineer suggests the shortcut: "Clear overload immediately at boot before route and forwarding synchronization." Which critique explains the specific risk of that shortcut?
- Premature transit eligibility can blackhole traffic while the node has incomplete routing state.
- Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy.
- Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes.
- Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling.
Explanation
Correct Answer
A:Premature transit eligibility can blackhole traffic while the node has incomplete routing state. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Clear overload immediately at boot before route and forwarding synchronization. It fails to resolve the underlying problem that An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. A sound alternative is the targeted engineering action: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
Incorrect Answers
B:Mass static redistribution adds scale and maintenance risk instead of using the designed hierarchy. That critique concerns a shortcut from the unrelated IS-IS Level 1 exit default case. The shortcut actually proposed in this controlled acceptance rehearsal is: Clear overload immediately at boot before route and forwarding synchronization. It should be rejected for the narrower reason that Premature transit eligibility can blackhole traffic while the node has incomplete routing state. This distinction matters because An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
C:Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. That critique concerns a shortcut from the unrelated IS-IS LSP lifetime anomaly case. The shortcut actually proposed in this controlled acceptance rehearsal is: Clear overload immediately at boot before route and forwarding synchronization. It should be rejected for the narrower reason that Premature transit eligibility can blackhole traffic while the node has incomplete routing state. This distinction matters because An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
D:Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. That critique concerns a shortcut from the unrelated IS-IS ISO family missing case. The shortcut actually proposed in this controlled acceptance rehearsal is: Clear overload immediately at boot before route and forwarding synchronization. It should be rejected for the narrower reason that Premature transit eligibility can blackhole traffic while the node has incomplete routing state. This distinction matters because An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
Question 856
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. An engineer suggests the shortcut: "Disable authentication permanently on one neighbor to force the adjacency up." Which critique explains the specific risk of that shortcut?
- DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link.
- Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection.
- A process reset can temporarily restart negotiation but leaves the same incompatibility in place.
- Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks.
Explanation
Correct Answer
B:Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Disable authentication permanently on one neighbor to force the adjacency up. It fails to resolve the underlying problem that OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. A sound alternative is the targeted engineering action: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
Incorrect Answers
A:DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link. That critique concerns a shortcut from the unrelated Point-to-point OSPF network type case. The shortcut actually proposed in this controlled acceptance rehearsal is: Disable authentication permanently on one neighbor to force the adjacency up. It should be rejected for the narrower reason that Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. This distinction matters because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
C:A process reset can temporarily restart negotiation but leaves the same incompatibility in place. That critique concerns a shortcut from the unrelated OSPF MTU ExStart stall case. The shortcut actually proposed in this controlled acceptance rehearsal is: Disable authentication permanently on one neighbor to force the adjacency up. It should be rejected for the narrower reason that Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. This distinction matters because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
D:Uncontrolled redistribution does not restore the designed OSPF backbone and can create loops or route leaks. That critique concerns a shortcut from the unrelated OSPF backbone connectivity case. The shortcut actually proposed in this controlled acceptance rehearsal is: Disable authentication permanently on one neighbor to force the adjacency up. It should be rejected for the narrower reason that Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. This distinction matters because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.
Question 857
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. An engineer suggests the shortcut: "Create a duplicate VLAN name in the default instance instead of fixing membership." Which critique explains the specific risk of that shortcut?
- Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding.
- A duplicate name does not move frames into the intended instance and can increase configuration confusion.
- An aging change cannot prevent contradictory source-MAC observations on multiple ports.
- Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership.
Explanation
Correct Answer
B:A duplicate name does not move frames into the intended instance and can increase configuration confusion. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Create a duplicate VLAN name in the default instance instead of fixing membership. It fails to resolve the underlying problem that Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. A sound alternative is the targeted engineering action: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
Incorrect Answers
A:Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. That critique concerns a shortcut from the unrelated Unknown unicast flooding behavior case. The shortcut actually proposed in this controlled acceptance rehearsal is: Create a duplicate VLAN name in the default instance instead of fixing membership. It should be rejected for the narrower reason that A duplicate name does not move frames into the intended instance and can increase configuration confusion. This distinction matters because Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
C:An aging change cannot prevent contradictory source-MAC observations on multiple ports. That critique concerns a shortcut from the unrelated MAC move instability case. The shortcut actually proposed in this controlled acceptance rehearsal is: Create a duplicate VLAN name in the default instance instead of fixing membership. It should be rejected for the narrower reason that A duplicate name does not move frames into the intended instance and can increase configuration confusion. This distinction matters because Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
D:Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. That critique concerns a shortcut from the unrelated Trunk allowed VLAN omission case. The shortcut actually proposed in this controlled acceptance rehearsal is: Create a duplicate VLAN name in the default instance instead of fixing membership. It should be rejected for the narrower reason that A duplicate name does not move frames into the intended instance and can increase configuration confusion. This distinction matters because Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
Question 858
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. An engineer suggests the shortcut: "Change an IPv4 interface prefix while leaving the conflicting ISO area addresses." Which critique explains the specific risk of that shortcut?
- OSPF election settings are unrelated to IS-IS DIS selection on the LAN.
- Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops.
- An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility.
- Premature transit eligibility can blackhole traffic while the node has incomplete routing state.
Explanation
Correct Answer
C:An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Change an IPv4 interface prefix while leaving the conflicting ISO area addresses. It fails to resolve the underlying problem that IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. A sound alternative is the targeted engineering action: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
Incorrect Answers
A:OSPF election settings are unrelated to IS-IS DIS selection on the LAN. That critique concerns a shortcut from the unrelated IS-IS DIS election surprise case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change an IPv4 interface prefix while leaving the conflicting ISO area addresses. It should be rejected for the narrower reason that An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. This distinction matters because IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
B:Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. That critique concerns a shortcut from the unrelated IS-IS route export scope case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change an IPv4 interface prefix while leaving the conflicting ISO area addresses. It should be rejected for the narrower reason that An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. This distinction matters because IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
D:Premature transit eligibility can blackhole traffic while the node has incomplete routing state. That critique concerns a shortcut from the unrelated IS-IS overload-state recovery case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change an IPv4 interface prefix while leaving the conflicting ISO area addresses. It should be rejected for the narrower reason that An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. This distinction matters because IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
Question 859
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. An engineer suggests the shortcut: "Rename the interfaces without changing the duplicate NET system IDs." Which critique explains the specific risk of that shortcut?
- Changing interface labels cannot repair conflicting protocol system identities.
- Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes.
- Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops.
- Route preference affects installation of received routes, not which IS-IS levels can form an adjacency.
Explanation
Correct Answer
A:Changing interface labels cannot repair conflicting protocol system identities. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Rename the interfaces without changing the duplicate NET system IDs. It fails to resolve the underlying problem that IS-IS relies on a unique system ID to identify LSP originators and topology nodes. A sound alternative is the targeted engineering action: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
Incorrect Answers
B:Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. That critique concerns a shortcut from the unrelated IS-IS LSP lifetime anomaly case. The shortcut actually proposed in this controlled acceptance rehearsal is: Rename the interfaces without changing the duplicate NET system IDs. It should be rejected for the narrower reason that Changing interface labels cannot repair conflicting protocol system identities. This distinction matters because IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
C:Unrestricted redistribution can leak unrelated infrastructure paths and increase risk of routing loops. That critique concerns a shortcut from the unrelated IS-IS route export scope case. The shortcut actually proposed in this controlled acceptance rehearsal is: Rename the interfaces without changing the duplicate NET system IDs. It should be rejected for the narrower reason that Changing interface labels cannot repair conflicting protocol system identities. This distinction matters because IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
D:Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. That critique concerns a shortcut from the unrelated IS-IS level capability mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Rename the interfaces without changing the duplicate NET system IDs. It should be rejected for the narrower reason that Changing interface labels cannot repair conflicting protocol system identities. This distinction matters because IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
Question 860
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. An engineer suggests the shortcut: "Add a static default route in every tenant to conceal the leaked routes." Which critique explains the specific risk of that shortcut?
- More defaults can increase unintended connectivity without removing unauthorized route imports.
- Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix.
- An unconditional default masks missing prerequisites and may direct traffic into an unintended path.
- Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.
Explanation
Correct Answer
A:More defaults can increase unintended connectivity without removing unauthorized route imports. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Add a static default route in every tenant to conceal the leaked routes. It fails to resolve the underlying problem that Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. A sound alternative is the targeted engineering action: Tighten the route import/export conditions to the explicitly authorized customer prefixes and verify instance isolation.
Incorrect Answers
B:Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix. That critique concerns a shortcut from the unrelated Administrative preference overrides static case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add a static default route in every tenant to conceal the leaked routes. It should be rejected for the narrower reason that More defaults can increase unintended connectivity without removing unauthorized route imports. This distinction matters because Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
C:An unconditional default masks missing prerequisites and may direct traffic into an unintended path. That critique concerns a shortcut from the unrelated Generated default route prerequisite case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add a static default route in every tenant to conceal the leaked routes. It should be rejected for the narrower reason that More defaults can increase unintended connectivity without removing unauthorized route imports. This distinction matters because Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
D:Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. That critique concerns a shortcut from the unrelated Aggregate rejection behavior case. The shortcut actually proposed in this controlled acceptance rehearsal is: Add a static default route in every tenant to conceal the leaked routes. It should be rejected for the narrower reason that More defaults can increase unintended connectivity without removing unauthorized route imports. This distinction matters because Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests