Juniper JN0-364 Practice Test 43 - Prepaway
Practice Exams:

Pass Juniper JN0-364 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

JN0-364 Premium ETE File


  • Premium File 69 Questions & Answers. Last Update: Nov 17, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Juniper JN0-364 Practice Test 43

Question 420

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Distinguishing evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.) after independently checking (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.) after independently checking (The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.) after independently checking (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.) after independently checking (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: A

A.

The approval decision should consider Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The specific proposal is: Approve only the bounded change (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.) after independently checking (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.), without quietly widening the provider or customer network scope. Its measurable outcome is: Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.

B.

An alternative approval would approve only the bounded change (Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.) after independently checking (The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface and Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route, respectively.

C.

Another proposed approval would approve only the bounded change (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.) after independently checking (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

D.

A separate release decision would approve only the bounded change (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.) after independently checking (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.), without quietly widening the provider or customer network scope. It does not match the current change: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.

Question 421

A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Distinguishing evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.
  2. Bounded remedy: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.
  3. Bounded remedy: Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.
  4. Bounded remedy: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.

Answer and Explanation

Correct Answer: C

A.

Another proposed action is: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association. That does not directly address the observed condition: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The more targeted correction is: Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.

B.

Another proposed action is: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately. It targets a different dependency; the evidence here is Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

C.

The issue turns on Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The relevant rule is that GRE encapsulation adds overhead and must be validated against underlay MTU and packet handling. The targeted correction is: Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.

D.

That alternative concerns: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints. The relevant evidence is Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The corresponding fix is: Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.

Question 422

A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.
  2. Differentiating observation: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
  3. Differentiating observation: The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.
  4. Differentiating observation: Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization.

Answer and Explanation

Correct Answer: A

A.

Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. That fact identifies the relevant dependency, rather than a separate issue. GRE encapsulation adds overhead and must be validated against underlay MTU and packet handling.

B.

Another proposed finding is: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. It is not the recorded discriminator, which is Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

C.

Another piece of evidence concerns the route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing. The current incident instead shows: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. This distinction supports the action: Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.

D.

Another alternative would address Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization as decisive. The actual evidence in this case is Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

Question 423

A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Distinguishing evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. Which Junos networking principle best explains the relevant engineering decision?

  1. Applicable protocol principle: The tunnel transport endpoint route must not depend recursively on the same tunnel it enables. Evidence for this case: The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.
  2. Applicable protocol principle: GRE encapsulation adds overhead and must be validated against underlay MTU and packet handling. Evidence for this case: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.
  3. Applicable protocol principle: IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability. Evidence for this case: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.
  4. Applicable protocol principle: IP tunnels require reachable correctly configured outer endpoints independently of the inner routed service. Evidence for this case: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.

Answer and Explanation

Correct Answer: B

A.

The competing option invokes: The tunnel transport endpoint route must not depend recursively on the same tunnel it enables. Evidence for this case: The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing. The present evidence is: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The case-relevant principle is: GRE encapsulation adds overhead and must be validated against underlay MTU and packet handling.

B.

GRE encapsulation adds overhead and must be validated against underlay MTU and packet handling. This distinction accounts for Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter; another unrelated mechanism would not address the same condition.

C.

A different principle is: IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability. Evidence for this case: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The present evidence, however, is Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The relevant rule is: GRE encapsulation adds overhead and must be validated against underlay MTU and packet handling.

D.

This alternative invokes: IP tunnels require reachable correctly configured outer endpoints independently of the inner routed service. Evidence for this case: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The governing distinction for the recorded case is GRE encapsulation adds overhead and must be validated against underlay MTU and packet handling.

Question 424

A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Intended bounded correction: Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.
  2. Independent verification: The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.
  3. Independent verification: Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.
  4. Independent verification: A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.

Answer and Explanation

Correct Answer: C

A.

A different option checks: The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic. The case-specific acceptance condition is instead Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.

B.

Passing that test would not establish resolution of the stated issue. The relevant proof is: Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.

C.

Confirm the correction by demonstrating: Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped. This directly tests the intended change, Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.

D.

Another proposed result is: A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed. It would not independently establish the required outcome: Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.

Question 425

A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Distinguishing evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Tunnel endpoint recursion can create a forwarding loop and total outage despite syntactically valid tunnel and route statements.
  2. Meaningful operational caution: Ignoring encapsulation overhead can create hard-to-diagnose selective loss despite a nominally up tunnel interface.
  3. Meaningful operational caution: Successful ordinary IP ping between routers does not prove the tunnel encapsulation source is still configured correctly.
  4. Meaningful operational caution: A syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement.

Answer and Explanation

Correct Answer: B

A.

This limitation concerns another setting: Tunnel endpoint recursion can create a forwarding loop and total outage despite syntactically valid tunnel and route statements. The observed facts here make a different caution decisive: Ignoring encapsulation overhead can create hard-to-diagnose selective loss despite a nominally up tunnel interface.

B.

Ignoring encapsulation overhead can create hard-to-diagnose selective loss despite a nominally up tunnel interface. That boundary protects the documented change, Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls, from introducing an unrelated problem.

C.

Another emphasis concerns: Successful ordinary IP ping between routers does not prove the tunnel encapsulation source is still configured correctly. The current change is Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls; the material limitation is Ignoring encapsulation overhead can create hard-to-diagnose selective loss despite a nominally up tunnel interface.

D.

This limitation concerns another setting: A syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement. The observed facts here make a different caution decisive: Ignoring encapsulation overhead can create hard-to-diagnose selective loss despite a nominally up tunnel interface.

Question 426

A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Distinguishing evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. Which focused investigation is the most useful before modifying the network configuration?

  1. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: BFD history indicates missed rapid control packets correlated with CPU spikes and peer timer negotiation different from the intended service design.
  2. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
  3. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.

Answer and Explanation

Correct Answer: C

A.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: BFD history indicates missed rapid control packets correlated with CPU spikes and peer timer negotiation different from the intended service design. It does not directly establish the reported condition: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

B.

That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

C.

The pre-change check should compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. That check directly concerns Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

D.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing. It does not directly establish the reported condition: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

Question 427

A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Distinguishing evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: First verify the observed failure (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.); review and authorize the bounded correction (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.); then independently verify the intended outcome (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.) before production rollout.
  2. Controlled engineering sequence: First verify the observed failure (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.); review and authorize the bounded correction (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.); then independently verify the intended outcome (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.) before production rollout.
  3. Controlled engineering sequence: First verify the observed failure (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.); review and authorize the bounded correction (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.); then independently verify the intended outcome (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.) before production rollout.
  4. Controlled engineering sequence: First verify the observed failure (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.); review and authorize the bounded correction (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.); then independently verify the intended outcome (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.) before production rollout.

Answer and Explanation

Correct Answer: D

A.

Another possible combination is: First verify the observed failure (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.); review and authorize the bounded correction (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.); then independently verify the intended outcome (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.) before production rollout. The current record instead supports Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls, verified by Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.

B.

Another potential sequence is: First verify the observed failure (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.); review and authorize the bounded correction (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.); then independently verify the intended outcome (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.) before production rollout. It has no direct link to the distinguishing evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

C.

Another action-and-check pairing is: First verify the observed failure (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.); review and authorize the bounded correction (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.); then independently verify the intended outcome (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.) before production rollout. The evidence here is Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The required action and proof are Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls and Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.

D.

The correction is Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls. The matching proof is Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped. Both address the finding that Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

Question 428

A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Distinguishing evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. Which set of evidence, limited change and independent validation best justifies authorization?

  1. Approval package: observed evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), limited correction (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.), independently measurable result (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.).
  2. Approval package: observed evidence (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), limited correction (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.), independently measurable result (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.).
  3. Approval package: observed evidence (Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.), limited correction (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.), independently measurable result (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.).
  4. Approval package: observed evidence (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.), limited correction (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.), independently measurable result (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.).

Answer and Explanation

Correct Answer: B

A.

Another approval action is: Observed evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), limited correction (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.), independently measurable result (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.). The relevant evidence and acceptance are Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter and Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped, respectively.

B.

The approval decision should consider Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The specific proposal is: Observed evidence (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), limited correction (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.), independently measurable result (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.). Its measurable outcome is: Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.

C.

An alternative release decision is: Observed evidence (Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.), limited correction (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.), independently measurable result (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.). It does not match the current change: Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.

D.

Another approval action is: Observed evidence (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.), limited correction (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.), independently measurable result (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.). The relevant evidence and acceptance are Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter and Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped, respectively.

Question 429

A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Distinguishing evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?

  1. If testing fails: pause changes, preserve the differentiating evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), restore the last approved safe network state and reassess gre interface is reachable only from the wrong source address.
  2. If testing fails: pause changes, preserve the differentiating evidence (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.), restore the last approved safe network state and reassess gre route recursion creates a transport forwarding loop.
  3. If testing fails: pause changes, preserve the differentiating evidence (The configured IPv6 link-local next hop exists on multiple segments but operational route resolution references the former interface rather than the active neighbor link.), restore the last approved safe network state and reassess ipv6 static route selects a link-local next hop on the wrong interface.
  4. If testing fails: pause changes, preserve the differentiating evidence (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), restore the last approved safe network state and reassess gre tunnel reports up but payload mtu is too large.

Answer and Explanation

Correct Answer: D

A.

Another option proposes: Pause changes, preserve the differentiating evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), restore the last approved safe network state and reassess gre interface is reachable only from the wrong source address. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), restore the last approved safe network state and reassess gre tunnel reports up but payload mtu is too large.

B.

Another fallback concerns pausing changes, preserve the differentiating evidence (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.), restore the last approved safe network state and reassess gre route recursion creates a transport forwarding loop. The current change concerns Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

C.

Another recovery route would pause changes, preserve the differentiating evidence (The configured IPv6 link-local next hop exists on multiple segments but operational route resolution references the former interface rather than the active neighbor link.), restore the last approved safe network state and reassess ipv6 static route selects a link-local next hop on the wrong interface. It does not preserve the condition of this case: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The bounded fallback is: Pause changes, preserve the differentiating evidence (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), restore the last approved safe network state and reassess gre tunnel reports up but payload mtu is too large.

D.

A recovery option is to pause changes, preserve the differentiating evidence (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), restore the last approved safe network state and reassess gre tunnel reports up but payload mtu is too large. The intended change was Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls, and acceptance must still be judged against Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.

Question 430

A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Distinguishing evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.) after independently checking (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.) after independently checking (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.) after independently checking (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: C

A.

Another proposed approval would approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

B.

A separate release decision would approve only the bounded change (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.) after independently checking (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.), without quietly widening the provider or customer network scope. It does not match the current change: Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.

C.

The approval decision should consider Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The specific proposal is: Approve only the bounded change (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.) after independently checking (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.), without quietly widening the provider or customer network scope. Its measurable outcome is: Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.

D.

Another proposed approval would approve only the bounded change (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.) after independently checking (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests