An administrator has onboarded a new SRX device and applied a configuration template. The device status shows 'In Sync', but the administrator notices that the device's security policy is not being enforced. The device is reachable and the configuration appears correct. What is the most likely cause of the policy not being enforced?

The device's root password was changed after onboarding.

The device's software version does not support the policy type.

The device's management IP is not reachable from the Security Director server.

The security policy is not attached to the correct zone or interface.

A security administrator is onboarding a new SRX device. The device is reachable via SSH, and the administrator has the correct credentials. However, when adding the device in Security Director, the 'Add Device' wizard fails with an authentication error. What is the most likely cause?

The device's software version is not supported by Security Director.

The device's hostname is not resolvable via DNS.

The device's SSH service is configured to use a non-default port.

The device's management interface is not configured with an IP address.

What does a 'configuration sync' status of 'In Sync' indicate for an onboarded device?

The device's firmware is up to date

The device's running configuration matches the configuration expected by Security Director

The device is connected to the internet

What is the role of the connection parameters (e.g., protocol and port) when adding a device to Security Director?

They set the device's administrative password

They define how Security Director communicates with the device

They specify the device's physical location in the network

They determine the device's routing table

What is the purpose of applying a configuration template to an onboarded device in Security Director?

To change the device's management IP address

To generate a performance report for the device

To standardize settings across multiple devices

To delete the device's existing configuration

Juniper NetworksCertified Specialist, Security (JNCIS-SEC)

Domain 7Objective 2

Onboarding Devices JN0-336 Practice Questions (Page 1)

Part of the Security Director domain, which makes up ~8% of our current practice bank. Juniper Networks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~3–5 in this domain), expect 1–2 from this objective — we provide 18 practice questions to prepare you well beyond it. (estimate)

18questions here

4free pages

4concepts

Questions 1–5

1expert · hard
An administrator has onboarded a new SRX device and applied a configuration template. The device status shows 'In Sync', but the administrator notices that the device's security policy is not being enforced. The device is reachable and the configuration appears correct. What is the most likely cause of the policy not being enforced?
Select an answer first
2application · medium
A security administrator is onboarding a new SRX device. The device is reachable via SSH, and the administrator has the correct credentials. However, when adding the device in Security Director, the 'Add Device' wizard fails with an authentication error. What is the most likely cause?
Select an answer first
3foundation · easy
What does a 'configuration sync' status of 'In Sync' indicate for an onboarded device?
Select an answer first
4foundation · easy
What is the role of the connection parameters (e.g., protocol and port) when adding a device to Security Director?
Select an answer first
5foundation · easy
What is the purpose of applying a configuration template to an onboarded device in Security Director?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to JN0-336

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Juniper Networks. “JN0-336” is a trademark of its owner, used for identification only.