Question 190
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A Level 1 router cannot use a required specific service prefix from another area because the site accepts only an attached default route. Which operational control would best prevent a recurrence of this exact failure mode?
- Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only.
- Review leak policies for loops and excessive L1 state whenever remote services change.
- Include removal of each L1/L2 border router in resilience exercises.
- Document protocol-level and area boundaries for each advertised prefix.
Explanation
Correct Answer
B:Review leak policies for loops and excessive L1 state whenever remote services change. The control limits repetition of the described root condition: Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. During audits, confirm: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.
Incorrect Answers
A:Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only. This is a plausible preventive practice for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.
C:Include removal of each L1/L2 border router in resilience exercises. This is a plausible preventive practice for a different IS-IS condition, specifically Level 2 backbone continuity. Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.
D:Document protocol-level and area boundaries for each advertised prefix. This is a plausible preventive practice for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.
Question 191
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: A connected service subnet is present in inet.0 but is absent from Level 2 IS-IS advertisements after a policy refactor. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect enabled IS-IS address-family reachability and the IPv6 TLVs in LSPs.
- Compare IS-IS LAN priorities and the elected DIS at each supported level.
- Review export policy terms and the active route's protocol and prefix properties.
- Compare directed IS-IS link metrics in both routers' advertisements and recompute SPF independently.
Explanation
Correct Answer
C:Review export policy terms and the active route's protocol and prefix properties. This check examines the decisive condition for IS-IS external route policy before any unrelated changes are made. The underlying mechanism is: Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence. The confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
Incorrect Answers
A:Inspect enabled IS-IS address-family reachability and the IPv6 TLVs in LSPs. This is a plausible diagnostic check for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
B:Compare IS-IS LAN priorities and the elected DIS at each supported level. This is a plausible diagnostic check for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
D:Compare directed IS-IS link metrics in both routers' advertisements and recompute SPF independently. This is a plausible diagnostic check for a different IS-IS condition, specifically IS-IS metric directionality. Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
Question 192
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: A connected service subnet is present in inet.0 but is absent from Level 2 IS-IS advertisements after a policy refactor. Which routing or service mechanism best explains the reported behavior?
- A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised.
- IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior.
- Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes.
- Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence.
Explanation
Correct Answer
D:Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs. The targeted correction is: Restore a narrow approved export term for the service prefix and source protocol.
Incorrect Answers
A:A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. This is a plausible protocol explanation for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
B:IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. This is a plausible protocol explanation for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
C:Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. This is a plausible protocol explanation for a different IS-IS condition, specifically IS-IS metric directionality. Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
Question 193
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: A connected service subnet is present in inet.0 but is absent from Level 2 IS-IS advertisements after a policy refactor. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
- The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
- The expected DIS originates the pseudonode LSP and the LAN neighbor set is stable.
- After physical stability and appropriate SPF pacing, route convergence occurs without repeated CPU spikes.
Explanation
Correct Answer
A:The intended source route passes the policy and appears as reachability in neighboring L2 LSPs. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence.
Incorrect Answers
B:The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured. This is a plausible observed evidence for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
C:The expected DIS originates the pseudonode LSP and the LAN neighbor set is stable. This is a plausible observed evidence for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
D:After physical stability and appropriate SPF pacing, route convergence occurs without repeated CPU spikes. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS SPF recalculation load. Frequent link-state database changes trigger recalculation work across routers that share the level's topology. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
Question 194
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A connected service subnet is present in inet.0 but is absent from Level 2 IS-IS advertisements after a policy refactor. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Enable compatible IPv6 IS-IS reachability for the intended level and check end-to-end next hops.
- Restore a narrow approved export term for the service prefix and source protocol.
- Set the intended LAN DIS priority consistently for the planned level and verify election state.
- Keep IS-IS neighbors on real transport interfaces and advertise lo0 only as a stable endpoint.
Explanation
Correct Answer
B:Restore a narrow approved export term for the service prefix and source protocol. The change addresses the root behavior described here: Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence. Verify success with: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
Incorrect Answers
A:Enable compatible IPv6 IS-IS reachability for the intended level and check end-to-end next hops. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
C:Set the intended LAN DIS priority consistently for the planned level and verify election state. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
D:Keep IS-IS neighbors on real transport interfaces and advertise lo0 only as a stable endpoint. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS loopback passive behavior. Junos normally treats IS-IS lo0 as passive, advertising reachability without forming HELLO-based neighbors on that interface. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
Question 195
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A connected service subnet is present in inet.0 but is absent from Level 2 IS-IS advertisements after a policy refactor. Which operational control would best prevent a recurrence of this exact failure mode?
- Track IPv4 and IPv6 reachability independently during routing expansions.
- Audit pseudonode LSP origin after LAN membership changes.
- Test policy term ordering and accidental external redistribution during each update.
- Enforce system-ID uniqueness checks in provisioning inventories.
Explanation
Correct Answer
C:Test policy term ordering and accidental external redistribution during each update. The control limits repetition of the described root condition: Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence. During audits, confirm: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
Incorrect Answers
A:Track IPv4 and IPv6 reachability independently during routing expansions. This is a plausible preventive practice for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
B:Audit pseudonode LSP origin after LAN membership changes. This is a plausible preventive practice for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
D:Enforce system-ID uniqueness checks in provisioning inventories. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS NET system ID collision. The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. In this scenario, however, the distinguishing issue is IS-IS external route policy and the confirming observation is: The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
Question 196
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A Junos IS-IS export policy accepts a wide aggregate ahead of a specific rejection term, unexpectedly leaking a sensitive more-specific prefix. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Check wide-metric enablement and effective LSP metric encoding throughout the relevant area.
- Inspect the leaking policy for selected Level 2 reachability into the local Level 1 domain.
- Inspect effective level settings at the global, interface and adjacency levels.
- Trace the route against ordered policy terms and identify the first terminating match.
Explanation
Correct Answer
D:Trace the route against ordered policy terms and identify the first terminating match. This check examines the decisive condition for Route-policy term ordering before any unrelated changes are made. The underlying mechanism is: Policy evaluation order can make a broad accept term preempt a later specific deny match. The confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
Incorrect Answers
A:Check wide-metric enablement and effective LSP metric encoding throughout the relevant area. This is a plausible diagnostic check for a different IS-IS condition, specifically IS-IS wide metric requirement. Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
B:Inspect the leaking policy for selected Level 2 reachability into the local Level 1 domain. This is a plausible diagnostic check for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
C:Inspect effective level settings at the global, interface and adjacency levels. This is a plausible diagnostic check for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
Question 197
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A Junos IS-IS export policy accepts a wide aggregate ahead of a specific rejection term, unexpectedly leaking a sensitive more-specific prefix. Which routing or service mechanism best explains the reported behavior?
- Policy evaluation order can make a broad accept term preempt a later specific deny match.
- Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain.
- Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking.
- Junos can enable both IS-IS levels by default unless one level is explicitly disabled.
Explanation
Correct Answer
A:Policy evaluation order can make a broad accept term preempt a later specific deny match. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected. The targeted correction is: Put restrictive or more-specific route handling before broad accept behavior.
Incorrect Answers
B:Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. This is a plausible protocol explanation for a different IS-IS condition, specifically IS-IS wide metric requirement. Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
C:Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. This is a plausible protocol explanation for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
D:Junos can enable both IS-IS levels by default unless one level is explicitly disabled. This is a plausible protocol explanation for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
Question 198
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A Junos IS-IS export policy accepts a wide aggregate ahead of a specific rejection term, unexpectedly leaking a sensitive more-specific prefix. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The advertised link metric matches the design and the calculated path preference changes accordingly.
- The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
- The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.
- Operational neighbor state shows only the intended levels after level settings are corrected.
Explanation
Correct Answer
B:The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Policy evaluation order can make a broad accept term preempt a later specific deny match.
Incorrect Answers
A:The advertised link metric matches the design and the calculated path preference changes accordingly. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS wide metric requirement. Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
C:The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized. This is a plausible observed evidence for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
D:Operational neighbor state shows only the intended levels after level settings are corrected. This is a plausible observed evidence for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
Question 199
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A Junos IS-IS export policy accepts a wide aggregate ahead of a specific rejection term, unexpectedly leaking a sensitive more-specific prefix. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Apply compatible wide-metric operation and the validated cost on all affected routers.
- Enable narrow L2-to-L1 route leaking for the required service prefix using appropriate policy.
- Put restrictive or more-specific route handling before broad accept behavior.
- Disable the unneeded IS-IS level on the device or interface according to its network role.
Explanation
Correct Answer
C:Put restrictive or more-specific route handling before broad accept behavior. The change addresses the root behavior described here: Policy evaluation order can make a broad accept term preempt a later specific deny match. Verify success with: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
Incorrect Answers
A:Apply compatible wide-metric operation and the validated cost on all affected routers. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS wide metric requirement. Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
B:Enable narrow L2-to-L1 route leaking for the required service prefix using appropriate policy. This is a plausible configuration or operational fix for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
D:Disable the unneeded IS-IS level on the device or interface according to its network role. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
Question 200
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A Junos IS-IS export policy accepts a wide aggregate ahead of a specific rejection term, unexpectedly leaking a sensitive more-specific prefix. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit metric encoding and path calculation before importing large traffic-engineering costs.
- Review leak policies for loops and excessive L1 state whenever remote services change.
- Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only.
- Run policy simulation against positive and negative test prefixes on every change.
Explanation
Correct Answer
D:Run policy simulation against positive and negative test prefixes on every change. The control limits repetition of the described root condition: Policy evaluation order can make a broad accept term preempt a later specific deny match. During audits, confirm: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
Incorrect Answers
A:Audit metric encoding and path calculation before importing large traffic-engineering costs. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS wide metric requirement. Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
B:Review leak policies for loops and excessive L1 state whenever remote services change. This is a plausible preventive practice for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
C:Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only. This is a plausible preventive practice for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests