Question 180At fictional Orchard Link 045, a regional service-provider network, during a preproduction design validation, operations observes: A static service prefix is missing from OSPF because the export policy was attached but does not match it. Which failure consequence follows most closely from ignoring this issue? A correct broadcast network is disrupted by unnecessary configuration changes. Duplicate identity produces unstable topology and confusing route calculations. Remote sites lose the service route or excessive routes leak into the IGP. The partially initialized router drops transit packets during planned recovery. ExplanationCorrect Answer C:Remote sites lose the service route or excessive routes leak into the IGP. Redistributing non-OSPF reachability into OSPF requires suitable export policy. Fix the OSPF export policy's precise match and validate external route origination. Incorrect Answers A:A correct broadcast network is disrupted by unnecessary configuration changes. The choice would be appropriate if on a broadcast segment, one non-designated router shows a peer at 2-Way and an operator incorrectly treats it as a failure. Here, a static service prefix is missing from OSPF because the export policy was attached but does not match it. B:Duplicate identity produces unstable topology and confusing route calculations. That option concerns two routers in the same routing domain advertise the same OSPF router ID after cloning a lab template. The problem here is different: A static service prefix is missing from OSPF because the export policy was attached but does not match it. D:The partially initialized router drops transit packets during planned recovery. This could matter when a newly rebooted core router attracts transit traffic while its forwarding state is still being restored. In this case, a static service prefix is missing from OSPF because the export policy was attached but does not match it.
Question 181In a separate fictional JNCIS-SP lab review for Oakshore Peering 046, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A static service prefix is missing from OSPF because the export policy was attached but does not match it. What intervention most directly restores the intended routing or switching behavior? Review planned OSPF costs in both directions and correct the traffic-engineering values. Apply compatible supported authentication settings on the intended OSPF interfaces and verify adjacency recovery. Fix the OSPF export policy's precise match and validate external route origination. Verify renewed label forwarding entries after the IGP path change and correct stale state. ExplanationCorrect Answer C:Fix the OSPF export policy's precise match and validate external route origination. The approved prefix is present as an external OSPF route and unauthorized prefixes remain absent. Redistributing non-OSPF reachability into OSPF requires suitable export policy. Incorrect Answers A:Review planned OSPF costs in both directions and correct the traffic-engineering values. This addresses a situation in which provider traffic takes a long backup path because OSPF interface costs were changed inconsistently; however, a static service prefix is missing from OSPF because the export policy was attached but does not match it. B:Apply compatible supported authentication settings on the intended OSPF interfaces and verify adjacency recovery. The choice would be appropriate if a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree. Here, a static service prefix is missing from OSPF because the export policy was attached but does not match it. D:Verify renewed label forwarding entries after the IGP path change and correct stale state. It addresses a different problem: After an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. Here, a static service prefix is missing from OSPF because the export policy was attached but does not match it.
Question 182In a separate fictional JNCIS-SP lab review for Oakshore Peering 046, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A static service prefix is missing from OSPF because the export policy was attached but does not match it. Which networking principle explains why the proposed correction is appropriate? A passive interface can advertise connected reachability without sending OSPF hellos to customers. OSPF SPF computes least-cost paths using the advertised topology metrics. Redistributing non-OSPF reachability into OSPF requires suitable export policy. Route policy controls which eligible nonnative prefixes are intentionally originated into IS-IS. ExplanationCorrect Answer C:Redistributing non-OSPF reachability into OSPF requires suitable export policy. The approved prefix is present as an external OSPF route and unauthorized prefixes remain absent. Fix the OSPF export policy's precise match and validate external route origination. Incorrect Answers A:A passive interface can advertise connected reachability without sending OSPF hellos to customers. That relates to circumstances in which a provider PE inadvertently attempts to form an OSPF adjacency on a customer LAN that should advertise reachability only. Here the problem is that a static service prefix is missing from OSPF because the export policy was attached but does not match it. B:OSPF SPF computes least-cost paths using the advertised topology metrics. This addresses a situation in which provider traffic takes a long backup path because OSPF interface costs were changed inconsistently; however, a static service prefix is missing from OSPF because the export policy was attached but does not match it. D:Route policy controls which eligible nonnative prefixes are intentionally originated into IS-IS. That option concerns a customer service route never reaches another IS-IS area because the required export policy omits it. The problem here is different: A static service prefix is missing from OSPF because the export policy was attached but does not match it.
Question 183In a separate fictional JNCIS-SP lab review for Oakshore Peering 046, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A static service prefix is missing from OSPF because the export policy was attached but does not match it. Which validation result would confirm the design is now functioning? The expected LSA is present with appropriate advertising router and area context. The circuit forms the expected point-to-point adjacency without an unwanted DR election. The active label operation now uses the recovered egress next hop. The approved prefix is present as an external OSPF route and unauthorized prefixes remain absent. ExplanationCorrect Answer D:The approved prefix is present as an external OSPF route and unauthorized prefixes remain absent. Fix the OSPF export policy's precise match and validate external route origination. Redistributing non-OSPF reachability into OSPF requires suitable export policy. Incorrect Answers A:The expected LSA is present with appropriate advertising router and area context. It is useful for situations where operators expect a customer prefix from another area but only inspect local interface counters and never examine link-state advertisements; the reported fault, though, is that a static service prefix is missing from OSPF because the export policy was attached but does not match it. B:The circuit forms the expected point-to-point adjacency without an unwanted DR election. That relates to circumstances in which OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. Here the problem is that a static service prefix is missing from OSPF because the export policy was attached but does not match it. C:The active label operation now uses the recovered egress next hop. This addresses a situation in which after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device; however, a static service prefix is missing from OSPF because the export policy was attached but does not match it.
Question 184In a separate fictional JNCIS-SP lab review for Oakshore Peering 046, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A static service prefix is missing from OSPF because the export policy was attached but does not match it. What likely service impact does this condition create? Remote sites lose the service route or excessive routes leak into the IGP. The adjacency repeatedly fails and transit traffic loses a redundant path. Misdiagnosis delays restoration because absent control-plane information is overlooked. IPv6 routing does not converge across the link. ExplanationCorrect Answer A:Remote sites lose the service route or excessive routes leak into the IGP. Fix the OSPF export policy's precise match and validate external route origination. Redistributing non-OSPF reachability into OSPF requires suitable export policy. Incorrect Answers B:The adjacency repeatedly fails and transit traffic loses a redundant path. It is useful for situations where OSPF neighbors remain down after one endpoint inherits a different hello and dead timer template; the reported fault, though, is that a static service prefix is missing from OSPF because the export policy was attached but does not match it. C:Misdiagnosis delays restoration because absent control-plane information is overlooked. That relates to circumstances in which operators expect a customer prefix from another area but only inspect local interface counters and never examine link-state advertisements. Here the problem is that a static service prefix is missing from OSPF because the export policy was attached but does not match it. D:IPv6 routing does not converge across the link. This addresses a situation in which an IPv6 prefix is missing across a point-to-point link because OSPFv2 was configured but OSPFv3 was omitted; however, a static service prefix is missing from OSPF because the export policy was attached but does not match it.
Question 185At fictional Brookridge Metro 047, a regional service-provider network, during a core-routing acceptance test, operations observes: OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. Which configuration or operational correction most directly addresses this failure? Use passive OSPF operation on the customer-facing interface while retaining intended prefix advertisement. Set compatible network type and review adjacency expectations on both ends. Review planned OSPF costs in both directions and correct the traffic-engineering values. Align the intended MSTP region parameters and VLAN-to-instance mapping on both switches. ExplanationCorrect Answer B:Set compatible network type and review adjacency expectations on both ends. OSPF interface network type influences neighbor discovery and DR behavior. The circuit forms the expected point-to-point adjacency without an unwanted DR election. Incorrect Answers A:Use passive OSPF operation on the customer-facing interface while retaining intended prefix advertisement. This could help if a provider PE inadvertently attempts to form an OSPF adjacency on a customer LAN that should advertise reachability only, but not when OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. C:Review planned OSPF costs in both directions and correct the traffic-engineering values. It is useful for situations where provider traffic takes a long backup path because OSPF interface costs were changed inconsistently; the reported fault, though, is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. D:Align the intended MSTP region parameters and VLAN-to-instance mapping on both switches. That relates to circumstances in which two interconnected switches place the same VLAN in different MSTP instances, leading to inconsistent blocking behavior. Here the problem is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology.
Question 186At fictional Brookridge Metro 047, a regional service-provider network, during a core-routing acceptance test, operations observes: OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. Which Junos forwarding or control-plane rule applies to this case? OSPF route visibility depends on appropriate LSA origination and flooding through the area topology. OSPF SPF computes least-cost paths using the advertised topology metrics. OSPF interface network type influences neighbor discovery and DR behavior. The IS-IS overload indication can discourage transit use during control-plane recovery. ExplanationCorrect Answer C:OSPF interface network type influences neighbor discovery and DR behavior. Set compatible network type and review adjacency expectations on both ends. The circuit forms the expected point-to-point adjacency without an unwanted DR election. Incorrect Answers A:OSPF route visibility depends on appropriate LSA origination and flooding through the area topology. It is relevant if operators expect a customer prefix from another area but only inspect local interface counters and never examine link-state advertisements, but the reported issue is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. B:OSPF SPF computes least-cost paths using the advertised topology metrics. This could help if provider traffic takes a long backup path because OSPF interface costs were changed inconsistently, but not when OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. D:The IS-IS overload indication can discourage transit use during control-plane recovery. It is useful for situations where a newly rebooted core router attracts transit traffic while its forwarding state is still being restored; the reported fault, though, is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology.
Question 187At fictional Brookridge Metro 047, a regional service-provider network, during a core-routing acceptance test, operations observes: OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. What operational evidence best establishes successful remediation? Route detail and controlled traffic testing select the documented primary path. The circuit forms the expected point-to-point adjacency without an unwanted DR election. Neighbor state stabilizes and hello and dead intervals match on both endpoints. The planned L1 adjacency forms and the corresponding area information is consistent. ExplanationCorrect Answer B:The circuit forms the expected point-to-point adjacency without an unwanted DR election. OSPF interface network type influences neighbor discovery and DR behavior. Set compatible network type and review adjacency expectations on both ends. Incorrect Answers A:Route detail and controlled traffic testing select the documented primary path. This is applicable when provider traffic takes a long backup path because OSPF interface costs were changed inconsistently; the present condition is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. C:Neighbor state stabilizes and hello and dead intervals match on both endpoints. This could help if OSPF neighbors remain down after one endpoint inherits a different hello and dead timer template, but not when OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. D:The planned L1 adjacency forms and the corresponding area information is consistent. This relates to a case where a Level 1 IS-IS adjacency fails between routers with different area addresses even though the physical link is up; the current situation is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology.
Question 188At fictional Brookridge Metro 047, a regional service-provider network, during a core-routing acceptance test, operations observes: OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. Which operational harm would persist without the intended correction? Routing connectivity fails or a poorly scoped workaround weakens control-plane trust. Duplicate identity produces unstable topology and confusing route calculations. MPLS traffic remains broken despite restored IGP neighbors. A transit route remains unavailable because neighbor behavior is inconsistent. ExplanationCorrect Answer D:A transit route remains unavailable because neighbor behavior is inconsistent. OSPF interface network type influences neighbor discovery and DR behavior. Set compatible network type and review adjacency expectations on both ends. Incorrect Answers A:Routing connectivity fails or a poorly scoped workaround weakens control-plane trust. That could help when a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree; here, OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. B:Duplicate identity produces unstable topology and confusing route calculations. This is applicable when two routers in the same routing domain advertise the same OSPF router ID after cloning a lab template; the present condition is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. C:MPLS traffic remains broken despite restored IGP neighbors. It is relevant if after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device, but the reported issue is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology.
Question 189In a separate fictional JNCIS-SP lab review for Stonefield Telecom 048, a carrier-edge and core routing team, following a monitored network change window, engineers find: OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. What should the Junos specialist change first to resolve this specific fault? Check relevant LSA types and area scope before changing forwarding routes. Set compatible network type and review adjacency expectations on both ends. Align the intended OSPF area on both endpoints and inspect neighbor state. Restore the documented protection features and run controlled BPDU and failover tests. ExplanationCorrect Answer B:Set compatible network type and review adjacency expectations on both ends. The circuit forms the expected point-to-point adjacency without an unwanted DR election. OSPF interface network type influences neighbor discovery and DR behavior. Incorrect Answers A:Check relevant LSA types and area scope before changing forwarding routes. This could matter when operators expect a customer prefix from another area but only inspect local interface counters and never examine link-state advertisements. In this case, OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. C:Align the intended OSPF area on both endpoints and inspect neighbor state. This is applicable when two provider routers on a point-to-point circuit cannot form an OSPF adjacency because their interfaces use different area IDs; the present condition is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. D:Restore the documented protection features and run controlled BPDU and failover tests. It is relevant if a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards, but the reported issue is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology.
Question 190In a separate fictional JNCIS-SP lab review for Stonefield Telecom 048, a carrier-edge and core routing team, following a monitored network change window, engineers find: OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. What technical principle underlies the right remedy? The OSPF router ID uniquely identifies a router in link-state advertisements. OSPF interface network type influences neighbor discovery and DR behavior. OSPF route visibility depends on appropriate LSA origination and flooding through the area topology. Link-local IPv6 addresses are scoped to a link and require an appropriate interface context. ExplanationCorrect Answer B:OSPF interface network type influences neighbor discovery and DR behavior. The circuit forms the expected point-to-point adjacency without an unwanted DR election. Set compatible network type and review adjacency expectations on both ends. Incorrect Answers A:The OSPF router ID uniquely identifies a router in link-state advertisements. It addresses a different problem: Two routers in the same routing domain advertise the same OSPF router ID after cloning a lab template. Here, OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. C:OSPF route visibility depends on appropriate LSA origination and flooding through the area topology. That could help when operators expect a customer prefix from another area but only inspect local interface counters and never examine link-state advertisements; here, OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. D:Link-local IPv6 addresses are scoped to a link and require an appropriate interface context. This is applicable when an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design; the present condition is that OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology.