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

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.

Question 21

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 specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan.
  2. Bounded remedy: Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.
  3. 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.
  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: D

A.

Another proposed action is: Compare level-specific route metrics and approved traffic-engineering intent, then restore or adjust the scoped metric with a measured failover plan. That does not directly address the observed condition: 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 more targeted correction is: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.

B.

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. It targets a different dependency; the evidence here is Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

C.

Another option proposes: 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 specific correction is: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration. The deciding evidence is: 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 evidence for the issue is 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 matching step is: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration. This follows the principle that Routing instances and RIB groups require explicit route import and forwarding boundaries.

Question 22

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. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix.
  2. 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.
  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: VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design.

Answer and Explanation

Correct Answer: C

A.

This other option describes: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. The problem to explain is different: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

B.

Another proposed finding is: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link. It is not the recorded discriminator, which is Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

C.

Consider this 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 applicable explanation is: Routing instances and RIB groups require explicit route import and forwarding boundaries. The matching response is: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.

D.

Another alternative would address VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design as decisive. The actual evidence in this case is Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

Question 23

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 Junos networking principle best explains the relevant engineering decision?

  1. 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.
  2. Applicable protocol principle: GR, GRES and NSR address different aspects of routing and Routing Engine continuity and must be separately verified. Evidence for this case: Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization.
  3. 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.
  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: C

A.

The competing option 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 present evidence is: 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-relevant principle is: Routing instances and RIB groups require explicit route import and forwarding boundaries.

B.

That principle concerns another fact pattern: GR, GRES and NSR address different aspects of routing and Routing Engine continuity and must be separately verified. Evidence for this case: Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization. Here the key fact is: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

C.

Routing instances and RIB groups require explicit route import and forwarding boundaries. The recorded evidence is: 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 corresponding action is: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.

D.

This alternative invokes: 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. The governing distinction for the recorded case is Routing instances and RIB groups require explicit route import and forwarding boundaries.

Question 24

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. Intended bounded correction: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration. Which independently verifiable test best demonstrates the intended correction worked?

  1. 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.
  2. Independent verification: Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.
  3. 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.
  4. Independent verification: 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: A

A.

The expected 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. It links the scoped action to the documented condition: Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

B.

Passing that test would not establish resolution of the stated issue. The relevant proof is: The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.

C.

That result would assess another condition: Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch. The correct criterion is directly linked to the finding: 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.

Another proposed result is: Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable. It would not independently establish the required outcome: The shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.

Question 25

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 material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Overbroad route exchange between logical routing tables can break tenant isolation even without any physical link change.
  2. Meaningful operational caution: A syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement.
  3. Meaningful operational caution: Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority.
  4. Meaningful operational caution: Per-packet expectations applied to flow-hashed traffic can drive damaging changes and create packet reordering.

Answer and Explanation

Correct Answer: A

A.

The relevant boundary is: Overbroad route exchange between logical routing tables can break tenant isolation even without any physical link change. It matters when applying the specific response: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.

B.

Another emphasis concerns: A syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement. The current change is Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration; the material limitation is Overbroad route exchange between logical routing tables can break tenant isolation even without any physical link change.

C.

This limitation concerns another setting: Altering link metrics to force a DIS outcome can reroute unrelated customer traffic without changing election priority. The observed facts here make a different caution decisive: Overbroad route exchange between logical routing tables can break tenant isolation even without any physical link change.

D.

Another caution is: Per-packet expectations applied to flow-hashed traffic can drive damaging changes and create packet reordering. The key risk in this case is: Overbroad route exchange between logical routing tables can break tenant isolation even without any physical link change.

Question 26

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 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 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.
  2. 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.
  3. 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.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.

Answer and Explanation

Correct Answer: B

A.

That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: 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. The case-relevant check is: 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.

B.

The current finding is 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 pre-change check is: 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. Use it to distinguish the problem from an unrelated symptom.

C.

Another investigation would 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 does not directly establish the reported condition: 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.

That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link. The case-relevant check is: 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.

Question 27

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 controlled operational implementation sequence best protects the related provider service?

  1. 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.
  2. Controlled engineering sequence: First verify the observed failure (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.); review and authorize the bounded correction (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.); then independently verify the intended outcome (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.) before production rollout.
  3. Controlled engineering sequence: First verify the observed failure (Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.); review and authorize the bounded correction (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.); then independently verify the intended outcome (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.) before production rollout.
  4. 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.

Answer and Explanation

Correct Answer: D

A.

Another possible combination 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. The current record instead supports Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration, verified by the shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.

B.

Another potential sequence is: First verify the observed failure (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.); review and authorize the bounded correction (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.); then independently verify the intended outcome (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.) before production rollout. It has no direct link to the 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.

C.

Another action-and-check pairing is: First verify the observed failure (Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.); review and authorize the bounded correction (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.); then independently verify the intended outcome (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.) before production rollout. The evidence here is 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 required action and proof are Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration and the shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests.

D.

The correction is Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration. The matching proof is the shared resolver prefix is available to the approved instance while unauthorized customer routes are absent from both route displays and forwarding tests. Both address the finding that Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

Question 28

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 set of evidence, limited change and independent validation best justifies authorization?

  1. 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.).
  2. 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.).
  3. Approval package: observed evidence (Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.), limited correction (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.), independently measurable result (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.).
  4. Approval package: observed evidence (Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization.), limited correction (Distinguish GR, GRES and NSR supported roles, verify actual chassis and protocol prerequisites and use only approved continuity techniques for the planned event.), independently measurable result (A sandbox or maintenance test measures the agreed forwarding and neighbor behavior for each configured redundancy feature before production rollout.).

Answer and Explanation

Correct Answer: A

A.

The change-control boundary 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 evidence for this scope is Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

B.

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: Constrain the policy and RIB group to the documented destination and routing instances, then review import consequences in a candidate configuration.

C.

Another approval action is: Observed evidence (Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.), limited correction (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.), independently measurable result (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.). 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.

D.

Another approval package concerns: Observed evidence (Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization.), limited correction (Distinguish GR, GRES and NSR supported roles, verify actual chassis and protocol prerequisites and use only approved continuity techniques for the planned event.), independently measurable result (A sandbox or maintenance test measures the agreed forwarding and neighbor behavior for each configured redundancy feature before production rollout.). 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.

Question 29

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. 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 (Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.), restore the last approved safe network state and reassess ospf import policy blocks a needed external route.
  3. If testing fails: pause changes, preserve the differentiating 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.), restore the last approved safe network state and reassess route leaking across routing instances is broader than intended.
  4. 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.

Answer and Explanation

Correct Answer: C

A.

Another fallback concerns pausing 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 current change concerns Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

B.

Another recovery route would pause changes, preserve the differentiating evidence (Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term.), restore the last approved safe network state and reassess ospf import policy blocks a needed external route. It does not preserve the condition of 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 bounded fallback is: Pause changes, preserve the differentiating 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.), restore the last approved safe network state and reassess route leaking across routing instances is broader than intended.

C.

If the change fails acceptance, the bounded recovery is: Pause changes, preserve the differentiating 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.), restore the last approved safe network state and reassess route leaking across routing instances is broader than intended. The case-specific risk is Overbroad route exchange between logical routing tables can break tenant isolation even without any physical link change. The original evidence remains: 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.

Another fallback concerns pausing 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. The current change concerns Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.

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.

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