— Exhibit –-
[edit security utm feature-profile content-filtering]
user@host# show
profile profileA {
block-content-type {
exe;
zip;
}
notification-options {
type message;
custom-message “Not permitted. illegal file type”;
}
}
— Exhibit –-
Refer to the Exhibit.
Your SRX Series device includes the content filtering configuration shown in the exhibit.
Assuming the content filtering profile has been properly applied, what happens when a user
attempts to send a zip file through the SRX device using FTP?
A.
The file is blocked and silently dropped.
B.
The file is blocked and a message is sent back to the user.
C.
The file is permitted and forwarded to its destination, and a message is sent back to the user.
D.
The file is permitted and forwarded to its destination.
just to add for who will here ask, I ll spend time:
The “block-content-type” configuration is for HTTP use only. That s why the FTP will be permitted
http://www.juniper.net/techpubs/en_US/junos12.1/topics/reference/configuration-statement/security-edit-block-content-type.html
Apply blocks to other available content such as exe, http-cookie, java-applet. This is for HTTP only.
http://www.juniper.net/techpubs/en_US/junos12.1/topics/concept/utm-content-filtering-overview.html
The following types of content blocking are supported only for HTTP:
Block ActiveX
Block Java applets
Block cookies
Block EXE files
Block ZIP files
You use “filename-extension” block specific extension, more detail
http://jncie-sec.exactnetworks.net/2012/11/srx-utm-content-filtering.html
d is the right answer.