Juniper JN0-364 Practice Test 2 - 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 2

Question 10

A fictional Junos service-provider engineer encounters this scenario: A regional Junos provider edge begins preferring a manually installed default route after a circuit migration, although the specified next-hop address cannot be resolved through any working connected path. Distinguishing evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.) after independently checking (Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.) after independently checking (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.) after independently checking (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.) after independently checking (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.), 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 (Inspect the advertised address-family-specific TLVs and corresponding IPv6 routing table and interface support before changing IS-IS policy.) after independently checking (Both route-family displays match their advertised TLV data and IPv6 next-hop reachability is verified separately.), without quietly widening the provider or customer network scope. The present scope must instead be justified by the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.

B.

A separate release decision would approve only the bounded change (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.) after independently checking (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.), without quietly widening the provider or customer network scope. It does not match the current change: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.

C.

The approval decision should consider the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The specific proposal is: Approve only the bounded change (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.) after independently checking (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.), without quietly widening the provider or customer network scope. Its measurable outcome is: A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.

D.

Another proposed approval would approve only the bounded change (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.) after independently checking (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.), without quietly widening the provider or customer network scope. The present scope must instead be justified by the routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.

Question 11

A fictional Junos service-provider engineer encounters this scenario: An ISP customer aggregation router advertises a summary for several branch networks while one delegated component prefix was withdrawn during an access outage. Distinguishing evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.
  2. Bounded remedy: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.
  3. Bounded remedy: Review VRRP advertisement, tracking and preemption conditions, then restore the documented gateway active-standby policy without forcing an untested outage.
  4. Bounded remedy: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.

Answer and Explanation

Correct Answer: B

A.

Another proposed action is: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change. That does not directly address the observed condition: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The more targeted correction is: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.

B.

The evidence for the issue is BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The matching step is: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior. This follows the principle that Aggregate route advertisement must be evaluated with constituent route state and actual forwarding reachability.

C.

Another option proposes: Review VRRP advertisement, tracking and preemption conditions, then restore the documented gateway active-standby policy without forcing an untested outage. The specific correction is: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior. The deciding evidence is: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

D.

That alternative concerns: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration. The relevant evidence is BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The corresponding fix is: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.

Question 12

A fictional Junos service-provider engineer encounters this scenario: An ISP customer aggregation router advertises a summary for several branch networks while one delegated component prefix was withdrawn during an access outage. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.
  2. Differentiating observation: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.
  3. Differentiating observation: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.
  4. Differentiating observation: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

Answer and Explanation

Correct Answer: A

A.

Consider this evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The applicable explanation is: Aggregate route advertisement must be evaluated with constituent route state and actual forwarding reachability. The matching response is: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.

B.

Another alternative would address the script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance as decisive. The actual evidence in this case is BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

C.

This other option describes: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route. The problem to explain is different: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

D.

Another proposed finding is: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. It is not the recorded discriminator, which is BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

Question 13

A fictional Junos service-provider engineer encounters this scenario: An ISP customer aggregation router advertises a summary for several branch networks while one delegated component prefix was withdrawn during an access outage. Distinguishing evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. Which Junos networking principle best explains the relevant engineering decision?

  1. Applicable protocol principle: Routing instances and RIB groups require explicit route import and forwarding boundaries. Evidence for this case: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.
  2. Applicable protocol principle: Junos forwarding load balancing depends on the configured policy and traffic hashing, and must be validated against suitable flows. Evidence for this case: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.
  3. Applicable protocol principle: Aggregate route advertisement must be evaluated with constituent route state and actual forwarding reachability. Evidence for this case: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.
  4. Applicable protocol principle: GRES depends on supported synchronized Routing Engine state, not hardware redundancy alone. Evidence for this case: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.

Answer and Explanation

Correct Answer: C

A.

A different principle is: Routing instances and RIB groups require explicit route import and forwarding boundaries. Evidence for this case: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route. The present evidence, however, is BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The relevant rule is: Aggregate route advertisement must be evaluated with constituent route state and actual forwarding reachability.

B.

This alternative invokes: Junos forwarding load balancing depends on the configured policy and traffic hashing, and must be validated against suitable flows. Evidence for this case: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link. The governing distinction for the recorded case is Aggregate route advertisement must be evaluated with constituent route state and actual forwarding reachability.

C.

The observed evidence is: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The governing principle is: Aggregate route advertisement must be evaluated with constituent route state and actual forwarding reachability. Consequently, the targeted action is: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.

D.

That principle concerns another fact pattern: GRES depends on supported synchronized Routing Engine state, not hardware redundancy alone. Evidence for this case: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. Here the key fact is: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

Question 14

A fictional Junos service-provider engineer encounters this scenario: An ISP customer aggregation router advertises a summary for several branch networks while one delegated component prefix was withdrawn during an access outage. Intended bounded correction: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior. Which independently verifiable test best demonstrates the intended correction worked?

  1. 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.
  2. Independent verification: Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.
  3. Independent verification: Controlled primary failure and recovery show a predictable gateway master role and preserved host connectivity.
  4. Independent verification: The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.

Answer and Explanation

Correct Answer: B

A.

That result would assess another condition: A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed. The correct criterion is directly linked to the finding: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

B.

Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch. This verifies the required result rather than merely stating the action; the original issue was BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

C.

A different option checks: Controlled primary failure and recovery show a predictable gateway master role and preserved host connectivity. The case-specific acceptance condition is instead Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.

D.

Passing that test would not establish resolution of the stated issue. The relevant proof is: Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.

Question 15

A fictional Junos service-provider engineer encounters this scenario: An ISP customer aggregation router advertises a summary for several branch networks while one delegated component prefix was withdrawn during an access outage. Distinguishing evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Per-packet expectations applied to flow-hashed traffic can drive damaging changes and create packet reordering.
  2. Meaningful operational caution: Conflating distinct high-availability features can make unsupported hitless-upgrade promises and lead to unexpected service loss.
  3. Meaningful operational caution: A syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement.
  4. Meaningful operational caution: A filter term matching too broadly can redirect critical control-plane and operations traffic to the wrong path.

Answer and Explanation

Correct Answer: C

A.

Another emphasis concerns: Per-packet expectations applied to flow-hashed traffic can drive damaging changes and create packet reordering. The current change is Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior; the material limitation is a syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement.

B.

This limitation concerns another setting: Conflating distinct high-availability features can make unsupported hitless-upgrade promises and lead to unexpected service loss. The observed facts here make a different caution decisive: A syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement.

C.

The relevant boundary is: A syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement. It matters when applying the specific response: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.

D.

Another emphasis concerns: A filter term matching too broadly can redirect critical control-plane and operations traffic to the wrong path. The current change is Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior; the material limitation is a syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement.

Question 16

A fictional Junos service-provider engineer encounters this scenario: An ISP customer aggregation router advertises a summary for several branch networks while one delegated component prefix was withdrawn during an access outage. Distinguishing evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. 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: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.
  2. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.
  3. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

Answer and Explanation

Correct Answer: D

A.

Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route. The case observation to isolate is BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

B.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. It does not directly establish the reported condition: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

C.

That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

D.

The focused investigation should compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. It is tied to the observed evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. It tests the conditions for this response: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.

Question 17

A fictional Junos service-provider engineer encounters this scenario: An ISP customer aggregation router advertises a summary for several branch networks while one delegated component prefix was withdrawn during an access outage. Distinguishing evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: First verify the observed failure (The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.); review and authorize the bounded correction (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.); then independently verify the intended outcome (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.) before production rollout.
  2. Controlled engineering sequence: First verify the observed failure (Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.); review and authorize the bounded correction (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.); then independently verify the intended outcome (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.) before production rollout.
  3. Controlled engineering sequence: First verify the observed failure (Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors.); review and authorize the bounded correction (Inspect LAG member speed, LACP participation and physical health, then repair or isolate the anomalous member under approved redundancy policy.); then independently verify the intended outcome (All intended members participate compatibly and multi-flow traffic crosses the LAG without selective packet loss.) before production rollout.
  4. Controlled engineering sequence: First verify the observed failure (BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.); review and authorize the bounded correction (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.); then independently verify the intended outcome (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.) before production rollout.

Answer and Explanation

Correct Answer: D

A.

Another action-and-check pairing is: First verify the observed failure (The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.); review and authorize the bounded correction (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.); then independently verify the intended outcome (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.) before production rollout. The evidence here is BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The required action and proof are Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior and Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.

B.

An alternative plan is: First verify the observed failure (Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.); review and authorize the bounded correction (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.); then independently verify the intended outcome (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.) before production rollout. It does not test the case-specific condition: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

C.

Another possible combination is: First verify the observed failure (Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors.); review and authorize the bounded correction (Inspect LAG member speed, LACP participation and physical health, then repair or isolate the anomalous member under approved redundancy policy.); then independently verify the intended outcome (All intended members participate compatibly and multi-flow traffic crosses the LAG without selective packet loss.) before production rollout. The current record instead supports Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior, verified by Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.

D.

The starting point is BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The proposed action and its separate check are Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior and Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch, respectively.

Question 18

A fictional Junos service-provider engineer encounters this scenario: An ISP customer aggregation router advertises a summary for several branch networks while one delegated component prefix was withdrawn during an access outage. Distinguishing evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. Which set of evidence, limited change and independent validation best justifies authorization?

  1. Approval package: observed evidence (The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.), limited correction (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.), independently measurable result (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.).
  2. Approval package: observed evidence (Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.), limited correction (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.), independently measurable result (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.).
  3. Approval package: observed evidence (BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.), limited correction (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.), independently measurable result (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.).
  4. Approval package: observed evidence (Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.), limited correction (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.), independently measurable result (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.).

Answer and Explanation

Correct Answer: C

A.

An alternative release decision is: Observed evidence (The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.), limited correction (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.), independently measurable result (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.). It does not match the current change: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.

B.

Another approval action is: Observed evidence (Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.), limited correction (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.), independently measurable result (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.). The relevant evidence and acceptance are BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails and Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch, respectively.

C.

The bounded proposal is: Observed evidence (BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.), limited correction (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.), independently measurable result (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.). The separate acceptance measure remains: Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.

D.

An alternative release decision is: Observed evidence (Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.), limited correction (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.), independently measurable result (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.). It does not match the current change: Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.

Question 19

A fictional Junos service-provider engineer encounters this scenario: An ISP customer aggregation router advertises a summary for several branch networks while one delegated component prefix was withdrawn during an access outage. Distinguishing evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. 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 (BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.), restore the last approved safe network state and reassess aggregate route hides a needed more-specific reachability signal.
  2. If testing fails: pause changes, preserve the differentiating evidence (The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.), restore the last approved safe network state and reassess static route becomes active despite unreachable ultimate next hop.
  3. If testing fails: pause changes, preserve the differentiating evidence (The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.), restore the last approved safe network state and reassess filter-based forwarding changes the wrong customer stream.
  4. If testing fails: pause changes, preserve the differentiating evidence (OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination.), restore the last approved safe network state and reassess single-area lsa information is not visible as an installed route.

Answer and Explanation

Correct Answer: A

A.

If the change fails acceptance, the bounded recovery is: Pause changes, preserve the differentiating evidence (BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.), restore the last approved safe network state and reassess aggregate route hides a needed more-specific reachability signal. The case-specific risk is a syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement. The original evidence remains: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

B.

Another option proposes: Pause changes, preserve the differentiating evidence (The routing table shows the configured static prefix with an unresolved next-hop state while the new transit interface has a different active adjacency and reachable gateway.), restore the last approved safe network state and reassess static route becomes active despite unreachable ultimate next hop. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.), restore the last approved safe network state and reassess aggregate route hides a needed more-specific reachability signal.

C.

Another fallback concerns pausing changes, preserve the differentiating evidence (The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.), restore the last approved safe network state and reassess filter-based forwarding changes the wrong customer stream. The current change concerns BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

D.

Another recovery route would pause changes, preserve the differentiating evidence (OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination.), restore the last approved safe network state and reassess single-area lsa information is not visible as an installed route. It does not preserve the condition of this case: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The bounded fallback is: Pause changes, preserve the differentiating evidence (BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.), restore the last approved safe network state and reassess aggregate route hides a needed more-specific reachability signal.

Question 20

A fictional Junos service-provider engineer encounters this scenario: An ISP customer aggregation router advertises a summary for several branch networks while one delegated component prefix was withdrawn during an access outage. Distinguishing evidence: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Inspect the broadcast network type, priorities and DR election state before changing any OSPF settings; document expected adjacency behavior.) after independently checking (The observed DR and BDR remain legitimate and all routers learn correct routes without forcing unnecessary full mesh adjacencies.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.) after independently checking (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.) after independently checking (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.) after independently checking (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: C

A.

An alternative approval would approve only the bounded change (Inspect the broadcast network type, priorities and DR election state before changing any OSPF settings; document expected adjacency behavior.) after independently checking (The observed DR and BDR remain legitimate and all routers learn correct routes without forcing unnecessary full mesh adjacencies.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails and Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch, respectively.

B.

Another proposed approval would approve only the bounded change (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.) after independently checking (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.), without quietly widening the provider or customer network scope. The present scope must instead be justified by BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

C.

The change-control boundary is: Approve only the bounded change (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.) after independently checking (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.), without quietly widening the provider or customer network scope. The evidence for this scope is BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.

D.

An alternative approval would approve only the bounded change (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.) after independently checking (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails and Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch, respectively.

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