JNCIS-SEC Changed JN0-336 Questions

The correct answer is D. You have too many domain controllers. The exhibit shows 15 Active Directory domain controllers. Juniper’s integrated Active Directory identity-source configuration for SRX identity-aware firewall supports a limited number of domain controllers; Juniper documentation states that an SRX Series device can configure a maximum of 10 domain controllers for Active Directory identity-source integration. Because this environment has 15 domain controllers, the direct Active Directory identity-source method exceeds the supported scale and JIMS must be used instead.

Option A is wrong because SRX devices can use Active Directory directly as an identity source; JIMS is not the only possible method. Option B is wrong because 1,500 users does not exceed the relevant identity-source scale shown here; Juniper documentation also notes probe functionality support well above this number. Option C is wrong because the issue being tested is not the Windows Server version. JIMS is designed for larger identity-aware deployments and can centralize identity collection from Active Directory, domain controllers, Exchange servers, and syslog sources, then provide identity mappings to SRX firewalls. Juniper’s JIMS datasheet shows much higher scale, including up to 100 active directories, 25 domains, and 500,000 user entries. Reference topics: Identity-Aware Security Policies, Active Directory identity source limits, JIMS scalability, domain controller scale limitations.

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