The correct answers are A, C, and E. Junos Space Security Director supports policy hierarchy and policy management at device, group, and global/all-devices levels. A device policy is created for a specific device and is used when a unique firewall policy must be pushed to one SRX Series Firewall. A group policy is shared across multiple devices and is used when the same policy configuration must be applied consistently to a set of managed firewalls. Juniper’s Security Director documentation explicitly describes device policy and group policy behavior, including the fact that device-specific policies are evaluated within the broader policy-ordering model.

The third correct policy type is global, often represented in Security Director workflows as all-devices/global policy behavior. Juniper Security Director product material describes granular control over global, group, and device-level firewall policies, which maps directly to the options in this question. Option B, local, is not the Security Director policy type being tested; local configuration may exist on an SRX, but it is not one of the Security Director policy hierarchy types listed here. Option D, universal, is also not a Junos Space Security Director policy type. Reference topics: Security Director, global policy, group policy, device policy, firewall policy hierarchy, centralized SRX policy management.

The correct answers are A and C. In SSL forward proxy, the SRX sits between internal clients and external SSL/TLS servers. Juniper’s SSL proxy configuration documentation shows that a forward proxy profile is created when root-ca is configured and server-certificate is not configured. This root CA is used by the SRX to generate substitute certificates for intercepted SSL sessions, so internal clients must trust the CA used by the firewall. Juniper’s procedure specifically includes generating or loading a local certificate and applying it as the root-ca in the SSL proxy profile.

Option C is also correct because forward proxy terminates the client-side SSL session and establishes a separate SSL session toward the destination server. Juniper states that the SSL proxy acts as an SSL server to the client and establishes a new SSL session to the server; from the server’s perspective, the SRX is the SSL client. Option B is wrong because forward proxy intercepts the server certificate and creates a substitute certificate; forwarding the actual server certificate unchanged is associated with reverse proxy behavior. Option D is wrong because Encrypted Traffic Insights is not the required forward-proxy mechanism here. Reference topics: SSL Proxy, SSL forward proxy, root CA, client protection, certificate interception.

The correct answers are B and C. Juniper Secure Connect uses route-based VPN connectivity, not policy-based VPN connectivity. Juniper’s Secure Connect user guide contrasts Dynamic VPN and Juniper Secure Connect and identifies Juniper Secure Connect as using route-based VPN connectivity, with a tunnel interface selected or created to bind the VPN. This is why SRX configurations for Juniper Secure Connect use an st0 tunnel interface and routing/security policy logic, rather than policy-based encryption tied directly to individual firewall policies.

Option B is also correct because Juniper Secure Connect can use a self-signed certificate. Juniper’s certificate deployment guidance states that before deploying Juniper Secure Connect, the SRX should use an appropriate certificate, which can be a signed certificate, a self-signed certificate, or a Let’s Encrypt-signed certificate. The documentation also shows generating a self-signed certificate and binding it to the SRX for Secure Connect use.

Option A is wrong because policy-based VPN describes older Dynamic VPN behavior, not Juniper Secure Connect. Option D is directly contradicted by Juniper’s certificate guidance. Reference topics: Juniper Secure Connect, route-based VPN, st0 tunnel interface, certificate deployment, self-signed certificate support.

The correct answers are A and D. Juniper documentation describes domain PC probing as a supplement to event-log reading. When a user logs in to the domain, the domain controller event log normally provides the user-to-IP mapping. If that IP address-to-username mapping is not available from the event log, JIMS initiates a domain PC probe to the endpoint to obtain the active username and domain. JIMS can also use probes to determine a device’s status after the logged-in state expires, so the operational idea is not blind periodic probing; it is used to resolve or validate identity state when normal event-log information is missing or stale.

Option D is correct because the result of identity collection is reported back to SRX Series devices. JIMS generates reports containing IP address, username, and group relationship information, keeps a list of reports communicated to SRX devices, and sends those reports so SRX devices can create authentication-table entries for identity-aware policy enforcement. Options B and C are wrong because the tested PC-probe behavior is not “every 30 seconds” or “every 60 seconds.” Those values confuse PC probing with other timers or query intervals. Reference topics: JIMS, domain PC probing, event-log identity mapping, SRX authentication table, identity-aware security policies.

The correct answers are B and D. A terminal rule is specifically designed to stop further rule evaluation. Juniper states that the IDP rule-matching algorithm normally checks traffic against all matching rules in the rulebase, but when a terminal rule matches the source, destination, zones, and application, IDP does not continue to check subsequent rules for that same traffic. Juniper also warns that traffic matching a terminal rule is not compared to later rules even if it does not match the attack object inside that terminal rule.

Option D is also correct because the Ignore Connection action stops scanning traffic for the rest of the connection if an attack match is found. Juniper defines Ignore Connection as disabling the rulebase for that specific connection after a match. Option A is wrong because a close action closes the connection by sending reset behavior, but it is not the rule-processing control mechanism being tested. Option C is a trap: the exempt rulebase is used to suppress known false positives after an IPS rule match, but the two direct mechanisms that end IDP rule processing are terminal rule matching and ignore connection. Reference topics: IDP rulebases, terminal rules, Ignore Connection action, rule-matching algorithm, false-positive exemption.

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 A and D. Juniper provides predefined IDP policy templates to simplify IDP deployment. These templates are supplied by Juniper Networks and include common templates such as client protection, server protection, DMZ services, DNS server, file server, web server, IDP default, and recommended policies. Juniper’s IDP documentation states that predefined templates are available from a secured Juniper Networks website, and the listed templates are explicitly described as being provided by Juniper Networks.

Option D is correct because these templates are not automatically present as usable policies in a factory-default SRX configuration. Juniper’s procedure says that to use predefined IDP policy templates, you download the policy templates and then install them. The CLI process includes request security idp security-package download policy-templates followed by request security idp security-package install policy-templates; committing then makes them available under the IDP policy hierarchy.

Option B is wrong because Juniper specifically says you should customize these templates for your network and recommends using a copied template so you can safely make changes. Option C is wrong because they must be downloaded and installed, so they are not simply available in the factory-default configuration. Reference topics: IDP, predefined IDP policy templates, security-package download, security-package install, active IDP policy.

The correct answers are B and D. On SRX Series Firewalls, SSL proxy is configured by creating an SSL proxy profile and then applying that profile to the relevant security policy as an application service. Juniper’s SSL proxy configuration overview lists the required workflow: configure certificates and CA profile material, configure the SSL proxy profile, create a security policy matching the traffic to be inspected, and apply the SSL proxy profile to that security policy. Juniper further states that SSL proxy is enabled as an application service within a security policy, where the policy match criteria identify the traffic and the SSL proxy profile is applied to that traffic.

Option A is wrong because enabling the SSL ALG is not the required control point for SSL proxy. SSL proxy is a decryption/inspection service applied through policy, not simply an ALG toggle. Option C is wrong because creating a separate SSL application object is not the mandatory SSL proxy configuration action. The policy can match the desired traffic and then invoke SSL proxy through then permit application-services ssl-proxy profile-name. Juniper’s example explicitly shows applying the SSL proxy profile under the security policy action.

Reference topics: SSL Proxy, SSL forward proxy, SSL proxy profiles, security policy application-services, encrypted traffic inspection.

The correct answers are B and C. Juniper ATP Cloud improves security by delivering cloud-based threat detection, malware analysis, and enforcement integration with SRX Series Firewalls. Juniper describes ATP Cloud as using shared cloud intelligence so customers benefit from new threat intelligence in near real time. It also provides zero-day threat protection, machine-learning-based malware detection, inline malware blocking, and policy actions that can stop malware, quarantine infected systems, prevent data exfiltration, and disrupt lateral movement.

Option C is also correct because Juniper ATP Cloud uses dynamic analysis, commonly called sandboxing. In this process, a suspicious file is executed in a secure environment while tools monitor its activity. Juniper further explains that ATP Cloud uses deception techniques to make the sandbox appear like a real user environment, including simulated mouse movement, keystrokes, common software packages, realistic network access, stored credentials, and vulnerable OS areas. This encourages evasive malware to execute and reveal malicious behavior.

Option A is weaker and not the best answer because logging alone is not the key ATP Cloud security-improvement mechanism being tested. Option D is wrong because ATP Cloud is a threat-prevention service, not a performance-acceleration technology. Reference topics: ATP Cloud, malware analysis, dynamic sandboxing, machine learning, threat intelligence, inline malware blocking.

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 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, 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 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.