Question 70In a separate fictional JNCIS-SP lab review for Brightstone Backbone 018, a carrier-edge and core routing team, following a monitored network change window, engineers find: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Which networking principle explains why the proposed correction is appropriate? Filter-based forwarding selects a routing lookup context based on packet classification. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. Routing policy terms should match only their explicitly intended routes before altering route attributes. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. ExplanationCorrect Answer A:Filter-based forwarding selects a routing lookup context based on packet classification. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Incorrect Answers B:For otherwise comparable routes, Junos route preference influences which eligible route becomes active. This could matter when a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. In this case, a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. C:Routing policy terms should match only their explicitly intended routes before altering route attributes. That could help when a broad routing policy term changes preference for all imported prefixes instead of only the intended test network; here, a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. D:Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. This is applicable when a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared; the present condition is that a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup.
Question 71In a separate fictional JNCIS-SP lab review for Brightstone Backbone 018, a carrier-edge and core routing team, following a monitored network change window, engineers find: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Which validation result would confirm the design is now functioning? The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. Both client MACs appear in the intended VLAN and bidirectional frames traverse the switch. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. ExplanationCorrect Answer D:Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Filter-based forwarding selects a routing lookup context based on packet classification. Incorrect Answers A:The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. That option concerns a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. The problem here is different: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. B:The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. It addresses a different problem: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. Here, a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. C:Both client MACs appear in the intended VLAN and bidirectional frames traverse the switch. This could matter when hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier. In this case, a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup.
Question 72In a separate fictional JNCIS-SP lab review for Brightstone Backbone 018, a carrier-edge and core routing team, following a monitored network change window, engineers find: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. What likely service impact does this condition create? Traffic crosses a customer boundary and violates contractual segmentation. Unrelated subscribers change transit paths after a narrowly intended policy update. The backbone link stays out of the routing topology or an unsafe bypass is introduced. Sensitive application traffic bypasses the required upstream inspection or transit path. ExplanationCorrect Answer D:Sensitive application traffic bypasses the required upstream inspection or transit path. Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Filter-based forwarding selects a routing lookup context based on packet classification. Incorrect Answers A:Traffic crosses a customer boundary and violates contractual segmentation. The choice would be appropriate if customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table. Here, a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. B:Unrelated subscribers change transit paths after a narrowly intended policy update. That option concerns a broad routing policy term changes preference for all imported prefixes instead of only the intended test network. The problem here is different: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. C:The backbone link stays out of the routing topology or an unsafe bypass is introduced. It addresses a different problem: A provider IS-IS circuit stops forming neighbors after the authentication key is changed on only one end. Here, a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup.
Question 73At fictional Eastbridge Networks 019, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. Which configuration or operational correction most directly addresses this failure? Correct the static next hop to a reachable transit address and confirm the selected route can resolve. Inspect the aggregate route contributors and align the summary with the intended component prefixes. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. Review RSVP path constraints and explicit-route settings, then reestablish the LSP. ExplanationCorrect Answer C:Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. Incorrect Answers A:Correct the static next hop to a reachable transit address and confirm the selected route can resolve. 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, an operator changes route preference to make a broader prefix override a healthy more-specific prefix. B:Inspect the aggregate route contributors and align the summary with the intended component prefixes. The choice would be appropriate if a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. Here, an operator changes route preference to make a broader prefix override a healthy more-specific prefix. D:Review RSVP path constraints and explicit-route settings, then reestablish the LSP. It addresses a different problem: An RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. Here, an operator changes route preference to make a broader prefix override a healthy more-specific prefix.
Question 74At fictional Eastbridge Networks 019, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. Which Junos forwarding or control-plane rule applies to this case? Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. A RIB group permits specifically configured routes to be installed into additional routing tables. BGP MED expresses a neighboring AS's ingress preference and its comparison scope is policy-dependent. ExplanationCorrect Answer A:Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. Incorrect Answers B:A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. This addresses a situation in which a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised; however, an operator changes route preference to make a broader prefix override a healthy more-specific prefix. C:A RIB group permits specifically configured routes to be installed into additional routing tables. The choice would be appropriate if a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. Here, an operator changes route preference to make a broader prefix override a healthy more-specific prefix. D:BGP MED expresses a neighboring AS's ingress preference and its comparison scope is policy-dependent. That option concerns a network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems. The problem here is different: An operator changes route preference to make a broader prefix override a healthy more-specific prefix.
Question 75At fictional Eastbridge Networks 019, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. What operational evidence best establishes successful remediation? Each tenant's route lookup uses its own instance table and reaches only authorized customer next hops. The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. The link carries protected MPLS traffic only after the required label state is available. ExplanationCorrect Answer B:The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. Incorrect Answers A:Each tenant's route lookup uses its own instance table and reaches only authorized customer next hops. It is useful for situations where customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table; the reported fault, though, is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix. C:The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. This addresses a situation in which a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it; however, an operator changes route preference to make a broader prefix override a healthy more-specific prefix. D:The link carries protected MPLS traffic only after the required label state is available. The choice would be appropriate if a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. Here, an operator changes route preference to make a broader prefix override a healthy more-specific prefix.
Question 76At fictional Eastbridge Networks 019, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. Which operational harm would persist without the intended correction? Management packets leave via a customer-facing path or fail unexpectedly. Neighbor sessions cannot establish because the local link subnet is unreachable. A false fix redirects a customer subnet onto an inappropriate aggregate route. Unplanned DIS churn produces extra flooding and convergence disruption. ExplanationCorrect Answer C:A false fix redirects a customer subnet onto an inappropriate aggregate route. Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. Incorrect Answers A:Management packets leave via a customer-facing path or fail unexpectedly. 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 an operator changes route preference to make a broader prefix override a healthy more-specific prefix. B:Neighbor sessions cannot establish because the local link subnet is unreachable. It is useful for situations where a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout; the reported fault, though, is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix. D:Unplanned DIS churn produces extra flooding and convergence disruption. This addresses a situation in which operators see two possible LAN-designated routers and assume the wrong one leads routing for the shared segment; however, an operator changes route preference to make a broader prefix override a healthy more-specific prefix.
Question 77In a separate fictional JNCIS-SP lab review for Orchard Link 020, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. What should the Junos specialist change first to resolve this specific fault? Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. Restrict the discard summary and verify that intended specific routes win for live destinations. Place an approved default route into the management routing instance and check its specific table. Use the approved source address and confirm matching outer-packet forwarding and policy. ExplanationCorrect Answer A:Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. Incorrect Answers B:Restrict the discard summary and verify that intended specific routes win for live destinations. This relates to a case where a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised; the current situation is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix. C:Place an approved default route into the management routing instance and check its specific table. It is useful for situations where a route lookup for a management instance falls back to the global default, which the design prohibits; the reported fault, though, is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix. D:Use the approved source address and confirm matching outer-packet forwarding and policy. That relates to circumstances in which a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. Here the problem is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix.
Question 78In a separate fictional JNCIS-SP lab review for Orchard Link 020, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. What technical principle underlies the right remedy? Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. A configured static route forwards only after Junos can resolve its forwarding next hop. A RIB group permits specifically configured routes to be installed into additional routing tables. OSPF shortest-path calculations rely on consistent synchronized link-state information within an area. ExplanationCorrect Answer A:Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. Incorrect Answers B:A configured static route forwards only after Junos can resolve its forwarding next hop. This could help if a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface, but not when an operator changes route preference to make a broader prefix override a healthy more-specific prefix. C:A RIB group permits specifically configured routes to be installed into additional routing tables. This relates to a case where a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table; the current situation is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix. D:OSPF shortest-path calculations rely on consistent synchronized link-state information within an area. It is useful for situations where two supposed adjacent routers have different views of a backbone link because database synchronization never completes; the reported fault, though, is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix.
Question 79In a separate fictional JNCIS-SP lab review for Orchard Link 020, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. Which acceptance finding demonstrates the affected service has recovered? The target prefix has the planned preference while unrelated routes retain prior selection. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. The intended EBGP neighbor becomes Established and exchanges authorized prefixes. ExplanationCorrect Answer C:The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. Incorrect Answers A:The target prefix has the planned preference while unrelated routes retain prior selection. This is applicable when a broad routing policy term changes preference for all imported prefixes instead of only the intended test network; the present condition is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix. B:Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. It is relevant if a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup, but the reported issue is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix. D:The intended EBGP neighbor becomes Established and exchanges authorized prefixes. This relates to a case where an external BGP session never reaches Established because the local peer definition uses the wrong remote AS; the current situation is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix.
Question 80In a separate fictional JNCIS-SP lab review for Orchard Link 020, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. What is the direct residual network risk if the fault remains unresolved? Invalid or unintended address space can enter forwarding decisions and misdirect traffic. Management packets leave via a customer-facing path or fail unexpectedly. A false fix redirects a customer subnet onto an inappropriate aggregate route. Repeated control-plane resets withdraw customer routes. ExplanationCorrect Answer C:A false fix redirects a customer subnet onto an inappropriate aggregate route. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. Incorrect Answers A:Invalid or unintended address space can enter forwarding decisions and misdirect traffic. That could help when a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing; here, an operator changes route preference to make a broader prefix override a healthy more-specific prefix. B:Management packets leave via a customer-facing path or fail unexpectedly. 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 an operator changes route preference to make a broader prefix override a healthy more-specific prefix. D:Repeated control-plane resets withdraw customer routes. This could help if a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions, but not when an operator changes route preference to make a broader prefix override a healthy more-specific prefix.