Juniper JN0-335 Dumps Questions Answers

Juniper ATP Cloud is the threat intelligence hub for Juniper customers, identifying indicators of compromise for users and devices across the network. It provides security intelligence feeds, such as command and control (C & C) and infected hosts, that can be used to block or log malicious traffic. When you configure the C & C category with Juniper ATP Cloud, you need to specify the authentication token, the URL, and the update interval for the feeds. After you commit the configuration, the feeds are downloaded automatically from the Juniper ATP Cloud server. This may take a few minutes, depending on the network latency and the size of the feeds. Therefore, no action is required from the user, and the feeds will have non-zero objects once the download is complete. You can verify the status of the feeds by using the show services security intelligence category summary command, as shown in the exhibit.  References :

Introduction to Juniper ATP Cloud

security-intelligence (services)

Juniper ATP Cloud CLI Reference Guide

 A chassis cluster is a pair of SRX Series devices that are connected and configured to operate as a single node, providing high availability and load balancing for traffic flows 1 . A chassis cluster consists of two nodes: one primary and one secondary.  Each node can host one or more redundancy groups, which are logical entities that group the interfaces and services that need to fail over together in case of a node failure 2 . Redundancy group 0 is a special group that monitors the control plane of the cluster, such as the routing engine and the control link.  Redundancy group 0 is always active on the primary node and standby on the secondary node 3 . Therefore, option A is false.  Each chassis cluster member requires a unique node ID value, which can be either 0 or 1, to identify itself within the cluster 4 . However, the cluster ID value is the same for both nodes, and it is used to identify the cluster as a whole. Therefore, option B is false. Each chassis cluster member device can host active redundancy groups, depending on the configuration and the status of the nodes. By default, the primary node hosts all the redundancy groups, but you can configure some groups to be preempted by the secondary node if it has a higher priority or load-sharing between the nodes if they have the same priority. Therefore, option C is true. Chassis cluster member devices must be the same model, because different models have different hardware and software specifications that may not be compatible with each other in a cluster. Therefore, option D is true.  References :

Chassis Cluster User Guide for SRX Series Devices

Understanding Chassis Cluster Redundancy Groups

Understanding Redundancy Group 0

Understanding Chassis Cluster Node IDs

[Understanding Chassis Cluster Cluster IDs]

[Configuring Chassis Cluster Redundancy Group Settings]

[Chassis Cluster Feature Guide for SRX Series Devices]

A reth LAG is a redundant Ethernet interface that includes one or more physical interfaces from each node of a chassis cluster. A reth LAG provides increased bandwidth and link availability for the cluster. To configure a reth LAG, you need to follow these steps:

Configure the physical interfaces on each node as aggregated Ethernet interfaces with the same speed and duplex settings. This is required to ensure that the links can form a LAG and pass traffic correctly. You can use different cable types (such as copper or fiber-optic) for the links, but the speed must be the same.

Configure the reth interface with the redundant-ether-options statement and specify the aggregated Ethernet interfaces as child links. You should have at least two interfaces (one from each node) in the reth LAG, but you can add more for redundancy and load balancing. You can also specify the minimum-links statement to set the minimum number of child links that must be up for the reth interface to be up. The default value is one, but you can change it to a higher value if needed.

Configure the reth interface with the appropriate IP address, security zone, and other settings as needed. You can also enable LACP on the reth interface to dynamically negotiate the LAG parameters with the peer devices.

References :

[Aggregated Ethernet Interfaces in a Chassis Cluster]  1

[Chassis Cluster Redundant Ethernet Interfaces]  2

[LACP / LAG on Chassis Cluster - Interface Monitoring?]  3

[URGENT (LAG - RETH Interconnect)]  4