Juniper JN0-351 Enterprise Routing and Switching, Specialist Exam Practice Test

Answer : A

A RIB group is a configuration that allows a routing protocol to install routes into multiple routing tables in Junos OS. A RIB group consists of an import-rib statement, which specifies the source routing table, and an export-rib statement, which specifies the destination routing table or group.A RIB group can also include an import-policy statement, which specifies one or more policies to control which routes are imported into the destination routing table or group1.

An import policy is a policy statement that defines the criteria for accepting or rejecting routes from the source routing table. An import policy can also modify the attributes of the imported routes, such as preference, metric, or community.An import policy can be applied to a RIB group by using the import-policy statement under the [edit routing-options rib-groups] hierarchy level1.

Therefore, option A is correct, because an import policy is applied to the RIB group to control which routes are installed in the destination routing table or group. Option B is incorrect, because all routes in the source routing table are imported into the destination routing table or group, unless filtered by an import policy. Option C is incorrect, because a firewall filter is not used to install routes in the RIB groups; a firewall filter is used to filter packets based on various criteria. Option D is incorrect, because an export policy is not applied to the RIB group; an export policy is applied to a routing protocol to control which routes are advertised to other devices.

1:rib-groups | Junos OS | Juniper Networks

Answer : D

In OSPF, the Designated Router (DR) and Backup Designated Router (BDR) are elected based on the priority of the routers1.The router with the highest priority becomes the DR, and the router with the second highest priority becomes the BDR1.If there is a tie in priority, then the router with the highest Router ID is chosen1.

In this scenario, R2 has a higher priority (64) than R1 (32), so R2 will become the DR1.Since R1 has the second highest priority, it will become the BDR1. Therefore, option D is correct.

Answer : B

The configuration shown in the exhibit is an example of a routing instance of type virtual-router.A routing instance is a collection of routing tables, interfaces, and routing protocol parameters that create a separate routing domain on a Juniper device1.A virtual-router routing instance allows administrators to divide a device into multiple independent virtual routers, each with its own routing table2.

The configuration also includes a rib-group statement, which is used to import routes from one routing table to another. A rib-group consists of an import-rib statement, which specifies the source routing table, and an export-rib statement, which specifies the destination routing table.

In this case, the rib-group name is inet-to-ispi, and the import-rib statement specifies inet.0 as the source routing table. The export-rib statement specifies ispi.inet.0 as the destination routing table. This means that the routes from inet.0 will be imported into ispi.inet.0.

Therefore, the correct answer is B. The inet.0 route table will be imported into the ispi.inet.0 route table.

1:Routing Instances Overview2:Virtual Routing Instances: [rib-group (Routing Options)]

Answer : A, D

Option A suggests that the MTU is not at least 1492 bytes.This is correct because IS-IS requires a minimum MTU of 1492 bytes to establish adjacencies1.If the MTU is less than this, IS-IS adjacencies will not be established1.

Option D suggests that the lo0 interface is not included as an IS-IS interface.This is also correct because the loopback interface (lo0) is typically used as the router ID in IS-IS1.If the loopback interface is not included in IS-IS, it could prevent IS-IS adjacencies from being established1.

Therefore, options A and D are correct.

Answer : D

A keepalive OAM probe is a mechanism that can be used to monitor the state of a GRE tunnel and detect any failures in the tunnel path. A keepalive OAM probe consists of sending periodic packets from one end of the tunnel to the other and expecting a reply.If no reply is received within a specified time, the tunnel is considered down and the line protocol of the tunnel interface is changed to down1.

To configure a keepalive OAM probe for a GRE tunnel, you need to specify two parameters: the keepalive-time and the hold-time. The keepalive-time is the interval between each keepalive packet sent by the local router.The hold-time is the maximum time that the local router waits for a reply from the remote router before declaring the tunnel down2.

According to the Juniper Networks documentation, the hold-time value must be two times the keepalive-time value for a GRE tunnel2. This is because the hold-time value must account for both the round-trip time of the keepalive packet and the processing time of the remote router. If the hold-time value is too small, it may cause false positives and unnecessary tunnel flaps.

In the exhibit, the configuration shows that the keepalive-time is set to 10 seconds and the hold-time is set to 15 seconds for the gr-1/1/10.1 interface. This means that the local router will send a keepalive packet every 10 seconds and will wait for 15 seconds for a reply from the remote router. However, this hold-time value is not two times the keepalive-time value, which violates the recommended configuration. This may cause traffic drops if the remote router takes longer than 15 seconds to reply.

Therefore, option D is correct, because the hold-time value must be two times the keepalive-time value for a GRE tunnel.Option A is incorrect, because BFD is not required for GRE tunnels; BFD is another protocol that can be used to monitor tunnels, but it is not compatible with GRE keepalives3.Option B is incorrect, because the ''event link-adjacency-loss'' option is not related to GRE tunnels; it is an option that can be used to trigger an action when a link goes down4.Option C is incorrect, because LLDP does not need to be removed from the gr-1/1/10.1 interface; LLDP is a protocol that can be used to discover neighboring devices and their capabilities, but it does not interfere with GRE tunnels5.

1:Configuring Keepalive Time and Hold time for a GRE Tunnel Interface2: keepalive | Junos OS | Juniper Networks3: Configuring Bidirectional Forwarding Detection4: event link-adjacency-loss | Junos OS | Juniper Networks5: Understanding Link Layer Discovery Protocol

Answer : A

Option A is correct.The storm control feature is enabled in the factory-default configuration on EX Series switches12.On EX2200, EX3200, EX3300, EX4200, and EX6200 switches, the factory default configuration enables storm control for broadcast and unknown unicast traffic on all switch interfaces2.On EX4300 switches, the factory default configuration enables storm control on all Layer 2 switch interfaces1.

Option B is incorrect.The storm control feature does not require a special license on EX Series switches34.

Option C is incorrect. There's no information available that suggests the storm control feature is not supported on aggregate Ethernet interfaces.

Option D is incorrect.The storm control configuration applies to traffic at the ingress of an interface5, not just between the forwarding and control plane.

Answer : C

The Graceful Routing Engine Switchover (GRES) feature in Junos OS enables a router with redundant Routing Engines to continue forwarding packets, even if one Routing Engine fails1.GRES preserves interface and kernel information, ensuring that traffic is not interrupted1.However, GRES does not preserve the control plane1.

To preserve routing during a switchover, GRES must be combined with either Graceful Restart protocol extensions or Nonstop Active Routing (NSR)1.When GRES is combined with NSR, nearly 75 percent of line rate worth of traffic per Packet Forwarding Engine remains uninterrupted during GRES1.Any updates to the primary Routing Engine are replicated to the backup Routing Engine as soon as they occur1.

Therefore, when GRES is combined with NSR, routing is preserved and the new master RE does not restart rpd1.