What is causing this behavior?

Refer to the Exhibit.
— Exhibit –

— Exhibit —
Referring to the exhibit, AppTrack is only logging the session closure messages for sessions that
last 1 to 3 minutes.
What is causing this behavior?

Refer to the Exhibit.
— Exhibit –

— Exhibit —
Referring to the exhibit, AppTrack is only logging the session closure messages for sessions that
last 1 to 3 minutes.
What is causing this behavior?

A.
AppTrack is not properly configured under the [edit security application-tracking] hierarchy.

B.
AppTrack only generates session update messages.

C.
AppTrack only generates session closure messages.

D.
AppTrack generates other messages only when the update interval is surpassed.

Explanation:

Reference :http://www.juniper.net/techpubs/software/junos-security/junos-security10.2/junossecurity-swconfig-security/topic-45952.html

Show Hint

Leave a Reply 3

Your email address will not be published. Required fields are marked *

wissam

wissam

D is correct based on :

http://www.juniper.net/documentation/en_US/junos12.1/topics/concept/app-track-understanding.html

AppTrack checks whether the time since the start of the session or since the last update is greater than the update interval. If so, AppTrack updates the counts and sends an update message to the host. If a short-lived session starts and ends within the update interval, AppTrack generates a message only at session close.

That means App track sends not only session closure messages but at condition that the update interval is surpassed

Reply