Free Juniper JN0-336 Practice Exam with Questions & Answers

The correct answers are B and C. To form an SRX chassis cluster, both devices must be assigned the same cluster ID and different node IDs. Juniper states that the cluster ID identifies the cluster, while the node ID identifies the individual node within that cluster. A valid two-node SRX chassis cluster uses node 0 on one chassis and node 1 on the other chassis. Juniper’s example shows the operational-mode commands as set chassis cluster cluster-id 1 node 0 reboot on the first device and set chassis cluster cluster-id 1 node 1 reboot on the second device.

Option A is wrong because cluster-id 0 disables clustering rather than forming a cluster. It also shows configuration-mode prompt #, while this chassis cluster node assignment is performed from operational mode. Option D is doubly wrong: cluster-id 0 disables clustering, and node 2 is invalid because SRX chassis cluster node IDs are limited to 0 and 1. The exam options omit the reboot keyword, but the only logically valid pair is still SRX1 as node 0 and SRX2 as node 1 under the same nonzero cluster ID. Reference topics: HA Clustering, chassis cluster ID, node ID, operational-mode cluster enablement.

The correct answers are A and C. To use user identity information on an SRX Series Firewall, the firewall must first be able to obtain identity mappings from an identity source or identity provider, such as Active Directory, JIMS, Aruba ClearPass, or another supported identity-aware firewall component. Juniper’s identity-aware firewall documentation states that identity parameters are used to configure security policies so authenticated users receive the correct level of access, and that firewalls can query JIMS, obtain user identity information, and then enforce security policy decisions.

Option A is required because identity-aware enforcement only happens when security policies include user identity match criteria, such as source identity, users, roles, or groups. Juniper’s source-identity policy reference states that source identities are used as match criteria in security policies, and when configured, traffic is matched against authentication-table entries before policy lookup completes. Option C is required because the SRX must be configured with an identity source/provider so it can populate or query identity mappings. Option B is not an SRX configuration task and is not generally required because users may already exist in appropriate AD groups. Option D is wrong for this question; the required SRX tasks are configuring identity integration and identity-aware policies, not adding a separate “user identity” license. Reference topics: Identity-Aware Security Policies, identity source/provider, authentication table, source-identity policy matching.

The correct answer is A. by granting access based on user roles or identities. Juniper identity-aware firewall moves enforcement beyond simple IP-address-based policy by associating traffic with authenticated users, groups, devices, and roles. Juniper states that identity parameters can be used to configure security policies so that policies provide the appropriate level of access to authenticated users. It further explains that identity helps secure access to resources based on username, roles, and groups, and that firewalls can create and enforce rules based on user identity rather than only an IP address.

This directly supports compliance because regulated environments usually require least-privilege access, auditable user-based control, and role-based authorization. Option B is wrong because identity-aware security might simplify policy operations in some cases, but network architecture simplification is not its compliance function. Option C is wrong because capacity expansion has no direct relationship to identity-based regulatory enforcement. Option D is too vague and not the mechanism being tested; confidentiality is a security goal, but identity-aware firewall enforces access decisions by mapping traffic to users and groups. Reference topics: Identity-Aware Security Policies, user identity, role-based access control, group-based policy enforcement, authentication table.

The correct answer is D. AppQoS. The requirement is not to block, permit, translate, or inspect SIP signaling; it is to prioritize VoIP traffic on a low-bandwidth branch link. Juniper Application QoS, or AppQoS, is designed exactly for this purpose. Juniper states that AppQoS provides the ability to prioritize and meter application traffic so business-critical or high-priority application traffic receives better service. It can classify traffic by application, assign forwarding classes, rewrite DSCP values, set loss priority, and apply rate limiters.

Option A, AppFW, is wrong because AppFW controls application access; it is used to permit, deny, reject, or log application traffic, not primarily to prioritize voice traffic. Option B, SIP ALG, is wrong because the SIP ALG helps inspect and handle SIP control traffic and related media pinholes, but it is not a QoS prioritization service. Option C, AppQoE, is not the correct SRX edge service being tested here. For cloud-based VoIP under a broad outbound permit rule, AppQoS is the correct service because it can identify the VoIP application and give it better treatment during congestion. Reference topics: AppQoS, application traffic control, VoIP prioritization, DSCP rewrite, forwarding class, rate limiting.

The correct answers are A and C. To log denied traffic on an SRX Series Firewall, the security policy must deny the traffic and must generate a log at session initiation. Juniper’s security policy monitoring documentation states that to view logs from denied connections, you enable logging on session-init. Juniper’s traffic-logging guidance also states that for a security policy with a deny action, traffic logs must be generated when a session starts.

Option C is required because the policy action must be deny; otherwise the traffic is not denied by that policy. Option A is required because denied traffic does not complete a normal permitted session lifecycle, so session-init is the correct logging stage for denied connection attempts. Option B, session-close, is used to log permitted sessions after teardown or conclusion; it is not the required parameter for denied traffic. Option D, count, increments policy counters but does not create traffic logs. The correct configuration concept is: match the unwanted traffic, apply then deny, and enable then log session-init. Reference topics: SRX security policies, deny action, session-init logging, traffic log generation, policy counters.

The correct answers are A and B. In an SRX chassis cluster, the cluster ID identifies the chassis cluster, and valid operational cluster IDs are nonzero values. Juniper’s chassis cluster command documentation states that the system uses the chassis cluster ID and node ID to apply the correct node-specific configuration, and the command writes the chassis cluster ID and node ID to EPROM. When the cluster ID is set to 0, clustering is disabled; therefore, the HA cluster configuration is effectively ignored because the device is no longer operating as a chassis-cluster member.

Option B is also correct because Juniper states that chassis cluster ID and node ID changes take effect only after the system is rebooted. That is why the operational command format includes the reboot behavior when setting cluster-id and node. Option C is wrong because node ID 0 is valid; it identifies node0 in the two-node cluster. Option D is wrong because SRX chassis clusters use node IDs 0 and 1 only; the 1–255 range applies to cluster IDs, not node IDs. Reference topics: HA Clustering, cluster ID, node ID, EPROM, chassis cluster enablement, node-specific configuration.

The correct answer is D. drop packet. In IDP terminology, a silent discard means the offending packet is discarded without sending reset packets or other connection-closing signals back to the endpoints. Juniper defines the Drop Packet IDP action as dropping a matching packet before it reaches its destination while not closing the connection. That is the closest and correct IDP action for “silent discard” in the listed choices.

Option A, no action, is wrong because it does not discard anything; Juniper describes No Action as taking no enforcement action, typically used when the administrator only wants logging. Option B, close client and server, is wrong because that action actively closes the session by sending TCP RST packets to both sides, which is explicitly not silent. Option C, ignore connection, is wrong because it stops further IDP scanning for the rest of the connection; it does not discard the packet. Juniper distinguishes these actions clearly: drop packet discards the offending packet, drop connection blocks the whole connection, and close actions send reset packets. Reference topics: IDP actions, drop packet, close client and server, ignore connection, silent discard behavior.

The correct answer is C. fxp0 or fxp1 on either device has an existing configuration. The exhibit shows each node reporting itself in hold state and the peer as lost under redundancy group 0. Juniper’s chassis cluster troubleshooting documentation shows this same hold/lost symptom and states that when a node is in hold, it is not ready to operate in a chassis cluster. For branch SRX devices, when cluster mode is enabled, specific physical interfaces are automatically converted into fxp0 for out-of-band management and fxp1 for the HA control link. These interfaces cannot retain normal transit or standalone interface configuration. If the ports that become fxp0 or fxp1 already have configuration, the cluster can enter the hold/lost condition shown in the exhibit.

Option A is wrong because the output does not indicate a Junos version mismatch. Option B is wrong because hardware mismatch is not the symptom being shown. Option D is too specific: a factory-default configuration can cause this problem because it may include configuration on interfaces that become fxp0/fxp1, but the exhibit does not prove specifically that node1 alone is running factory-default configuration. The tested issue is the existing configuration on the interfaces reserved for chassis-cluster management/control. Reference topics: HA Clustering, chassis cluster hold/lost state, fxp0, fxp1, branch SRX cluster initialization.

The correct answer is D. exempt. In Junos IDP, the exempt rulebase is specifically used to prevent selected traffic from triggering known false-positive detections. Juniper’s IDP documentation explains that exempt rules can be configured when an IDP policy generates false positives for a particular attack object, source, destination, or traffic pattern. The exempt rulebase lets the administrator exclude matching traffic from attack detection while still allowing the rest of the IDP policy to inspect other traffic normally.

Option A, IPS, is wrong because the IPS rulebase is the main inspection rulebase used to detect and act on attacks. It is where attack objects and actions are commonly applied, but it is not the rulebase designed to eliminate false positives. Option B, monitor, is not the correct false-positive elimination mechanism. Monitoring can help observe behavior, but it does not exempt traffic from matching an attack object. Option C, signature, is wrong because signatures are attack-detection patterns, not a rulebase type used to suppress false positives. The operational correction for noisy or irrelevant matches is to create an exempt rule for the specific trusted source, destination, or attack object. Reference topics: IDP rulebases, exempt rulebase, false-positive tuning, attack objects, IPS inspection.

The correct answer is D. maintaining a centralized authentication table. Juniper Identity Management Service, or JIMS, is used with SRX Series Firewalls to collect user-identity information from identity sources such as Microsoft Active Directory, domain controllers, and Exchange servers, then provide that identity data to SRX enforcement points. Juniper describes JIMS as storing IP address, username, and group-relationship information in its cache and generating authentication entries used for user-based or group-based access control on SRX firewalls. Juniper’s Identity-Aware Firewall documentation also states that the authentication table contains the IP address, username, and group mapping information used as the authentication source.

Option A is wrong because JIMS is not an email-encryption service. Option B is wrong because malicious-code logging belongs to security inspection features such as antivirus, IDP, or ATP workflows, not JIMS. Option C is wrong because network data encryption is handled by technologies such as IPsec VPN or SSL/TLS, not identity management. JIMS exists to centralize identity-to-IP mapping so identity-aware security policies can match users and groups instead of relying only on source IP addresses. Reference topics: Identity-Aware Security Policies, JIMS, authentication table, user-to-IP mapping, group-based policy enforcement.