Online Access Free JN0-696 Practice Test

-- Exhibit -

-- Exhibit -
Click the Exhibit button.
Referring to the exhibit, PC-1 is unable to ping Server-1. Traffic from PC-1 to Server-1 arrives on interface fe-0/0/3 but return traffic from Server-1 to PC-1 should be sent out from interface fe0/0/2.
What would you change on SRX-1 to resolve this problem?

• A.Move both interface fe-0/0/2 and fe-0/0/3 to the same security zone.
• B.Configure a security policy to allow traffic from the DMZ zone to the untrust-1 zone.
• C.Configure a security policy to allow traffic from the DMZ zone to the untrust-2 zone.
• D.Disable TCP SYN check and TCP sequence check.

Users at a branch office report that they cannot reach an internal Web server. The users connect through a single SRX Series device to reach the Web server. A security policy has been configured on the device that allows traffic to flow between interfaces in the Trust zone.
What is causing this problem?

• A.The interface on the device that connects to the Web server is not in the Trust zone.
• B.There is a host inbound traffic configuration problem.
• C.There is an antispam configuration problem.
• D.The IPsec VPN connection between the users and the Web server is down.

-- Exhibit --
user@host> show log ibgp-trace
...
Jun 12 10:21:08 10:21:08.367627:CID-0:RT:192.168.2.1/49170->192.168.1.1/179;6> matched
filter ibgp-traffic:
Jun 12 10:21:08 10:21:08.367747:CID-0:RT:packet [64] ipid = 11792, @423f741c
Jun 12 10:21:08 10:21:08.367747:CID-0:RT:---- flow_process_pkt: (thd 2): flow_ctxt type 15,
common flag 0x0, mbuf 0x423f7200, rtbl_idx = 0
Jun 12 10:21:08 10:21:08.367747:CID-0:RT: flow process pak fast ifl 71 in_ifp ge-0/0/3.0
Jun 12 10:21:08 10:21:08.367747:CID-0:RT: ge-0/0/3.0:192.168.2.1/49170->192.168.1.1/179,
tcp, flag 2 syn
Jun 12 10:21:08 10:21:08.367747:CID-0:RT: find flow: table 0x4f161150, hash 15898(0xffff), sa 192.168.2.1, da 192.168.1.1, sp 49170, dp 179, proto 6, tok 7 Jun 12 10:21:08 10:21:08.367747:CID-0:RT: no session found, start first path. in_tunnel - 0,
from_cp_flag - 0 Jun 12 10:21:08 10:21:08.367747:CID-0:RT: flow_first_create_session Jun 12 10:21:08 10:21:08.367747:CID-0:RT:Doing DESTINATION addr route-lookup
Jun 12 10:21:08 10:21:08.367747:CID-0:RT: routed (x_dst_ip 192.168.1.1) from trust (ge-0/0/3.0 in 0) to lo0.0, Next-hop: 92.168.1.1 Jun 12 10:21:08 10:21:08.367747:CID-0:RT:flow_first_policy_search: policy search from zone
trust-> zone loopback-zone (0x0,0xc01200b3,0xb3)
Jun 12 10:21:08 10:21:08.367747:CID-0:RT: policy has timeout 900
Jun 12 10:21:08 10:21:08.367747:CID-0:RT: app 0, timeout 1800s, curr ageout 20s
Jun 12 10:21:08 10:21:08.367747:CID-0:RT: permitted by policy allow-bgp(8)
Jun 12 10:21:08 10:21:08.368250:CID-0:RT: flow_first_install_session======> 0x5394a110
Jun 12 10:21:08 10:21:08.368250:CID-0:RT:flow_first_service_lookup(): natp(0x5394a110):
app_id, 0(0).
Jun 12 10:21:08 10:21:08.368250:CID-0:RT: service lookup identified service 0.
Jun 12 10:21:08 10:21:08.368250:CID-0:RT: flow_first_final_check: in 0/3.0>, out
Jun 12 10:21:08 10:21:08.368250:CID-0:RT: existing vector list 2-49c75930.
Jun 12 10:21:08 10:21:08.368250:CID-0:RT: Session (id:137) created for first pak 2
Jun 12 10:21:08 10:21:08.368250:CID-0:RT: post addr xlation: 192.168.2.1->192.168.1.1.
Jun 12 10:21:08 10:21:08.368250:CID-0:RT:check self-traffic on lo0.0, in_tunnel 0x0
Jun 12 10:21:08 10:21:08.368250:CID-0:RT:retcode: 0xa01
Jun 12 10:21:08 10:21:08.368250:CID-0:RT:pak_for_self : proto 6, dst port 179, action 0x0
Jun 12 10:21:08 10:21:08.368250:CID-0:RT: flow_first_create_session
Jun 12 10:21:08 10:21:08.368250:CID-0:RT: flow_first_in_dst_nat: in , out A> dst_adr
192.168.1.1, sp 49170, dp 179
Jun 12 10:21:08 10:21:08.368752:CID-0:RT: chose interface lo0.0 as incoming nat if.
Jun 12 10:21:08 10:21:08.368752:CID-0:RT: packet droppeD. for self but not interested
Jun 12 10:21:08 10:21:08.368752:CID-0:RT: packet dropped, packet droppeD. for self but not
interested.
Jun 12 10:21:08 10:21:08.368752:CID-0:RT: flow find session returns error.
Jun 12 10:21:08 10:21:08.368752:CID-0:RT: ----- flow_process_pkt rc 0x7 (fp rc -1)
-- Exhibit --
Click the Exhibit button.
You are asked to troubleshoot a new IBGP peering problem on your SRX Series device. The IBGP peering is not establishing.
Referring to the outputs in the exhibit, what is causing the problem?

• A.The traffic is not being accepted by the security policy.
• B.The host inbound traffic configuration does not include the BGP parameter.
• C.NAT is translating the destination IP addresses.
• D.The loopback interface does not have the correct IP address assigned to it.

-- Exhibit --
Apr 27 19:11:09 company-fw init: low_mem_signal_processes: send signal 16 to routing
Apr 27 19:11:09 company-fw /kernel: KERNEL_MEMORY_CRITICAL: System low on free memory, notifying init (#4).
Apr 27 19:11:09 company-fw rpd[1268]: Processing low memory signal
Apr 27 19:11:09 company-fw init: low_mem_signal_processes: send signal 16 to idp-policy
Apr 27 19:11:09 company-fw idpd[1295]: Processing low memory signal
Apr 27 19:11:10 company-fw idpd[1987]: IDP_SECURITY_INSTALL_RESULT: security package install result
Done;Install aborted due to system reaching low memory condition!)
-- Exhibit -
Click the Exhibit button.
You are troubleshooting a problem where the IDP signature database update on your Junos device has failed.
Referring to the exhibit, which action will resolve this problem?

• A.Perform a manual update of the IDP signature database by issuing the command request security idp security-package download.
• B.Download the IDP signature database on the control plane without updating the data plane detector engine by issuing the command request security idp security-package install update-attack-database-only.
• C.Increase the amount of control plane memory by issuing the command set security advanced-services data-plane memory low.
• D.Clear the control plane memory used by IDP by issuing the command clear security idp status.

-- Exhibit -
[edit security utm]
user@host# show
custom-objects { url-pattern { blocklist { value [ http://badsite.com http://blocksite.com ]; } acceptlist { value http://juniper.net; } } custom-url-category { blacklist { value blocklist; } whitelist { value acceptlist; } }
}
feature-profile { web-filtering { url-whitelist whitelist; url-blacklist blacklist; type juniper-local; juniper-local {
profile web-filter {
custom-block-message "Site is not allowed";
fallback-settings {
default log-and-permit;
}
}
}
}
}
utm-policy utm1 {
web-filtering {
http-profile web-filter;
}
}
-- Exhibit --
Click the Exhibit button.
You set up Web filtering to allow employees to only access your internal website. You notice that employees are still able to reach websites outside of the blacklists.
Referring the exhibit, which parameter must be changed?

• A.You must define all sites you want to block using the mime-pattern parameter.
• B.You must define all sites you want to block using the protocol-command parameter.
• C.You must change the fallback-settings parameter to default block.
• D.You must use integrated or redirect Web filtering instead of local list filtering.