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

Question 30

A fictional Junos service-provider engineer encounters this scenario: A managed VPN customer should access only a shared DNS resolver but a new Junos routing-instance import arrangement exposes other tenant-connected prefixes. Distinguishing 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. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.) after independently checking (The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.), 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 the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.) after independently checking (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.) after independently checking (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: D

A.

A separate release decision would approve only the bounded change (Validate LAN circuit priority and DIS role independently from route metrics; change only the control-plane election setting if the design requires it.) after independently checking (The designated intermediate system role matches documented circuit priority policy and shortest-path computations remain consistent.), without quietly widening the provider or customer network scope. It does not match the current change: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.

B.

An alternative 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 relevant evidence and acceptance are Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route and the shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests, respectively.

C.

Another proposed approval would approve only the bounded change (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.) after independently checking (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

D.

The approval decision should consider 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 specific proposal is: Approve only the bounded change (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.) after independently checking (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.), without quietly widening the provider or customer network scope. Its measurable outcome is: The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.

Question 31

A fictional Junos service-provider engineer encounters this scenario: A service provider deploys policy-based forwarding for one customer traffic class but unexpectedly sends management packets through a costly transit instead of the management path. Distinguishing evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. 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.
  2. Bounded remedy: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.
  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: Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.

Answer and Explanation

Correct Answer: B

A.

Another proposed 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. That does not directly address the observed condition: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. The more targeted correction is: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.

B.

The evidence is the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. The relevant principle is that Filter-based forwarding changes packet forwarding based on matched ingress policy, not merely destination route preference. The correction is: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order. The separate success check is: Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.

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: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order. The deciding evidence is: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

D.

That alternative concerns: Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution. The relevant evidence is the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. The corresponding fix is: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.

Question 32

A fictional Junos service-provider engineer encounters this scenario: A service provider deploys policy-based forwarding for one customer traffic class but unexpectedly sends management packets through a costly transit instead of the management path. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency.
  2. Differentiating observation: 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.
  3. Differentiating observation: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.
  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: D

A.

Another piece of evidence concerns Operational IS-IS output shows compatible physical interfaces but inconsistent enabled protocol levels and no common level adjacency. The current incident instead shows: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. This distinction supports the action: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.

B.

Another alternative would address 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 as decisive. The actual evidence in this case is the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

C.

This other option describes: 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 problem to explain is different: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

D.

The record points to the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. After confirming the clue, the appropriate response is: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.

Question 33

A fictional Junos service-provider engineer encounters this scenario: A service provider deploys policy-based forwarding for one customer traffic class but unexpectedly sends management packets through a costly transit instead of the management path. Distinguishing evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. Which Junos networking principle best explains the relevant engineering decision?

  1. 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.
  2. 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.
  3. Applicable protocol principle: IS-IS path computation follows topology information and relevant link metrics. Evidence for this case: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.
  4. Applicable protocol principle: Filter-based forwarding changes packet forwarding based on matched ingress policy, not merely destination route preference. Evidence for this case: 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: D

A.

A different principle is: 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 present evidence, however, is the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. The relevant rule is: Filter-based forwarding changes packet forwarding based on matched ingress policy, not merely destination route preference.

B.

This alternative invokes: 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. The governing distinction for the recorded case is Filter-based forwarding changes packet forwarding based on matched ingress policy, not merely destination route preference.

C.

The competing option invokes: IS-IS path computation follows topology information and relevant link metrics. Evidence for this case: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. The present evidence is: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. The case-relevant principle is: Filter-based forwarding changes packet forwarding based on matched ingress policy, not merely destination route preference.

D.

Filter-based forwarding changes packet forwarding based on matched ingress policy, not merely destination route preference. This distinction accounts for the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix; another unrelated mechanism would not address the same condition.

Question 34

A fictional Junos service-provider engineer encounters this scenario: A service provider deploys policy-based forwarding for one customer traffic class but unexpectedly sends management packets through a costly transit instead of the management path. Intended bounded correction: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.
  2. 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.
  3. Independent verification: The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged.
  4. 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.

Answer and Explanation

Correct Answer: A

A.

Confirm the correction by demonstrating: Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable. This directly tests the intended change, Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.

B.

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: Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.

C.

A different option checks: The pair establishes an adjacency at the planned level and corresponding level-specific link-state information is exchanged. The case-specific acceptance condition is instead Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.

D.

Passing that test would not establish resolution of the stated issue. The relevant proof is: Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.

Question 35

A fictional Junos service-provider engineer encounters this scenario: A service provider deploys policy-based forwarding for one customer traffic class but unexpectedly sends management packets through a costly transit instead of the management path. Distinguishing evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Changing global route preferences to force a broken next hop can blackhole unrelated customer prefixes.
  2. Meaningful operational caution: Treating expected two-way neighbor states as faults can trigger unnecessary election changes and route churn.
  3. Meaningful operational caution: Per-packet expectations applied to flow-hashed traffic can drive damaging changes and create packet reordering.
  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: D

A.

This limitation concerns another setting: Changing global route preferences to force a broken next hop can blackhole unrelated customer prefixes. The observed facts here make a different caution decisive: A filter term matching too broadly can redirect critical control-plane and operations traffic to the wrong path.

B.

Another caution is: Treating expected two-way neighbor states as faults can trigger unnecessary election changes and route churn. The key risk in this case is: A filter term matching too broadly can redirect critical control-plane and operations traffic to the wrong path.

C.

Another emphasis concerns: Per-packet expectations applied to flow-hashed traffic can drive damaging changes and create packet reordering. The current change is Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order; the material limitation is a filter term matching too broadly can redirect critical control-plane and operations traffic to the wrong path.

D.

A filter term matching too broadly can redirect critical control-plane and operations traffic to the wrong path. That boundary protects the documented change, Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order, from introducing an unrelated problem.

Question 36

A fictional Junos service-provider engineer encounters this scenario: A service provider deploys policy-based forwarding for one customer traffic class but unexpectedly sends management packets through a costly transit instead of the management path. Distinguishing evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. 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: 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.
  2. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.
  3. 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.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.

Answer and Explanation

Correct Answer: B

A.

Another investigation would 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. It does not directly establish the reported condition: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

B.

The focused investigation should compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. It is tied to the observed evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. It tests the conditions for this response: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.

C.

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 the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

D.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path. It does not directly establish the reported condition: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

Question 37

A fictional Junos service-provider engineer encounters this scenario: A service provider deploys policy-based forwarding for one customer traffic class but unexpectedly sends management packets through a costly transit instead of the management path. Distinguishing evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: First verify the observed failure (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.); review and authorize the bounded correction (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.); then independently verify the intended outcome (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.) before production rollout.
  2. 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.
  3. 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.
  4. Controlled engineering sequence: First verify the observed failure (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.); review and authorize the bounded correction (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.); then independently verify the intended outcome (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.) before production rollout.

Answer and Explanation

Correct Answer: B

A.

Another action-and-check pairing is: First verify the observed failure (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.); review and authorize the bounded correction (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.); then independently verify the intended outcome (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.) before production rollout. The evidence here is the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. The required action and proof are Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order and Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.

B.

The correction is Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order. The matching proof is Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable. Both address the finding that the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

C.

Another possible combination 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. The current record instead supports Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order, verified by Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.

D.

Another potential sequence is: First verify the observed failure (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.); review and authorize the bounded correction (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.); then independently verify the intended outcome (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.) before production rollout. It has no direct link to the distinguishing evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

Question 38

A fictional Junos service-provider engineer encounters this scenario: A service provider deploys policy-based forwarding for one customer traffic class but unexpectedly sends management packets through a costly transit instead of the management path. Distinguishing evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. Which set of evidence, limited change and independent validation best justifies authorization?

  1. Approval package: observed evidence (IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.), limited correction (Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.), independently measurable result (Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.).
  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 (The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.), limited correction (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.), independently measurable result (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.).

Answer and Explanation

Correct Answer: D

A.

Another approval action is: Observed evidence (IS-IS topology output reflects the new interface cost and SPF paths differ, while link utilization counters align with the changed shortest path.), limited correction (Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.), independently measurable result (Representative destinations use the intended ring path and link utilization remains within the approved operational envelope.). The relevant evidence and acceptance are the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix and Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable, respectively.

B.

Another approval package concerns: 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 present scope must instead be justified by the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

C.

An alternative release decision 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.). It does not match the current change: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.

D.

The bounded proposal is: Observed evidence (The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.), limited correction (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.), independently measurable result (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.). The separate acceptance measure remains: Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.

Question 39

A fictional Junos service-provider engineer encounters this scenario: A service provider deploys policy-based forwarding for one customer traffic class but unexpectedly sends management packets through a costly transit instead of the management path. Distinguishing evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. 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 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.
  2. If testing fails: pause changes, preserve the differentiating evidence (BFD history indicates missed rapid control packets correlated with CPU spikes and peer timer negotiation different from the intended service design.), restore the last approved safe network state and reassess bfd timer mismatch produces frequent false failure detection.
  3. If testing fails: pause changes, preserve the differentiating 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.), restore the last approved safe network state and reassess per-flow load balancing creates asymmetric monitoring results.
  4. 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.

Answer and Explanation

Correct Answer: A

A.

A recovery option is to 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. The intended change was Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order, and acceptance must still be judged against Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.

B.

Another fallback concerns pausing changes, preserve the differentiating evidence (BFD history indicates missed rapid control packets correlated with CPU spikes and peer timer negotiation different from the intended service design.), restore the last approved safe network state and reassess bfd timer mismatch produces frequent false failure detection. The current change concerns the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

C.

Another recovery route would pause changes, preserve the differentiating 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.), restore the last approved safe network state and reassess per-flow load balancing creates asymmetric monitoring results. It does not preserve the condition of this case: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. The bounded fallback is: 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.

D.

Another option proposes: 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. Its assumptions differ from the observed failure; the appropriate recovery is: 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.

Question 40

A fictional Junos service-provider engineer encounters this scenario: A service provider deploys policy-based forwarding for one customer traffic class but unexpectedly sends management packets through a costly transit instead of the management path. Distinguishing evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. 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 (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 (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.) after independently checking (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.) after independently checking (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: B

A.

Another proposed 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 present scope must instead be justified by the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

B.

The bounded proposal is: 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 separate acceptance measure remains: Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.

C.

An alternative approval would approve only the bounded change (Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.) after independently checking (The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix and Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable, respectively.

D.

Another proposed approval would approve only the bounded change (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.) after independently checking (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.), without quietly widening the provider or customer network scope. The present scope must instead be justified by the firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.

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