Juniper JN0-336 Security, Specialist (JNCIS-SEC) Exam Practice Test

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.

The correct answer is C. Enable connectivity between the SRX Series device and Juniper ATP Cloud. Juniper ATP Cloud cannot inspect files, receive verdicts, or apply cloud-based malware intelligence until the SRX is enrolled and has a working secure connection to the ATP Cloud service. Juniper states that SRX enrollment establishes a secure connection between the SRX Series Firewall and the Juniper ATP Cloud server, downloads and installs certificate authorities, creates local certificates, enrolls them with the cloud server, and establishes the secure cloud connection.

Option A is not the first required configuration setting because the anti-malware service depends on successful cloud onboarding and connectivity. Option B is premature because firewall/security policies can reference malware inspection only after the device is properly connected and enrolled. Option D is also later in the workflow; anti-malware policies define how files are inspected and what action is taken, but those policies are useless if the SRX cannot communicate with ATP Cloud. Juniper also notes that ATP Cloud requires both the Routing Engine and Packet Forwarding Engine to reach the Internet, and DNS must resolve the cloud URL. Reference topics: ATP Cloud onboarding, SRX enrollment, advanced anti-malware connection, secure cloud connectivity, anti-malware policy deployment.

The correct answers are B and C . A redundant Ethernet interface, or reth , is a logical interface used in an SRX chassis cluster to provide interface redundancy across node0 and node1. Juniper states that a reth interface must include matching physical Ethernet interface types and speeds on both cluster nodes. In practical terms, you cannot build one reth bundle by mixing Fast Ethernet with Gigabit Ethernet, or by mixing different speed members inside the same redundant Ethernet interface. Juniper’s chassis cluster documentation explicitly states that mixed Ethernet interface types or speeds within a single reth interface are not supported.

Option B is correct because all member interfaces must use the same media/interface type, such as Fast Ethernet with Fast Ethernet or Gigabit Ethernet with Gigabit Ethernet. Option C is correct because the child interfaces must also operate at the same speed. Option A is wrong because speed mismatch is unsupported and can prevent a child link from joining the reth bundle. Option D is wrong because different media types are not valid within the same reth interface. Reference topics: HA Clustering, redundant Ethernet interfaces, reth child interfaces, interface type and speed requirements.

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 answers are A and D. In IKEv1-based IPsec VPNs, there are two distinct negotiation phases. IKEv1 Phase 1 establishes the secure and authenticated IKE channel between peers. That means the IKE SA is built during Phase 1. Juniper describes Phase 1 as the negotiation of proposals for how to authenticate and secure the channel, including encryption algorithms, authentication algorithms, Diffie-Hellman group, and authentication method.

IKEv1 Phase 2 then uses that secure channel to negotiate the IPsec SAs that protect actual user traffic through the VPN. Juniper states that Phase 2 negotiates security associations to secure the data traversing the IPsec tunnel, and that the Phase 2 proposal includes the security protocol, such as ESP or AH, plus the selected encryption and authentication algorithms. Option B is wrong because IKEv1 SAs are not established in Phase 2; Phase 2 creates IPsec SAs. Option C is wrong because Phase 1 does not create the data-plane IPsec SA; it creates the secure IKE control channel used for Phase 2 negotiation. Reference topics: IPsec VPN, IKEv1 Phase 1, IKE SA, IKEv1 Phase 2, IPsec SA, ESP/AH proposals.

The correct answers are B and C. IDP false positives occur when legitimate traffic matches an attack signature or attack object incorrectly. One valid way to reduce false positives is to remove the problematic attack object from the IDP rule, especially when that object is not relevant to the protected application, server role, or traffic direction. Juniper defines attack objects as the items specified in IDP rules to identify malicious activity, so removing an irrelevant or noisy attack object directly reduces unwanted matches.

Option C is also correct because Juniper specifically recommends using an exempt rulebase when an IDP rule uses an attack object group containing attack objects that produce false positives or irrelevant log records. Exempt rules can exclude a specific source, destination, or source/destination pair from matching an IDP rule, preventing unnecessary alarms.

Option A is wrong because changing the action to a lower severity response does not reduce the false positive; it only changes what happens after the false match occurs. Option D is wrong because a terminal rule at the end of the rule base does not prevent earlier false-positive matches. Reference topics: IDP, attack objects, exempt rulebase, false-positive tuning, IDP rule matching.

The correct answers are A, D, and E. In IPsec VPN terminology, DES, 3DES, and AES are encryption algorithms used to provide confidentiality for protected IP traffic. Juniper’s IPsec material identifies AES, DES, and Triple DES/3DES as IPsec encryption standards, while separating them from authentication hash algorithms such as MD5, SHA-1, and SHA-2. This distinction matters heavily in JNCIS-SEC because IPsec proposals contain different cryptographic functions: encryption protects packet confidentiality, while authentication/hash algorithms validate integrity and origin.

Option B, SHA-1, is incorrect because SHA-1 is a hashing/authentication algorithm, not an encryption algorithm. It produces a message digest used for integrity checking and authentication, commonly as an HMAC variant. Option C, MD5, is also incorrect for the same reason: MD5 is a message-digest algorithm used for authentication/integrity, not for encrypting payload data. AES is the modern preferred encryption family because it is cryptographically stronger than DES and 3DES at comparable key strengths, while DES and 3DES remain historically recognized IPsec encryption algorithms. Reference topics: IPsec VPN, IPsec proposals, encryption algorithms, authentication algorithms, DES, 3DES, AES, SHA, and MD5.

The correct answer is A. the action taken is defined in the IDP policy that includes this attack object. The exhibit defines a custom attack object named BGP-DEFEND under the security idp custom-attack hierarchy. The custom object includes metadata such as recommended-action drop, severity critical, and signature match conditions such as BGP update AS-path context and pattern 65501. However, an attack object by itself does not determine the final enforcement behavior. The attack object defines what to match; the IDP policy rule that references the object defines what action to take when that match occurs. Juniper describes attack objects as objects used inside IDP rules to identify malicious activity, while IDP rules include rule actions such as drop-packet, drop-connection, close-client, close-server, recommended, and others.

Option B is wrong because the firewall security policy enables IDP inspection by applying an IDP policy, but the IDP action is not selected directly by the normal security policy. Options C and D are too absolute. Even though the custom object shows recommended-action drop, that is only used if the IDP rule action invokes recommended behavior. Without seeing the IDP policy rule action, you cannot conclude reject or drop. Reference topics: IDP custom attack objects, IDP policy rule actions, recommended action, signature-based attack matching.

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 answers are B and C. Juniper IDP uses attack objects as match conditions inside IDP policy rules. Juniper states that IDP attack objects represent known and unknown attacks and that the predefined attack object database is periodically updated by Juniper Networks. The main IDP attack object types include signature attack objects, protocol anomaly attack objects, and compound attack objects.

Option C is correct because signature attack objects detect known attacks using stateful attack signatures. Juniper defines a signature as a pattern that exists within a specific section of an attack and includes protocol, service, direction, flow, and context information to reduce false positives.

Option B is correct because protocol anomaly attack objects detect abnormal protocol behavior. Juniper explains that protocol anomaly objects identify unusual or ambiguous traffic that violates protocol specifications, RFCs, or common RFC extensions.

Option A is wrong because “statistic-based” is not one of the IDP attack object database types being tested here. Option D is wrong because “vector-based” is not a Juniper IDP attack object type. Reference topics: IDP, attack object database, signature-based attack objects, protocol anomaly attack objects, predefined attack objects.

The correct answers are C and D. Static attack object groups are manually defined groups. Juniper states that custom attack groups are static in nature because the attacks are explicitly specified in the group; therefore, those attack groups do not change when the security database is updated. This is the key difference between static groups and dynamic groups. Dynamic groups use matching criteria and can automatically update membership when the signature database changes, but static groups do not behave that way.

Option C is correct because updating the IPS/IDP signature database does not automatically add or remove members from a static attack group. Option D is correct because the administrator must explicitly add the desired attack objects to the custom static group. Option A describes dynamic matching behavior, not static group behavior. Option B is also dynamic-group behavior; Juniper Security Director documentation says dynamic group membership is automatically updated during signature updates based on the group’s matching criteria. Static groups are intentionally deterministic: they include only the attacks manually selected by the administrator. Reference topics: IDP attack objects, static attack groups, custom attack groups, dynamic attack groups, IPS signature database updates.

The correct answers are A and B. The exhibit shows show chassis cluster statistics. Under Control link statistics, Control link 0 has heartbeat packets sent and received, with heartbeat packet errors: 0. That is the clearest indication that the control link is operating normally. Juniper describes chassis-cluster control-plane verification as checking control-link heartbeat packets sent and received, along with heartbeat errors. If both send and receive counters are incrementing and errors are zero, the control link is functioning.

Option A is also correct because under Fabric link statistics, Child link 0 shows probes sent and probes received. Juniper uses fabric-link probe counters to verify fabric-link operation; nonzero sent and received probe counters indicate that the link is participating in fabric monitoring. Option C is not the safest conclusion from this exhibit alone. Child link 1 shows zero probes sent and received, but the output does not prove that a second fabric child link is configured and failing; it could simply be unused or not configured in this deployment. Option D is directly contradicted by the healthy heartbeat counters. Reference topics: HA Clustering, chassis cluster statistics, control-link heartbeat, fabric-link probes, cluster health verification.

The correct answer is C. device policy rules. In Junos Space Security Director, a firewall rule that must apply uniquely to one SRX Series device belongs in the device-specific policy layer, not in global or group-level policy. Juniper’s Security Director documentation states that a device can have a device-specific policy and can also be part of multiple group policies; the rule processing order places policies applied before device-specific policies first, then device-specific policies, then policies applied after device-specific policies. Juniper also explains that rules applied before device-specific policies take priority and cannot be overridden, while rules applied after device-specific policies can be overridden by adding a rule in the device-specific policy.

Option A is wrong because all-devices prerules are global mandatory rules applied before device-specific policy, not unique device exceptions. Option B is wrong because group policy prerules apply to a group of devices, not one specific SRX. Option D is wrong because all-devices postrules are still global policy rules, although they can be overridden. For a unique policy requirement on one SRX device, device policy rules are the precise Security Director construct. Reference topics: Security Director, firewall policies, device-specific policies, policy rule precedence, global/group/device rule hierarchy.

The correct answer is B. by using AppID results. Junos SSL proxy does not identify SSL/TLS sessions by assuming that encrypted traffic always uses TCP/443. That would be technically weak because SSL/TLS can run on nonstandard ports, and non-SSL applications can also use common HTTPS ports. Juniper’s SSL proxy documentation explains that SSL proxy works with application security services and that AppID is used in the encrypted-traffic inspection workflow. In earlier wording from Juniper AppSecure material, SSL proxy uses application identification services to determine whether a session is SSL encrypted; in current Junos documentation, SSL proxy and AppID are tightly linked so encrypted sessions can be identified, decrypted, inspected, and then re-encrypted for enforcement.

Option A is wrong because the URL is inside the HTTP payload, and in HTTPS much of the meaningful HTTP content is encrypted before SSL proxy inspection occurs. Option C is wrong because destination port is only a rough hint, not a reliable detection method. Option D is wrong because certificates are used in the SSL/TLS handshake and proxy trust model, but the service’s traffic classification relies on AppID results, not merely reading the server certificate. Reference topics: SSL Proxy, AppID, encrypted session detection, SSL/TLS inspection, application security services.

The correct answers are A and D. A mobile command center using a 5G ISP behind CGNAT is operating behind dynamic address translation. For IPsec to work reliably through NAT, the SRX must support NAT Traversal, which encapsulates IKE and ESP traffic in UDP/4500 after NAT is detected. Juniper states that NAT-T is used when NAT devices exist in the datapath and that NAT keepalives are required because NAT devices age out UDP translations. Juniper’s Security Director VPN workflow also specifically says to enable NAT-T when the dynamic endpoint is behind a NAT device.

DPD is also required because mobile and carrier-grade NAT connections can disappear, roam, or become stale without a clean tunnel teardown. Juniper defines Dead Peer Detection as the method used by IPsec peers to verify whether the remote peer is still present and responsive by sending encrypted IKE notification payloads and waiting for acknowledgements. Option B is not the best answer because IKEv1 aggressive mode is weaker and does not provide identity protection; Juniper also notes that aggressive mode applies only to IKEv1. Option C is invalid because IKEv2 aggressive mode does not exist. Reference topics: IPsec VPN, NAT-T, CGNAT, dynamic endpoints, DPD, IKE peer availability.

The correct answers are A, C, and E. During Security Director device discovery, Junos Space first finds and connects to the managed device, then synchronizes the device inventory and configuration into the Junos Space database. Juniper’s Security Director documentation states that discovery uses a discovery profile containing target information, authentication credentials, probes, and SSH fingerprints. During discovery, Junos Space connects to the physical device and retrieves the running configuration and status information. It also states that Junos Space uses SSH, with optional ping and SNMP, to discover network devices.

Option B is wrong because device discovery is not a reboot operation. Rebooting would be disruptive and is not part of onboarding a managed SRX into Security Director. Option D is wrong because discovery does not automatically inject a local superuser into the SRX configuration. Security Director authenticates using credentials supplied in the discovery profile; it does not create privileged local accounts as a discovery action. The tested workflow is management-plane discovery: connect, authenticate, retrieve inventory/status, and import configuration state. Reference topics: Security Director, device discovery, discovery profiles, SSH, running configuration import, device status synchronization.

The correct answers are B and D. In VPN cryptography, hashing is used for authentication and integrity checking, not confidentiality. Juniper’s IPsec documentation describes MD5 as producing a 128-bit hash, also called a digital signature or message digest, from a message of arbitrary length. It also describes SHA as producing a 160-bit hash from a message of arbitrary length. That directly supports option B because a hash function takes variable-length input and produces a fixed-size digest.

Option D is also correct because Juniper states that the resulting hash is used like a fingerprint of the input to verify content and source authenticity and integrity. Juniper’s IPsec overview further explains that Junos compares the calculated message digest against the expected digest to verify that the message has not been tampered with.

Option A is wrong because hashing is not compression; it is one-way digest generation. Option C is wrong because encryption protects confidentiality, while hashing validates integrity and authenticity. In IPsec, algorithms such as AES, DES, and 3DES provide encryption, while MD5, SHA-1, and SHA-2 provide hashing/HMAC-based authentication. Reference topics: IPsec VPN, hashing, HMAC, MD5, SHA, message digest, data integrity.

The correct answers are C and D. The exhibit shows ESP encrypted bytes = 0, ESP decrypted bytes = 0, encrypted packets = 0, and decrypted packets = 0. That means no traffic is successfully passing through the IPsec tunnel. Juniper’s show security ipsec statistics command displays ESP encrypted/decrypted packet and byte counters, so zero values on these counters indicate that the tunnel is not successfully carrying protected ESP traffic.

Option C is also correct because the output shows ESP authentication failures and ESP decryption failures. Since ESP is the IPsec protocol responsible for encrypted payload handling, failures in ESP authentication/decryption point to an ESP/IPsec Phase 2 mismatch or incorrect configuration, such as mismatched authentication algorithm, encryption algorithm, keys, proposal parameters, or incompatible negotiated SA settings. Juniper’s IPsec overview explains that Phase 2 negotiates the IPsec SA used to authenticate traffic flowing through the tunnel, so ESP-related failures belong to the IPsec/ESP configuration path rather than AH.

Option A is wrong because the AH counters and AH authentication failures are zero; the evidence is not pointing to AH. Option B is unsupported because the output does not show peer reboot behavior. Reference topics: IPsec VPN, ESP statistics, Phase 2/IPsec SA negotiation, ESP authentication failures, ESP decryption failures.

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 B. ip-notify. When administrators want visibility without enforcement impact, ip-notify is the correct IP action. Juniper Security Director documentation defines IP Notify as an IP action that does not take any action against future traffic but logs the event. That is exactly the requirement in the question: traffic matching the IDP condition must not be blocked, closed, or rate-limited until administrators have reviewed the events and decided whether enforcement is appropriate.

Option A, ip-block, is wrong because it blocks future packets matching the IP action rule. That would immediately impact traffic. Option C, ip-connection-rate-limit, is wrong because it limits the connection rate and therefore changes traffic behavior before administrators complete evaluation. Option D, ip-close, is also wrong because it closes matching future sessions by sending reset packets to the client and server, which is disruptive. In a safe evaluation or tuning phase, the proper approach is to log and observe first, then move to stronger actions such as block, close, or rate-limit only after the detected condition has been validated. Reference topics: IDP IP actions, ip-notify, event logging, non-disruptive evaluation mode, IDP policy tuning.