Question 10
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: A remote OSPF area must inject a branch-only external prefix but the access router is not allowed to flood ordinary type 5 LSAs within the area. Which operational control would best prevent a recurrence of this exact failure mode?
- Verify summary coverage and black-hole risk whenever component routes change.
- Test both the NSSA LSDB and remote external route installation after a redistribution change.
- Test loss of upstream connectivity separately from loss of the local OSPF adjacency.
- Monitor LSDB freshness and SPF processing during periods of churn.
Explanation
Correct Answer
B:Test both the NSSA LSDB and remote external route installation after a redistribution change. The control limits repetition of the described root condition: An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. During audits, confirm: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Incorrect Answers
A:Verify summary coverage and black-hole risk whenever component routes change. This is a plausible preventive practice for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
C:Test loss of upstream connectivity separately from loss of the local OSPF adjacency. This is a plausible preventive practice for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
D:Monitor LSDB freshness and SPF processing during periods of churn. This is a plausible preventive practice for a different OSPF condition, specifically LSDB sequence-age mismatch. Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. In this scenario, however, the distinguishing issue is NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Question 11
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: An OSPF aggregation site is expected to use only a default toward the backbone, but its routing table still contains many specific interarea summaries. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect backbone reachability and actual upstream service path behind the advertised default.
- Identify which LSA type carries the prefixes and whether they originate at an ASBR rather than an ABR.
- Inspect the ABR stub options and the type 3 summary LSAs accepted in this area.
- Inspect LSA sequence numbers, age and LSDB synchronization before adjusting interface bandwidth.
Explanation
Correct Answer
C:Inspect the ABR stub options and the type 3 summary LSAs accepted in this area. This check examines the decisive condition for Totally stubby interarea suppression before any unrelated changes are made. The underlying mechanism is: A normal stub excludes type 5 externals but still allows type 3 interarea summaries, whereas a totally stubby design suppresses nondefault type 3s. The confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
Incorrect Answers
A:Inspect backbone reachability and actual upstream service path behind the advertised default. This is a plausible diagnostic check for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
B:Identify which LSA type carries the prefixes and whether they originate at an ASBR rather than an ABR. This is a plausible diagnostic check for a different OSPF condition, specifically ASBR external aggregation. AS-external advertisements have a different summarization control point from interarea type 3 summaries. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
D:Inspect LSA sequence numbers, age and LSDB synchronization before adjusting interface bandwidth. This is a plausible diagnostic check for a different OSPF condition, specifically LSDB sequence-age mismatch. Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
Question 12
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: An OSPF aggregation site is expected to use only a default toward the backbone, but its routing table still contains many specific interarea summaries. Which routing or service mechanism best explains the reported behavior?
- Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path.
- AS-external advertisements have a different summarization control point from interarea type 3 summaries.
- Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status.
- A normal stub excludes type 5 externals but still allows type 3 interarea summaries, whereas a totally stubby design suppresses nondefault type 3s.
Explanation
Correct Answer
D:A normal stub excludes type 5 externals but still allows type 3 interarea summaries, whereas a totally stubby design suppresses nondefault type 3s. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The area retains a default summary and no longer carries the unwanted individual interarea summaries. The targeted correction is: Use the appropriate totally-stubby no-summaries behavior consistently at the ABR while retaining a valid default.
Incorrect Answers
A:Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. This is a plausible protocol explanation for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
B:AS-external advertisements have a different summarization control point from interarea type 3 summaries. This is a plausible protocol explanation for a different OSPF condition, specifically ASBR external aggregation. AS-external advertisements have a different summarization control point from interarea type 3 summaries. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
C:Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. This is a plausible protocol explanation for a different OSPF condition, specifically LSDB sequence-age mismatch. Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
Question 13
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: An OSPF aggregation site is expected to use only a default toward the backbone, but its routing table still contains many specific interarea summaries. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The area retains a default summary and no longer carries the unwanted individual interarea summaries.
- End-to-end checks through the ABR succeed while its advertised default is valid and failover behavior is documented.
- External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
- Both routers hold the current LSA instance and SPF results match the intended next-hop behavior.
Explanation
Correct Answer
A:The area retains a default summary and no longer carries the unwanted individual interarea summaries. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A normal stub excludes type 5 externals but still allows type 3 interarea summaries, whereas a totally stubby design suppresses nondefault type 3s.
Incorrect Answers
B:End-to-end checks through the ABR succeed while its advertised default is valid and failover behavior is documented. This is a plausible observed evidence for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
C:External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect. This is a plausible observed evidence for a different OSPF condition, specifically ASBR external aggregation. AS-external advertisements have a different summarization control point from interarea type 3 summaries. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
D:Both routers hold the current LSA instance and SPF results match the intended next-hop behavior. This is a plausible observed evidence for a different OSPF condition, specifically LSDB sequence-age mismatch. Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
Question 14
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: An OSPF aggregation site is expected to use only a default toward the backbone, but its routing table still contains many specific interarea summaries. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Tie default-origination behavior to the intended exit architecture and upstream monitoring where feasible.
- Use the appropriate totally-stubby no-summaries behavior consistently at the ABR while retaining a valid default.
- Apply ASBR-appropriate external aggregation or controlled redistribution for the external prefix set.
- Enable supported multipath handling and verify consistent next-hop resolution before load-sharing.
Explanation
Correct Answer
B:Use the appropriate totally-stubby no-summaries behavior consistently at the ABR while retaining a valid default. The change addresses the root behavior described here: A normal stub excludes type 5 externals but still allows type 3 interarea summaries, whereas a totally stubby design suppresses nondefault type 3s. Verify success with: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
Incorrect Answers
A:Tie default-origination behavior to the intended exit architecture and upstream monitoring where feasible. This is a plausible configuration or operational fix for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
C:Apply ASBR-appropriate external aggregation or controlled redistribution for the external prefix set. This is a plausible configuration or operational fix for a different OSPF condition, specifically ASBR external aggregation. AS-external advertisements have a different summarization control point from interarea type 3 summaries. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
D:Enable supported multipath handling and verify consistent next-hop resolution before load-sharing. This is a plausible configuration or operational fix for a different OSPF condition, specifically OSPF equal-cost multipath. Equal-cost path computation and installing multiple usable forwarding next hops are distinct from merely having two neighbors. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
Question 15
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: An OSPF aggregation site is expected to use only a default toward the backbone, but its routing table still contains many specific interarea summaries. Which operational control would best prevent a recurrence of this exact failure mode?
- Test loss of upstream connectivity separately from loss of the local OSPF adjacency.
- Maintain an external-prefix inventory and validate reachable components before suppressing specifics.
- Check ABR summarization settings against the site's failover and reachability requirements.
- Test failure behavior for each ECMP member rather than assuming hashing guarantees perfect per-flow balance.
Explanation
Correct Answer
C:Check ABR summarization settings against the site's failover and reachability requirements. The control limits repetition of the described root condition: A normal stub excludes type 5 externals but still allows type 3 interarea summaries, whereas a totally stubby design suppresses nondefault type 3s. During audits, confirm: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
Incorrect Answers
A:Test loss of upstream connectivity separately from loss of the local OSPF adjacency. This is a plausible preventive practice for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
B:Maintain an external-prefix inventory and validate reachable components before suppressing specifics. This is a plausible preventive practice for a different OSPF condition, specifically ASBR external aggregation. AS-external advertisements have a different summarization control point from interarea type 3 summaries. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
D:Test failure behavior for each ECMP member rather than assuming hashing guarantees perfect per-flow balance. This is a plausible preventive practice for a different OSPF condition, specifically OSPF equal-cost multipath. Equal-cost path computation and installing multiple usable forwarding next hops are distinct from merely having two neighbors. In this scenario, however, the distinguishing issue is Totally stubby interarea suppression and the confirming observation is: The area retains a default summary and no longer carries the unwanted individual interarea summaries.
Question 16
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: An enterprise OSPF area 12 learns area-local routes but cannot reach prefixes that live in area 24 when the backbone transit was disconnected. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Check the transit area's type and the endpoints' shared nonbackbone-area participation.
- Inspect the ABR's area range configuration and the origin of interarea summary LSAs.
- Compare the area's stub configuration and its LSA types with the missing external destinations.
- Trace ABR connectivity to area 0 and check whether the backbone is logically continuous.
Explanation
Correct Answer
D:Trace ABR connectivity to area 0 and check whether the backbone is logically continuous. This check examines the decisive condition for Backbone continuity through ABR before any unrelated changes are made. The underlying mechanism is: OSPF interarea routing normally depends on a continuous area 0 backbone reached through ABRs. The confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
Incorrect Answers
A:Check the transit area's type and the endpoints' shared nonbackbone-area participation. This is a plausible diagnostic check for a different OSPF condition, specifically Virtual-link transit eligibility. A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
B:Inspect the ABR's area range configuration and the origin of interarea summary LSAs. This is a plausible diagnostic check for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
C:Compare the area's stub configuration and its LSA types with the missing external destinations. This is a plausible diagnostic check for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
Question 17
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: An enterprise OSPF area 12 learns area-local routes but cannot reach prefixes that live in area 24 when the backbone transit was disconnected. Which routing or service mechanism best explains the reported behavior?
- OSPF interarea routing normally depends on a continuous area 0 backbone reached through ABRs.
- A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit.
- Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary.
- A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes.
Explanation
Correct Answer
A:OSPF interarea routing normally depends on a continuous area 0 backbone reached through ABRs. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair. The targeted correction is: Restore area 0 connectivity or use a justified temporary virtual link through a suitable transit area.
Incorrect Answers
B:A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. This is a plausible protocol explanation for a different OSPF condition, specifically Virtual-link transit eligibility. A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
C:Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. This is a plausible protocol explanation for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
D:A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. This is a plausible protocol explanation for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
Question 18
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: An enterprise OSPF area 12 learns area-local routes but cannot reach prefixes that live in area 24 when the backbone transit was disconnected. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The virtual-link adjacency establishes through an eligible common transit area and backbone routes synchronize.
- ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
- Remote areas see the aggregate summary and no unwanted individual component advertisements under the defined policy.
- The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
Explanation
Correct Answer
B:ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: OSPF interarea routing normally depends on a continuous area 0 backbone reached through ABRs.
Incorrect Answers
A:The virtual-link adjacency establishes through an eligible common transit area and backbone routes synchronize. This is a plausible observed evidence for a different OSPF condition, specifically Virtual-link transit eligibility. A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
C:Remote areas see the aggregate summary and no unwanted individual component advertisements under the defined policy. This is a plausible observed evidence for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
D:The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed. This is a plausible observed evidence for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
Question 19
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: An enterprise OSPF area 12 learns area-local routes but cannot reach prefixes that live in area 24 when the backbone transit was disconnected. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Configure the ABR area range with a prefix that genuinely covers the intended internal networks.
- Use a normal area if individual external LSAs are required, or explicitly design default-route reachability through the ABR.
- Restore area 0 connectivity or use a justified temporary virtual link through a suitable transit area.
- Normalize planned costs or explicitly accept asymmetry based on tested service requirements.
Explanation
Correct Answer
C:Restore area 0 connectivity or use a justified temporary virtual link through a suitable transit area. The change addresses the root behavior described here: OSPF interarea routing normally depends on a continuous area 0 backbone reached through ABRs. Verify success with: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
Incorrect Answers
A:Configure the ABR area range with a prefix that genuinely covers the intended internal networks. This is a plausible configuration or operational fix for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
B:Use a normal area if individual external LSAs are required, or explicitly design default-route reachability through the ABR. This is a plausible configuration or operational fix for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
D:Normalize planned costs or explicitly accept asymmetry based on tested service requirements. This is a plausible configuration or operational fix for a different OSPF condition, specifically SPF metric asymmetry. OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
Question 20
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: An enterprise OSPF area 12 learns area-local routes but cannot reach prefixes that live in area 24 when the backbone transit was disconnected. Which operational control would best prevent a recurrence of this exact failure mode?
- Document virtual links as a temporary remediation with a planned backbone simplification.
- Verify summary coverage and black-hole risk whenever component routes change.
- Record permitted LSA types and verify the default route before converting an area to stub.
- Require a backbone-continuity diagram and test reachability between nonbackbone areas during changes.
Explanation
Correct Answer
D:Require a backbone-continuity diagram and test reachability between nonbackbone areas during changes. The control limits repetition of the described root condition: OSPF interarea routing normally depends on a continuous area 0 backbone reached through ABRs. During audits, confirm: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
Incorrect Answers
A:Document virtual links as a temporary remediation with a planned backbone simplification. This is a plausible preventive practice for a different OSPF condition, specifically Virtual-link transit eligibility. A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
B:Verify summary coverage and black-hole risk whenever component routes change. This is a plausible preventive practice for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
C:Record permitted LSA types and verify the default route before converting an area to stub. This is a plausible preventive practice for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is Backbone continuity through ABR and the confirming observation is: ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests