Question 940At fictional Fairhaven Broadband 235, a regional service-provider network, during a preproduction design validation, operations observes: A provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. Which operational harm would persist without the intended correction? Maintenance triggers avoidable traffic loss and prolonged recovery. A single gateway device fault disconnects all hosts on the VLAN. Intermittent route loss causes repeated customer outages. A single member fault causes a complete customer circuit outage. ExplanationCorrect Answer D:A single member fault causes a complete customer circuit outage. LAG availability depends on traffic being redirected to healthy active members after failure. Run a controlled member failure test and verify surviving-link service forwarding. Incorrect Answers A:Maintenance triggers avoidable traffic loss and prolonged recovery. This relates to a case where a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared; the current situation is that a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. B:A single gateway device fault disconnects all hosts on the VLAN. It is useful for situations where an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect; the reported fault, though, is that a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. C:Intermittent route loss causes repeated customer outages. That relates to circumstances in which an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. Here the problem is that a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails.
Question 941In a separate fictional JNCIS-SP lab review for Cedarwater Transit 236, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. What should the Junos specialist change first to resolve this specific fault? Align supported member configuration and verify aggregation state and distributed traffic. Verify nonstop bridging and platform-specific switchover readiness for the intended bridge domains. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends. Run a controlled member failure test and verify surviving-link service forwarding. ExplanationCorrect Answer D:Run a controlled member failure test and verify surviving-link service forwarding. Loss of one link leaves the logical bundle up and service traffic continues on the other. LAG availability depends on traffic being redirected to healthy active members after failure. Incorrect Answers A:Align supported member configuration and verify aggregation state and distributed traffic. This could help if a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ, but not when a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. B:Verify nonstop bridging and platform-specific switchover readiness for the intended bridge domains. This relates to a case where a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets; the current situation is that a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. C:Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends. It is useful for situations where monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered; the reported fault, though, is that a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails.
Question 942In a separate fictional JNCIS-SP lab review for Cedarwater Transit 236, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. What technical principle underlies the right remedy? NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. LAG availability depends on traffic being redirected to healthy active members after failure. BGP peers use negotiated timers to detect failed sessions and maintain liveness. ExplanationCorrect Answer C:LAG availability depends on traffic being redirected to healthy active members after failure. Loss of one link leaves the logical bundle up and service traffic continues on the other. Run a controlled member failure test and verify surviving-link service forwarding. Incorrect Answers A:NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation. It is relevant if traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state, but the reported issue is that a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. B:Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. This could help if a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared, but not when a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. D:BGP peers use negotiated timers to detect failed sessions and maintain liveness. It is useful for situations where a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions; the reported fault, though, is that a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails.
Question 943In a separate fictional JNCIS-SP lab review for Cedarwater Transit 236, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. Which acceptance finding demonstrates the affected service has recovered? Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval. Loss of one link leaves the logical bundle up and service traffic continues on the other. A controlled path failure produces the designed BFD event and route withdrawal within target bounds. The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. ExplanationCorrect Answer B:Loss of one link leaves the logical bundle up and service traffic continues on the other. Run a controlled member failure test and verify surviving-link service forwarding. LAG availability depends on traffic being redirected to healthy active members after failure. Incorrect Answers A:Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval. This is applicable when a provider assumes graceful restart will work during a routing process restart without considering neighbor support; the present condition is that a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. C:A controlled path failure produces the designed BFD event and route withdrawal within target bounds. This could help if a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow, but not when a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. D:The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. This relates to a case where a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface; the current situation is that a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails.
Question 944In a separate fictional JNCIS-SP lab review for Cedarwater Transit 236, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. What is the direct residual network risk if the fault remains unresolved? Customers experience extended blackholes before alternate paths take over. A single member fault causes a complete customer circuit outage. Traffic is blackholed because neighbors keep invalid routes or fail to assist recovery. Outbound traffic takes an expensive or congested transit link. ExplanationCorrect Answer B:A single member fault causes a complete customer circuit outage. Run a controlled member failure test and verify surviving-link service forwarding. LAG availability depends on traffic being redirected to healthy active members after failure. Incorrect Answers A:Customers experience extended blackholes before alternate paths take over. That could help when a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow; here, a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. C:Traffic is blackholed because neighbors keep invalid routes or fail to assist recovery. It is relevant if a provider assumes graceful restart will work during a routing process restart without considering neighbor support, but the reported issue is that a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. D:Outbound traffic takes an expensive or congested transit link. This could help if a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset, but not when a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails.
Question 945At fictional Riverstone Networks 237, a regional service-provider network, during a core-routing acceptance test, operations observes: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. Which targeted remediation best fits the reported behavior? Configure supported BFD monitoring with the neighbor protocol and validate failure detection behavior. Enable and verify supported nonstop active routing with required redundancy prerequisites. Configure and validate supported GRES readiness before an authorized controlled failover. Configure the supported IPv6 IS-IS family and confirm prefix reachability at intended levels. ExplanationCorrect Answer C:Configure and validate supported GRES readiness before an authorized controlled failover. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. The backup Routing Engine becomes active and forwarding remains within the accepted interruption budget. Incorrect Answers A:Configure supported BFD monitoring with the neighbor protocol and validate failure detection behavior. This could matter when a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow. In this case, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. B:Enable and verify supported nonstop active routing with required redundancy prerequisites. That could help when traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state; here, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. D:Configure the supported IPv6 IS-IS family and confirm prefix reachability at intended levels. It is relevant if an IPv6 service prefix is missing from an IS-IS network because the necessary topology and family capability were not enabled, but the reported issue is that a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.
Question 946At fictional Riverstone Networks 237, a regional service-provider network, during a core-routing acceptance test, operations observes: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. Why is this particular correction the best fit for the stated defect? High availability must be evaluated by usable service forwarding as well as control-plane states. NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation. LDP distributes label mappings needed for label-switched forwarding paths. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. ExplanationCorrect Answer D:Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. Configure and validate supported GRES readiness before an authorized controlled failover. The backup Routing Engine becomes active and forwarding remains within the accepted interruption budget. Incorrect Answers A:High availability must be evaluated by usable service forwarding as well as control-plane states. It addresses a different problem: An availability test is signed off because BFD and VRRP report healthy, but customer packets still drop during failover. Here, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. B:NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation. This could matter when traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. In this case, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. C:LDP distributes label mappings needed for label-switched forwarding paths. That could help when an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop; here, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.
Question 947At fictional Riverstone Networks 237, a regional service-provider network, during a core-routing acceptance test, operations observes: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. What direct observation would prove the corrective action worked? The backup Routing Engine becomes active and forwarding remains within the accepted interruption budget. A controlled path failure produces the designed BFD event and route withdrawal within target bounds. MAC tables and customer bridge forwarding remain stable during controlled switchover. The LDP neighbor is operational and exchanges label mappings for expected FECs. ExplanationCorrect Answer A:The backup Routing Engine becomes active and forwarding remains within the accepted interruption budget. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. Configure and validate supported GRES readiness before an authorized controlled failover. Incorrect Answers B:A controlled path failure produces the designed BFD event and route withdrawal within target bounds. It addresses a different problem: A core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow. Here, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. C:MAC tables and customer bridge forwarding remain stable during controlled switchover. This could matter when a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets. In this case, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. D:The LDP neighbor is operational and exchanges label mappings for expected FECs. That could help when two core routers cannot form an LDP session even though they discover one another on the connected link; here, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.
Question 948At fictional Riverstone Networks 237, a regional service-provider network, during a core-routing acceptance test, operations observes: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. Which failure consequence follows most closely from ignoring this issue? Traffic is blackholed because neighbors keep invalid routes or fail to assist recovery. Maintenance triggers avoidable traffic loss and prolonged recovery. Subscribers suffer flooding or Layer 2 interruption after a supervisor failure. Sensitive application traffic bypasses the required upstream inspection or transit path. ExplanationCorrect Answer B:Maintenance triggers avoidable traffic loss and prolonged recovery. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. Configure and validate supported GRES readiness before an authorized controlled failover. Incorrect Answers A:Traffic is blackholed because neighbors keep invalid routes or fail to assist recovery. The choice would be appropriate if a provider assumes graceful restart will work during a routing process restart without considering neighbor support. Here, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. C:Subscribers suffer flooding or Layer 2 interruption after a supervisor failure. It addresses a different problem: A switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets. Here, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. D:Sensitive application traffic bypasses the required upstream inspection or transit path. This could matter when a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. In this case, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.
Question 949In a separate fictional JNCIS-SP lab review for Windmere Fiber 238, a carrier-edge and core routing team, following a monitored network change window, engineers find: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. What intervention most directly restores the intended routing or switching behavior? Configure and validate supported GRES readiness before an authorized controlled failover. Enable and verify supported nonstop active routing with required redundancy prerequisites. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery. Perform controlled LSP validation and only then switch the authorized service resolution. ExplanationCorrect Answer A:Configure and validate supported GRES readiness before an authorized controlled failover. The backup Routing Engine becomes active and forwarding remains within the accepted interruption budget. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. Incorrect Answers B:Enable and verify supported nonstop active routing with required redundancy prerequisites. The choice would be appropriate if traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. Here, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. C:Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery. That option concerns a provider assumes graceful restart will work during a routing process restart without considering neighbor support. The problem here is different: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. D:Perform controlled LSP validation and only then switch the authorized service resolution. It addresses a different problem: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. Here, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.
Question 950In a separate fictional JNCIS-SP lab review for Windmere Fiber 238, a carrier-edge and core routing team, following a monitored network change window, engineers find: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. Which networking principle explains why the proposed correction is appropriate? LAG availability depends on traffic being redirected to healthy active members after failure. A link aggregation group forwards correctly only over members meeting the operational bundle requirements. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. An Ethernet port's VLAN tagging behavior must match the frames it receives. ExplanationCorrect Answer C:Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. The backup Routing Engine becomes active and forwarding remains within the accepted interruption budget. Configure and validate supported GRES readiness before an authorized controlled failover. Incorrect Answers A:LAG availability depends on traffic being redirected to healthy active members after failure. That relates to circumstances in which a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. Here the problem is that a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. B:A link aggregation group forwards correctly only over members meeting the operational bundle requirements. This addresses a situation in which a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ; however, a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared. D:An Ethernet port's VLAN tagging behavior must match the frames it receives. That option concerns a provider access port drops customer tagged frames because it was configured for untagged access mode. The problem here is different: A planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared.