You have implemented APBR on your SRX Series device and are verifying that your changes are working properly. You notice that when you start the application for the first time, it does not follow the expected path.
What are two reasons that would cause this behavior? (Choose two.)

• A. The application system cache does not have an entry for the first session.
• B. The advanced policy-based routing is applied to the ingress zone and must be moved to the egress zone.
• C. The application system cache has been disabled.
• D. The application system cache already has an entry for this application.

You are asked to configure a new SRX Series CPE device at a remote office. The device must participate in forwarding MPLS and IPsec traffic.
Which two statements are true regarding this implementation? (Choose two.)

• A. Host inbound traffic must not be processed by the flow module
• B. A firewall filter must be configured to enable packet mode forwarding
• C. Host inbound traffic must be processed by the flow module
• D. The SRX Series device can process both MPLS and IPsec with default traffic handling

Click the Exhibit button.

Referring to the exhibit, which statement is true?

• A. E-mails from the [email protected] address are allowed by the allow whitelist.
• B. E-mails from the [email protected] address are blocked by the spam list server.
• C. E-mails from the [email protected] address are marked with SPAM in the subject line by the spam block list server.
• D. E-mails from the [email protected] address are blocked by the reject blacklist.

Click the Exhibit button.

userehost# run show route
inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
0.0.0.0/0 *[Static/5] 00:05:06
> to 172.16.1.1 via ge-0/0/1.0
172.16.1.0/24 *[Direct/O] 00:05:06
> via ge-0/0/1.0
172.16.1.3/32 *[Local/0] 00:05:07
Local via ge-0/0/1.0
192.168.200.2/32 *[Local/0] 00:05:07
Reject
vr-a.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - =
Last Active, * = Both
192.168.1.0/24 *[Direct/0] 00:01:05
> via ge-0/0/2.0
192.168.1.1/32 *[Local/0] 00:01:05
Local via ge-0/0/2.0
vr-b.inet.0: 2 destinations, 2 routes (2 active, 0 holddcwn, 0 hidden)
+ = Active Route, - =
Last Active, * = Both
192.168.1.0/24 *[Direct/O] 00:01:05
> via go-0/0/3.0
192.168.1.1/32 *[Local/0] 00:01:05
Local via ge-0/0/3.0
User 1 will access Server 1 using IP address 10.2.1.1.
You need to ensure that return traffic is able to reach User 1 from Server 1.
Referring to the exhibit, which two configurations allow this communication (Choose two.)

• A. [edit security nat static]
  user@host# show
  rule-set server-nat {
  from zone untrust;
  rule 1 {
  match {
  destination-address 10.2.1.1/32;
  }
  then {
  static-nat {
  prefix {
  192.168.1.2/32;
  routing-instance vr-a;
  }
  }
  }
  }
  }
• B. [edit security nat static]
  user@host# show
  rule-set server-nat {
  from zone [ junos-host untrust ];
  rule 1 {
  match {
  destination-address 10.2.1.1/32;
  }
  then {
  static-nat {
  prefix {
  192.168.1.2/32;
  routing-instance vr-b;
  }
  }
  }
  }
  }
• C. [edit security nat static]
  user@host# show
  rule-set server-nat {
  from zone [ untrust ];
  rule 1 {
  match {
  destination-address 10.2.1.1/32;
  }
  then {
  static-nat {
  prefix {
  192.168.1.2/32;
  }
  }
  }
  }
  }
• D. [edit security nat static]
  user@host# show
  rule-set in {
  from zone untrust;
  to zone cust-a;
  rule overload {
  match {
  source-address 0.0.0.0/0;
  }
  then {
  source-nat {
  interface;
  }
  }
  }
  }

You have set up Security Director with Policy Enforcer and have configured 12 third-party feeds and a Sky ATP feed. You are also injecting 16 feeds using the available open API. You want to add another compatible feed using the available open API, but Policy Enforcer is not receiving the new feed.
What is the problem in this scenario?

• A. You have reached the maximum limit of 29 total feeds
• B. You cannot add more than 16 feeds through the available open API
• C. You cannot add more than 16 feeds with the available open API
• D. You must wait 48 hours for the feed to update