Juniper JN0-364 Questions & Answers

Exercise VRRP failover and confirm virtual gateway reachability under device and link failure. That ongoing check is for VRRP virtual gateway failover; it would not reliably detect recurrence of LACP aggregation consistency. LACP aggregates only compatible negotiated member links; physical Up state alone does not prove active bundle participation.

This is a useful guard against BGP ASN and OPEN negotiation, but it is not scoped to the observed LACP aggregation consistency failure. An appropriate test would show that every intended member joins the same aggregation and distributes frames according to the approved LAG hash behavior.

This is a useful guard against GRES preserves forwarding not protocols, but it is not scoped to the observed LACP aggregation consistency failure. An appropriate test would show that every intended member joins the same aggregation and distributes frames according to the approved LAG hash behavior.

Correct the static route's reachable next hop and preference, then verify that its active route resolves to an operational forwarding interface. This addresses static route next-hop resolution, but the reported symptoms arise from aggregate route contributor. For this case, verify instead that the aggregate is active only with the expected contributors and disappears when the contributor precondition is removed.

Use a generated route with the intended contributor policy and verify the selected qualifying route supplies usable forwarding behavior. This addresses generated route qualified next hop, but the reported symptoms arise from aggregate route contributor. For this case, verify instead that the aggregate is active only with the expected contributors and disappears when the contributor precondition is removed.

Configure and verify the intended VSTP instance and per-VLAN root priorities for the affected VLANs. This addresses VSTP per-VLAN root choice, but the reported symptoms arise from aggregate route contributor. For this case, verify instead that the aggregate is active only with the expected contributors and disappears when the contributor precondition is removed.

Include tagged and untagged frame tests in trunk turn-up and template drift checks. That ongoing check is for native untagged VLAN drift; it would not reliably detect recurrence of provider Q-in-Q tagging. Q-in-Q carries an additional provider VLAN tag around customer-tagged traffic to isolate services with overlapping customer VLAN numbers.

Validate accepted tag stacks and logical-unit counters when deploying a multi-service port. That ongoing check is for flexible VLAN encapsulation alignment; it would not reliably detect recurrence of provider Q-in-Q tagging. Q-in-Q carries an additional provider VLAN tag around customer-tagged traffic to isolate services with overlapping customer VLAN numbers.

Audit network type against actual link topology during edge circuit deployment. That ongoing check is for OSPF point-to-point topology; it would not reliably detect recurrence of provider Q-in-Q tagging. Q-in-Q carries an additional provider VLAN tag around customer-tagged traffic to isolate services with overlapping customer VLAN numbers.

This is a useful guard against equal-cost forwarding flow hashing, but it is not scoped to the observed martian source address rejection failure. An appropriate test would show that the inappropriate prefix is absent or rejected while legitimate provider routes remain eligible and active. Applied here, the relevant facts are: An invalid address block enters a lab RIB after a routing-policy change and operators mistake the route for genuine service reachability. The question asks which ongoing control would most directly detect or prevent the same failure from recurring.

Test one-way BPDU loss and confirm correct port role and loop-protection state during maintenance. That ongoing check is for RSTP loop protection; it would not reliably detect recurrence of martian source address rejection. Martian-address handling protects routing tables from addresses that should not be accepted as normal routable destinations.

The control protects generated route qualified next hop. It does not establish the ongoing martian source address rejection behavior required in this network. Martian-address handling protects routing tables from addresses that should not be accepted as normal routable destinations. Applied here, the relevant facts are: An invalid address block enters a lab RIB after a routing-policy change and operators mistake the route for genuine service reachability. The question asks which ongoing control would most directly detect or prevent the same failure from recurring.

This measurement tests BGP next-hop reachability; it cannot distinguish success from failure for the observed BGP import export control condition. BGP import policy governs received routes and export policy governs outbound advertisements; changing the wrong direction cannot enforce the intended boundary.

External route advertisements show the intended relative AS-path lengths and measured inbound behavior is compared with the goal. It would validate a separate AS-path prepend inbound influence operation, not the change needed here. Confirm instead that only approved prefixes are advertised to or accepted from the intended neighbor, as confirmed by received and advertised route views.

Untagged frames map to the intended VLAN on both devices while explicitly tagged VLAN traffic remains isolated. That establishes native untagged VLAN drift rather than a repaired BGP import export control path. The reported failure still requires this evidence: only approved prefixes are advertised to or accepted from the intended neighbor, as confirmed by received and advertised route views.

Internal BGP best paths prefer the approved egress due to the intended local-preference values. That establishes BGP local preference rather than a repaired AS-path prepend inbound influence path. The reported failure still requires this evidence: external route advertisements show the intended relative AS-path lengths and measured inbound behavior is compared with the goal.

This measurement tests MSTP region consistency; it cannot distinguish success from failure for the observed AS-path prepend inbound influence condition. AS-path prepending can make a path less attractive to other ASes but does not override their local policies or guarantee inbound steering.

Only approved prefixes are advertised to or accepted from the intended neighbor, as confirmed by received and advertised route views. That establishes BGP import export control rather than a repaired AS-path prepend inbound influence path. The reported failure still requires this evidence: external route advertisements show the intended relative AS-path lengths and measured inbound behavior is compared with the goal.

Validate tag behavior, allowed VLAN membership, and connected device expectations at port provisioning. The monitored boundary differs from MAC address learning and moves, so the original weakness might reappear unnoticed. Ethernet bridges learn destination forwarding from observed source MAC addresses; unstable topology can continually invalidate learned ports.

Include tagged maximum-frame-size tests and hardware interface MTU limits in service acceptance. That ongoing check is for provider bridging MTU overhead; it would not reliably detect recurrence of MAC address learning and moves. Ethernet bridges learn destination forwarding from observed source MAC addresses; unstable topology can continually invalidate learned ports.

This is a useful guard against GRE confidentiality limitation, but it is not scoped to the observed MAC address learning and moves failure. An appropriate test would show that the MAC address stabilizes on the expected interface and unicast forwarding avoids repeated flooding.

Check downstream label advertisement, selected next hop, and label binding installation before activating the LSP path. This addresses LDP label binding completeness, but the reported symptoms arise from segment routing adjacency SID. For this case, verify instead that packet traces follow the specified adjacency rather than merely the IGP shortest path to a node SID.

Verify full label stack ordering and bottom-of-stack indication on the encapsulated service path. Its normal acceptance signal would be traces show the transport label above the service label with bottom-of-stack marked only on the last label. Here the deciding check is different: packet traces follow the specified adjacency rather than merely the IGP shortest path to a node SID.

Keep GRES for forwarding continuity and enable the appropriate supported NSB for bridging or NSR or graceful restart for routing sessions as required. That could help in a case involving GRES preserves forwarding not protocols. This failure instead depends on segment routing adjacency SID; an adjacency SID steers traffic across a specific link, whereas a prefix SID steers toward a node or prefix along shortest paths.

Packets to the remote outer endpoint resolve through an ordinary underlay route and GRE probes reach the peer. That establishes GRE endpoint underlay routing rather than a repaired GRE recursive route avoidance path. The reported failure still requires this evidence: the outer GRE endpoint resolves to an underlay interface while only intended inner destinations use the tunnel.

Maximum expected encapsulated packets cross the tunnel without fragmentation blackholes or oversized drop counters. That establishes GRE tunnel path MTU rather than a repaired GRE recursive route avoidance path. The reported failure still requires this evidence: the outer GRE endpoint resolves to an underlay interface while only intended inner destinations use the tunnel.

The shared LAN shows the intended DIS and pseudonode information, and adjacency remains stable through a controlled election. It would validate a separate IS-IS LAN designated intermediate system operation, not the change needed here. Confirm instead that the outer GRE endpoint resolves to an underlay interface while only intended inner destinations use the tunnel.

Apply a narrowly scoped ingress filter-based-forwarding match that selects the intended forwarding routing instance and validate lookup there. That could help in a case involving filter-based forwarding table selection. This failure instead depends on generated route qualified next hop; generated routes can derive their next-hop behavior from qualifying contributing routes, unlike aggregate discard summaries.

Align aggregate generation with present contributing routes and confirm the discard or reject behavior and intentional export policy. This addresses aggregate route contributor, but the reported symptoms arise from generated route qualified next hop. For this case, verify instead that the generated route becomes active when eligible contributors exist and forwards through the intended resolved contributing next hop.

The proposal changes GRE confidentiality limitation; that is not the failure isolated by the facts. It could leave generated route qualified next hop unresolved even if its own test passed. Generated routes can derive their next-hop behavior from qualifying contributing routes, unlike aggregate discard summaries.

The check is meaningful for segment routing prefix SID, but it does not prove that NSR protocol state replication was repaired. NSR uses GRES infrastructure while preserving routing protocol state on the backup Routing Engine, avoiding reliance on neighbor restart helpers.

A controlled link or peer failure causes BFD Down and timely routing reconvergence rather than waiting for long protocol timers. That establishes BFD fast failure detection rather than a repaired NSR protocol state replication path. The reported failure still requires this evidence: during a controlled primary RE loss, eligible routing adjacencies continue using state maintained by the backup RE.

Every intended member joins the same aggregation and distributes frames according to the approved LAG hash behavior. That establishes LACP aggregation consistency rather than a repaired NSR protocol state replication path. The reported failure still requires this evidence: during a controlled primary RE loss, eligible routing adjacencies continue using state maintained by the backup RE.