Juniper JN0-664 Practice Test 3
Question 20
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. An engineer changes hello intervals on one router to accelerate convergence but leaves the matching peer unchanged and subsequently loses adjacency. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Conclude that working OSPFv2 routes automatically provide IPv6 reachability on Junos without any OSPFv3 or other IPv6 routing configuration.
- Disable OSPF on every provider interface merely because one neighbor is stuck in ExStart during database negotiation.
- Declare that a Type 2 external metric always equals the sum of backbone hop costs and must be changed whenever an IGP link cost changes.
- Enable MP-BGP VPN unicast for a tenant and promise its source multicast group will automatically traverse provider PEs with no MVPN or multicast setup.
Explanation
Correct Answer
B:That conflicts with the edge-to-cloud principle: OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ.
Incorrect Answers
A:This alternative proposes: Conclude that working OSPFv2 routes automatically provide IPv6 reachability on Junos without any OSPFv3 or other IPv6 routing configuration. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.
C:This alternative proposes: Declare that a Type 2 external metric always equals the sum of backbone hop costs and must be changed whenever an IGP link cost changes. It concerns a different Junos engineering issue OSPF external type E1 E2 route cost evaluation, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.
D:This alternative proposes: Enable MP-BGP VPN unicast for a tenant and promise its source multicast group will automatically traverse provider PEs with no MVPN or multicast setup. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue OSPF adjacency MTU and hello compatibility diagnosis.
Question 21
A Junos service-provider routing engineer investigates the following routing and service incident: A branch needs to redistribute a static access subnet into its limited OSPF area, but a fully stubby design prevents the expected external advertisement. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
- Apply summarization or import/export controls at the appropriate OSPF area boundary after proving which access prefixes should be reachable.
- Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.
- Check whether the deployed IS-IS metric style and link costs support the provider's intended routing and traffic-engineering behavior.
Explanation
Correct Answer
A:A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions. Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
Incorrect Answers
B:This alternative proposes: Apply summarization or import/export controls at the appropriate OSPF area boundary after proving which access prefixes should be reachable. It concerns a different Junos engineering issue OSPF interarea route summarization and route restrictions, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
C:This alternative proposes: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor. It concerns a different Junos engineering issue OSPF adjacency MTU and hello compatibility diagnosis, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
D:This alternative proposes: Check whether the deployed IS-IS metric style and link costs support the provider's intended routing and traffic-engineering behavior. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
Question 22
A provider routing design review considers this situation. A branch needs to redistribute a static access subnet into its limited OSPF area, but a fully stubby design prevents the expected external advertisement. A colleague proposes: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation. Which technical principle BEST supports that action? Select ONE best answer.
- VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design.
- A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions.
- OSPF backbone area 0 carries interarea reachability; a virtual link can join a disconnected backbone through an eligible transit area, but it is not a substitute for planned topology repair.
- ABRs can advertise summary information between areas while routing policy and area ranges alter which routes are visible; overly broad aggregation can blackhole traffic if specifics lack coverage.
Explanation
Correct Answer
B:The relevant Junos service-provider networking principle is: A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions. In the described provider-network case (A branch needs to redistribute a static access subnet into its limited OSPF area, but a fully stubby design prevents the expected external advertisement.), it supports the planned action: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
Incorrect Answers
A:This alternative proposes: VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
C:This alternative proposes: OSPF backbone area 0 carries interarea reachability; a virtual link can join a disconnected backbone through an eligible transit area, but it is not a substitute for planned topology repair. It concerns a different Junos engineering issue OSPF multi-area backbone connectivity and virtual-link limitations, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
D:This alternative proposes: ABRs can advertise summary information between areas while routing policy and area ranges alter which routes are visible; overly broad aggregation can blackhole traffic if specifics lack coverage. It concerns a different Junos engineering issue OSPF interarea route summarization and route restrictions, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
Question 23
A Juniper service-provider engineer needs decisive verification evidence for this situation. A branch needs to redistribute a static access subnet into its limited OSPF area, but a fully stubby design prevents the expected external advertisement. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Compare show ospf interface, election priorities, router IDs, two-way versus full neighbors, and current DR/BDR state after planned link transitions.
- Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries.
- Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
- Inspect show ospf3 neighbor, show ospf3 interface, IPv6 link-local addresses, area association, LSDB and inet6 routes independently of OSPFv2.
Explanation
Correct Answer
C:The direct discriminating observation is: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation. In the stated situation (A branch needs to redistribute a static access subnet into its limited OSPF area, but a fully stubby design prevents the expected external advertisement.), the intended acceptance outcome is: The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers.
Incorrect Answers
A:This alternative proposes: Compare show ospf interface, election priorities, router IDs, two-way versus full neighbors, and current DR/BDR state after planned link transitions. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
B:This alternative proposes: Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
D:This alternative proposes: Inspect show ospf3 neighbor, show ospf3 interface, IPv6 link-local addresses, area association, LSDB and inet6 routes independently of OSPFv2. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
Question 24
A service-provider acceptance team reviews the result of a provider-service change. A branch needs to redistribute a static access subnet into its limited OSPF area, but a fully stubby design prevents the expected external advertisement. The intended verification is: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation. Which outcome BEST demonstrates success? Select ONE best answer.
- The chosen exit aligns to the operator's end-to-end cost policy, and failover to another valid ASBR meets the documented path objective.
- The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers.
- Customer dual-homing provides the intended redundancy without duplicate broadcast delivery or loss of reachability when either PE fails.
- The appropriate designated and backup routers maintain required adjacencies and exchange reachability across the shared Ethernet without unnecessary resets.
Explanation
Correct Answer
B:The verified success outcome is: The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers. Confirm this by: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
Incorrect Answers
A:This alternative proposes: The chosen exit aligns to the operator's end-to-end cost policy, and failover to another valid ASBR meets the documented path objective. It concerns a different Junos engineering issue OSPF external type E1 E2 route cost evaluation, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
C:That option concerns EVPN Ethernet segment multihoming and designated forwarder. The related controlled intervention is: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
D:That option concerns OSPF designated router election on a multiaccess segment. The related controlled intervention is: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
Question 25
A Junos service-provider routing engineer investigates this service-provider network scenario. A branch needs to redistribute a static access subnet into its limited OSPF area, but a fully stubby design prevents the expected external advertisement. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Inspect show ospf3 neighbor, show ospf3 interface, IPv6 link-local addresses, area association, LSDB and inet6 routes independently of OSPFv2.
- Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
- Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress.
- Use Site of Origin controls and supported OSPF sham-link design where required to prevent multihomed customer loops or preserve intended intra-area OSPF path selection.
- Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
Explanation
Correct Answers
B:The case-specific routing and services action is: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation. The governing Junos routing/service principle is: A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions.
E:The direct discriminating observation is: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
Incorrect Answers
A:This alternative proposes: Inspect show ospf3 neighbor, show ospf3 interface, IPv6 link-local addresses, area association, LSDB and inet6 routes independently of OSPFv2. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling in the stated situation (A branch needs to redistribute a static access subnet into its limited OSPF area, but a fully stubby design prevents the expected external advertisement.). A better case-specific check is: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
C:This alternative proposes: Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
D:This alternative proposes: Use Site of Origin controls and supported OSPF sham-link design where required to prevent multihomed customer loops or preserve intended intra-area OSPF path selection. It concerns a different Junos engineering issue Site of Origin and OSPF sham-link loop control, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
Question 26
A Junos service-provider routing engineer investigates the following routing and service incident: A PE sees a Type 7 external LSA inside an NSSA but downstream backbone routers never learn the expected translated external prefix. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
- Apply summarization or import/export controls at the appropriate OSPF area boundary after proving which access prefixes should be reachable.
- Examine external route Type 1 versus Type 2 cost behavior and the forwarding cost toward the ASBR when determining why routers choose different exits.
- Validate multicast VPN control and data-plane dependencies before claiming a customer group's IP multicast stream should traverse an MPLS provider backbone.
Explanation
Correct Answer
A:The case-specific routing and services action is: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation. The governing Junos routing/service principle is: A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions. Verify the decision through: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
Incorrect Answers
B:This alternative proposes: Apply summarization or import/export controls at the appropriate OSPF area boundary after proving which access prefixes should be reachable. It concerns a different Junos engineering issue OSPF interarea route summarization and route restrictions, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
C:This alternative proposes: Examine external route Type 1 versus Type 2 cost behavior and the forwarding cost toward the ASBR when determining why routers choose different exits. It concerns a different Junos engineering issue OSPF external type E1 E2 route cost evaluation, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
D:This alternative proposes: Validate multicast VPN control and data-plane dependencies before claiming a customer group's IP multicast stream should traverse an MPLS provider backbone. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
Question 27
A provider routing design review considers this situation. A PE sees a Type 7 external LSA inside an NSSA but downstream backbone routers never learn the expected translated external prefix. A colleague proposes: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation. Which technical principle BEST supports that action? Select ONE best answer.
- A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions.
- OSPFv3 uses IPv6-related control-plane processing and link-local neighbor communication; it must be configured and verified according to the selected address family and release.
- IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths.
- OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ.
Explanation
Correct Answer
A:The relevant Junos service-provider networking principle is: A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions. In the described provider-network case (A PE sees a Type 7 external LSA inside an NSSA but downstream backbone routers never learn the expected translated external prefix.), it supports the planned action: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
Incorrect Answers
B:This alternative proposes: OSPFv3 uses IPv6-related control-plane processing and link-local neighbor communication; it must be configured and verified according to the selected address family and release. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
C:This alternative proposes: IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths. It concerns a different Junos engineering issue IS-IS link-state packet flooding and database consistency, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
D:This alternative proposes: OSPF neighbors can exchange hellos yet fail database description exchange when interface MTU or other required compatibility settings differ. It concerns a different Junos engineering issue OSPF adjacency MTU and hello compatibility diagnosis, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
Question 28
A Juniper service-provider engineer needs decisive verification evidence for this situation. A PE sees a Type 7 external LSA inside an NSSA but downstream backbone routers never learn the expected translated external prefix. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Check area IDs, ABR relationships, backbone LSA visibility, virtual-link state, and show ospf neighbor and database before adjusting policies.
- Inspect show ospf3 neighbor, show ospf3 interface, IPv6 link-local addresses, area association, LSDB and inet6 routes independently of OSPFv2.
- Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values.
- Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation.
Explanation
Correct Answer
D:The direct discriminating observation is: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation. In the stated situation (A PE sees a Type 7 external LSA inside an NSSA but downstream backbone routers never learn the expected translated external prefix.), the intended acceptance outcome is: The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers.
Incorrect Answers
A:This alternative proposes: Check area IDs, ABR relationships, backbone LSA visibility, virtual-link state, and show ospf neighbor and database before adjusting policies. It concerns a different Junos engineering issue OSPF multi-area backbone connectivity and virtual-link limitations, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
B:This alternative proposes: Inspect show ospf3 neighbor, show ospf3 interface, IPv6 link-local addresses, area association, LSDB and inet6 routes independently of OSPFv2. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
C:This alternative proposes: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values. It concerns a different Junos engineering issue CoS RED drop profiles and rewrite-marking validation, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
Question 29
A service-provider acceptance team reviews the result of a provider-service change. A PE sees a Type 7 external LSA inside an NSSA but downstream backbone routers never learn the expected translated external prefix. The intended verification is: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation. Which outcome BEST demonstrates success? Select ONE best answer.
- The session establishes over the intended transport and advertises only authorized routing information even across a link failure.
- Core route volume decreases while every authorized covered access subnet remains reachable and unintended prefixes stay filtered.
- The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers.
- The neighbor reaches Full, both routers synchronize the relevant link-state database, and no unrelated adjacencies are disrupted.
Explanation
Correct Answer
C:The verified success outcome is: The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers. Confirm this by: Compare area type on all routers, ASBR redistribution, Type 3 summaries, Type 5 or Type 7 database entries, and resulting route installation. The related controlled intervention is: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
Incorrect Answers
A:That option concerns BGP external multihop and loopback peer reachability. The related controlled intervention is: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
B:That option concerns OSPF interarea route summarization and route restrictions. The related controlled intervention is: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
D:That option concerns OSPF adjacency MTU and hello compatibility diagnosis. The related controlled intervention is: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
Question 30
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A PE sees a Type 7 external LSA inside an NSSA but downstream backbone routers never learn the expected translated external prefix. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Assume two separate nonbackbone areas exchange all interarea routes automatically even though neither connects to area 0.
- Configure one router in a shared area as NSSA while leaving its peer as a normal stub area and expect their adjacency and external imports to work.
- Apply maximum local preference to a path with an unresolved BGP next hop and insist that policy alone creates reachability to the next-hop address.
- Assume every pair of routers on a broadcast VLAN must display Full adjacency, and bounce the elected DR whenever another router is only Two-Way.
Explanation
Correct Answer
B:That conflicts with the edge-to-cloud principle: A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions.
Incorrect Answers
A:This alternative proposes: Assume two separate nonbackbone areas exchange all interarea routes automatically even though neither connects to area 0. It concerns a different Junos engineering issue OSPF multi-area backbone connectivity and virtual-link limitations, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
C:This alternative proposes: Apply maximum local preference to a path with an unresolved BGP next hop and insist that policy alone creates reachability to the next-hop address. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.
D:This alternative proposes: Assume every pair of routers on a broadcast VLAN must display Full adjacency, and bounce the elected DR whenever another router is only Two-Way. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue OSPF stub NSSA and external LSA handling.