Question 10At fictional Crestland Networks 003, a regional service-provider network, during a two-site transit migration, operations observes: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. Which Junos forwarding or control-plane rule applies to this case? Filter-based forwarding selects a routing lookup context based on packet classification. Route lookup and default selection occur within the configured routing-instance context. RSVP-TE can establish signaled LSPs subject to configured path constraints. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. ExplanationCorrect Answer D:For otherwise comparable routes, Junos route preference influences which eligible route becomes active. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. The primary path stays selected normally and the backup is activated only when the primary is unavailable. Incorrect Answers A:Filter-based forwarding selects a routing lookup context based on packet classification. It addresses a different problem: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Here, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. B:Route lookup and default selection occur within the configured routing-instance context. This could matter when a route lookup for a management instance falls back to the global default, which the design prohibits. In this case, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. C:RSVP-TE can establish signaled LSPs subject to configured path constraints. That could help when an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route; here, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low.
Question 11At fictional Crestland Networks 003, a regional service-provider network, during a two-site transit migration, operations observes: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. What operational evidence best establishes successful remediation? The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. The primary path stays selected normally and the backup is activated only when the primary is unavailable. The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. Protection triggers on test violations and normal subscriber frames still forward. ExplanationCorrect Answer B:The primary path stays selected normally and the backup is activated only when the primary is unavailable. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. Incorrect Answers A:The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. That option concerns an operator changes route preference to make a broader prefix override a healthy more-specific prefix. The problem here is different: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. C:The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. This could matter when a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. In this case, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. D:Protection triggers on test violations and normal subscriber frames still forward. That could help when a configuration change enables a customer loop-prevention override that also disables root and BPDU safeguards; here, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low.
Question 12At fictional Crestland Networks 003, a regional service-provider network, during a two-site transit migration, operations observes: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. Which operational harm would persist without the intended correction? Legitimate customer traffic is blackholed by an overbroad discard definition. Invalid or unintended address space can enter forwarding decisions and misdirect traffic. Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. Packets cannot reach the intended next hop despite a syntactically valid address. ExplanationCorrect Answer C:Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. Incorrect Answers A:Legitimate customer traffic is blackholed by an overbroad discard definition. The choice would be appropriate if a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. Here, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. B:Invalid or unintended address space can enter forwarding decisions and misdirect traffic. That option concerns a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. The problem here is different: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. D:Packets cannot reach the intended next hop despite a syntactically valid address. This could matter when an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design. In this case, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low.
Question 13In a separate fictional JNCIS-SP lab review for Silverlake Routing 004, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. What should the Junos specialist change first to resolve this specific fault? Place an approved default route into the management routing instance and check its specific table. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. Inspect spanning-tree port role, state, and received BPDU information before changing hardware. ExplanationCorrect Answer C:Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. The primary path stays selected normally and the backup is activated only when the primary is unavailable. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. Incorrect Answers A:Place an approved default route into the management routing instance and check its specific table. This addresses a situation in which a route lookup for a management instance falls back to the global default, which the design prohibits; however, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. B:Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. The choice would be appropriate if a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. Here, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. D:Inspect spanning-tree port role, state, and received BPDU information before changing hardware. It addresses a different problem: A link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. Here, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low.
Question 14In a separate fictional JNCIS-SP lab review for Silverlake Routing 004, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. What technical principle underlies the right remedy? Generated routes depend on qualifying routes and their configured policy, not merely on a destination name. A configured static route forwards only after Junos can resolve its forwarding next hop. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. NSB is intended to maintain relevant Layer 2 control-plane continuity through supported failover. ExplanationCorrect Answer C:For otherwise comparable routes, Junos route preference influences which eligible route becomes active. The primary path stays selected normally and the backup is activated only when the primary is unavailable. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. Incorrect Answers A:Generated routes depend on qualifying routes and their configured policy, not merely on a destination name. That relates to circumstances in which a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route. Here the problem is that a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. B:A configured static route forwards only after Junos can resolve its forwarding next hop. This addresses a situation in which a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface; however, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. D:NSB is intended to maintain relevant Layer 2 control-plane continuity through supported failover. That option concerns a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets. The problem here is different: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low.
Question 15In a separate fictional JNCIS-SP lab review for Silverlake Routing 004, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. Which acceptance finding demonstrates the affected service has recovered? The primary path stays selected normally and the backup is activated only when the primary is unavailable. Each tenant's route lookup uses its own instance table and reaches only authorized customer next hops. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. All routers compute the expected cost and favor the intended transit route. ExplanationCorrect Answer A:The primary path stays selected normally and the backup is activated only when the primary is unavailable. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. Incorrect Answers B:Each tenant's route lookup uses its own instance table and reaches only authorized customer next hops. That relates to circumstances in which customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table. Here the problem is that a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. C:Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. This addresses a situation in which a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup; however, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. D:All routers compute the expected cost and favor the intended transit route. The choice would be appropriate if an intended core link metric is truncated by a mismatched metric-style design and fails to shift paths as expected. Here, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low.
Question 16In a separate fictional JNCIS-SP lab review for Silverlake Routing 004, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. What is the direct residual network risk if the fault remains unresolved? Customers lose an intended default path even though the local route definition still exists. A single uplink becomes overloaded while redundant capacity remains idle. A single gateway device fault disconnects all hosts on the VLAN. Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. ExplanationCorrect Answer D:Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. Incorrect Answers A:Customers lose an intended default path even though the local route definition still exists. This relates to a case where a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; the current situation is that a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. B:A single uplink becomes overloaded while redundant capacity remains idle. It is useful for situations where a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed; the reported fault, though, is that a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. C:A single gateway device fault disconnects all hosts on the VLAN. That relates to circumstances in which an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect. Here the problem is that a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low.
Question 17At fictional Seabrook Metro 005, a regional service-provider network, during a preproduction design validation, operations observes: A summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. Which targeted remediation best fits the reported behavior? Put each tenant's interfaces and routes into the intended routing instances and verify separate lookups. Place an approved default route into the management routing instance and check its specific table. Validate the advertised label behavior and egress processing expectations. Inspect the aggregate route contributors and align the summary with the intended component prefixes. ExplanationCorrect Answer D:Inspect the aggregate route contributors and align the summary with the intended component prefixes. Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. Incorrect Answers A:Put each tenant's interfaces and routes into the intended routing instances and verify separate lookups. This could help if customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table, but not when a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. B:Place an approved default route into the management routing instance and check its specific table. This relates to a case where a route lookup for a management instance falls back to the global default, which the design prohibits; the current situation is that a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. C:Validate the advertised label behavior and egress processing expectations. It is useful for situations where an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP; the reported fault, though, is that a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it.
Question 18At fictional Seabrook Metro 005, a regional service-provider network, during a preproduction design validation, operations observes: A summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. Why is this particular correction the best fit for the stated defect? A RIB group permits specifically configured routes to be installed into additional routing tables. Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. Filter-based forwarding selects a routing lookup context based on packet classification. Trunk membership should reflect explicit service authorization, not an unrestricted default. ExplanationCorrect Answer B:Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. Inspect the aggregate route contributors and align the summary with the intended component prefixes. The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. Incorrect Answers A:A RIB group permits specifically configured routes to be installed into additional routing tables. It is relevant if a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table, but the reported issue is that a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. C:Filter-based forwarding selects a routing lookup context based on packet classification. This relates to a case where a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup; the current situation is that a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. D:Trunk membership should reflect explicit service authorization, not an unrestricted default. It is useful for situations where an interface permits every customer VLAN tag despite a contract listing only two approved VLANs; the reported fault, though, is that a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it.
Question 19At fictional Seabrook Metro 005, a regional service-provider network, during a preproduction design validation, operations observes: A summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. What direct observation would prove the corrective action worked? The management routing-table lookup resolves only to the authorized management gateway. The interface unit is operational and the connected subnet appears in the correct routing table. The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. An MPLS-aware trace and service probe pass before and after the selected cutover. ExplanationCorrect Answer C:The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. Inspect the aggregate route contributors and align the summary with the intended component prefixes. Incorrect Answers A:The management routing-table lookup resolves only to the authorized management gateway. This is applicable when a route lookup for a management instance falls back to the global default, which the design prohibits; the present condition is that a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. B:The interface unit is operational and the connected subnet appears in the correct routing table. It is relevant if a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout, but the reported issue is that a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. D:An MPLS-aware trace and service probe pass before and after the selected cutover. This relates to a case where a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested; the current situation is that a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it.
Question 20At fictional Seabrook Metro 005, a regional service-provider network, during a preproduction design validation, operations observes: A summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. Which failure consequence follows most closely from ignoring this issue? Customers lose an intended default path even though the local route definition still exists. Traffic crosses a customer boundary and violates contractual segmentation. IPv6 customers lose external paths despite healthy IPv4 peering. An inappropriate summary attracts packets for destinations the provider cannot actually reach. ExplanationCorrect Answer D:An inappropriate summary attracts packets for destinations the provider cannot actually reach. Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. Inspect the aggregate route contributors and align the summary with the intended component prefixes. Incorrect Answers A:Customers lose an intended default path even though the local route definition still exists. That could help when a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; here, a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. B:Traffic crosses a customer boundary and violates contractual segmentation. This is applicable when customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table; the present condition is that a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. C:IPv6 customers lose external paths despite healthy IPv4 peering. It is relevant if an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled, but the reported issue is that a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it.