Download Juniper Networks Certified Support Professional Security (JNCSP-SEC).JN0-696.Train4Sure.2018-06-21.36q.vcex

Vendor: Juniper
Exam Code: JN0-696
Exam Name: Juniper Networks Certified Support Professional Security (JNCSP-SEC)
Date: Jun 21, 2018
File Size: 2 MB
Download Exam

How to open VCEX files?

Files with VCEX extension can be opened by ProfExam Simulator.

Download
ProfExam Simulator

Purchase
Coupon: EXAMFILESCOM

Discount: 20%

ProfExam Simulator ProfExam Simulator ProfExam Simulator ProfExam Simulator ProfExam Simulator

Demo Questions

Question 1
-- Exhibit -- 
user@host> show security flow session interface ge-0/0/10.0 
Session ID. 29, Policy name: to-infrastructure/4, Timeout: 1250, Valid
Resource information : FTP ALG, 1, 0
  In: 10.1.1.213/61892 --> 10.2.2.20/21;tcp, If: ge-0/0/8.0, Pkts: 25, Bytes: 1242
  Out: 10.2.2.20/21 --> 10.1.1.213/61892;tcp, If: ge-0/0/10.0, Pkts: 18, Bytes: 1278
Total sessions: 1
user@host> show interfaces ge-0/0/10 | match zone 
    Security: Zone: infrastructure
user@host> show interfaces ge-0/0/8 | match zone 
    Security: Zone: finance
user@host> show configuration security policies from-zone infrastructure to-zone finance 
user@host> show log flow-traceoptions 
Jun 13 14:44:01 14:44:01.059151:CID-0:RT:SPU received an event,type 112, common:3
Jun 13 14:44:01 14:44:01.059151:CID-0:RT:Rcv packet with rtbl idx 0, cos 0
Jun 13 14:44:01 14:44:01.059151:CID-0:RT:SPU processing spu_flushed_pak, flag: 0x2, mbuf:0x423f6100
Jun 13 14:44:01 14:44:01.060343:CID-0:RT:10.2.2.20/20->10.1.1.213/64313;6> matched filter filter2:
Jun 13 14:44:01 14:44:01.060473:CID-0:RT:packet [64] ipid = 1614, @423fd19c
Jun 13 14:44:01 14:44:01.060473:CID-0:RT:---- flow_process_pkt: (thd 3): flow_ctxt type 15, common flag 0x0, mbuf 0x423fcf80, rtbl_idx = 0
Jun 13 14:44:01 14:44:01.060473:CID-0:RT: flow process pak fast ifl 71 in_ifp ge-0/0/10.0
Jun 13 14:44:01 14:44:01.060473:CID-0:RT:  ge-0/0/10.0:10.2.2.20/20->10.1.1.213/64313, tcp, flag 2 syn
Jun 13 14:44:01 14:44:01.060473:CID-0:RT: find flow: table 0x49175b08, hash 34391(0xffff), sa 10.2.2.20, da 10.1.1.213, sp 20, dp 64313, proto 6, tok 8
Jun 13 14:44:01 14:44:01.060473:CID-0:RT:  no session found, start first path. in_tunnel - 0, from_cp_flag - 0
Jun 13 14:44:01 14:44:01.060473:CID-0:RT:  flow_first_create_session
Jun 13 14:44:01 14:44:01.060473:CID-0:RT:-jsf : preset sess plugin info for session 31
Jun 13 14:44:01 14:44:01.060473:CID-0:RT: Allocating plugin info block for plugin(21)
Jun 13 14:44:01 14:44:01.060473:CID-0:RT:[JSF] set ext handle 0x46389be8 for plugin 21 on session 31
Jun 13 14:44:01 14:44:01.060473:CID-0:RT:asl_usp_get_l3_out_ifp_out_tunnel ASL IPV4 out_ifp = ge-0/0/8.0 for dst:10.1.1.213 in vr_id:0
Jun 13 14:44:01 14:44:01.060473:CID-0:RT:SPU invalid session id 00000000
Jun 13 14:44:01 14:44:01.060473:CID-0:RT: jsf drop pak pid 21, jbuf 0x4fcd7038,  release hold 0, sess_id 0
Jun 13 14:44:01 14:44:01.060761:CID-0:RT: After jsf gate hit. sid 0xfb39, pid 0, cookie 0x1f, jbuf 0x15. rc = 1
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:RM populated xlate info for nsp2: 10.1.1.213/64313->10.2.2.20/20out_ifp = ge-0/0/8.0, out_tunnel = 0x0
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:  flow_first_in_dst_nat: in  0/10.0>, out  0/8.0> dst_adr 10.1.1.213, sp 20, dp 64313
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:  flow_first_in_dst_nat: bypassed by RM
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:  flow_first_rule_dst_xlate: bypassed by RM
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:  flow_first_routing: bypassed by RM
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:  flow_first_policy_search: bypassed by RM
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:  flow_first_reverse_mip: bypassed by RM
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:  flow_first_src_xlate: bypassed by RM
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:  flow_first_get_out_ifp: bypassed by RM
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:is_loop_pak: No loop: on ifp: ge-0/0/8.0, addr: 10.1.1.213, rtt_idx:0
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:[JSF]Normal interest check. regd plugins 18, enabled impl mask 0x0
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:-jsf int check: plugin id  2, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:-jsf int check: plugin id  3, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:-jsf int check: plugin id  5, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060761:CID-0:RT:-jsf int check: plugin id  6, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:-jsf int check: plugin id  7, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:-jsf int check: plugin id  8, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:-jsf int check: plugin id 14, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:+++++++++++jsf_test_plugin_data_evh: 3
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:-jsf int check: plugin id 15, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:-jsf int check: plugin id 21, svc_req 0x0, impl mask 0x0. rc 3
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:-jsf int check: plugin id 22, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:-jsf int check: plugin id 25, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:-jsf int check: plugin id 26, svc_req 0x0, impl mask 0x0. rc 2
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:-jsf int check: plugin id 27, svc_req 0x0, impl mask 0x0. rc 4
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:[JSF]Plugins(0x0, count 0) enabled for session = 4294967296, impli mask(0x0), post_nat cnt 31 svc req(0x0)
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:[JSF]c2s order list:
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:               21
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:[JSF]s2c order list:
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:               21
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:  service lookup identified service 79.
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:  flow_first_final_check: in  0/10.0>, out  0/8.0>
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:flow_first_complete_session, pak_ptr: 0x48ae5ba0, nsp: 0x4c38e248, in_tunnel: 0x0
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:construct v4 vector for nsp2
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:  existing vector list 82-454e5c90.
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:  Session (id:31) created for first pak 82
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:  flow_first_install_session======> 0x4c38e248
Jun 13 14:44:01 14:44:01.060975:CID-0:RT: nsp 0x4c38e248, nsp2 0x4c38e2c8
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:  make_nsp_ready_no_resolve()
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:  route lookup: dest-ip 10.2.2.20 orig ifp ge-0/0/10.0 output_ifp ge-0/0/10.0 orig-zone 8 out-zone 8 vsd 0
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:  route to 10.2.2.20
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:Doing jsf sess create notify
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:flow_delete_gate: invoked for gate 0x4c077c24 [id 1000003]
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:gate_start_ageout: ageout started for gate 0x4c077c24
Jun 13 14:44:01 14:44:01.060975:CID-0:RT: jsf sess id ignore. sess 31, pid 21, dir 1, st_buf 0x0.
Jun 13 14:44:01 14:44:01.060975:CID-0:RT: jsf sess id ignore. sess 31, pid 21, dir 2, st_buf 0x0.
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:All plugins have ignored session :31
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:  existing vector list 2-454ecbd0.
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:  existing vector list 2-454ecbd0.
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:-jsf create notify: plugin id 21. rc 3
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:flow_do_jsf_notify_session_creation(): natp(0x4c38e248): 0 SHORT_CIRCUITED. 0x00000000.
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:no need update ha
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:Installing c2s NP session wing
Jun 13 14:44:01 14:44:01.060975:CID-0:RT:Installing s2c NP session wing
Jun 13 14:44:01 14:44:01.061475:CID-0:RT:  flow got session.
Jun 13 14:44:01 14:44:01.061475:CID-0:RT:  flow session id 31
Jun 13 14:44:01 14:44:01.061475:CID-0:RT: vector bits 0x2 vector 0x454ecbd0
Jun 13 14:44:01 14:44:01.061475:CID-0:RT:  tcp flags 0x2, flag 0x2
Jun 13 14:44:01 14:44:01.061475:CID-0:RT:  Got syn, 10.2.2.20(20)->10.1.1.213(64313), nspflag 0x1021, 0x20
Jun 13 14:44:01 14:44:01.061475:CID-0:RT:mbuf 0x423fcf80, exit nh 0xa0010
Jun 13 14:44:01 14:44:01.061475:CID-0:RT: ----- flow_process_pkt rc 0x0 (fp rc 0)
-- Exhibit -- 
While troubleshooting a device, you see that it is permitting packets for which it appears there is no policy. 
Using the information in the exhibit, what is causing this behavior?
  1. It is permitted due to an ALG.
  2. It is permitted due to a stale policy.
  3. It is permitted due to a global policy.
  4. It is permitted due to a default permit policy.
Correct answer: A
Question 2
-- Exhibit -- 
user@host> show configuration security policies from-zone engineering to-zone hr 
policy new-policy { 
    match { 
        source-address any; 
        destination-address server1; 
        application hr-data-feed; 
    } 
    then { 
        permit; 
    } 
} 
policy old-policy { 
    match { 
        source-address pc1; 
        destination-address server1; 
        application any; 
    } 
    then { 
        deny; 
        log { 
            session-init; 
        } 
    } 
} 
user@host> show configuration security policies global 
user@host> show configuration security address-book | match server1 | display set 
set security address-book book2 address server1 172.19.55.20/32 
set security address-book book3 address server1 172.20.11.18/32 
user@host> show configuration security address-book | match pc1 | display set 
set security address-book book1 address pc1 172.18.21.213/32 
user@host> show configuration applications 
application hr-data-feed { 
    protocol tcp; 
    destination-port 38888; 
} 
user@host> run show log flow-traceoptions | no-more 
Jun 13 15:54:09 host clear-log[2503]: logfile cleared
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:172.18.21.213/38362->172.19.55.20/38888;17> matched filter filter1:
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:packet [40] ipid = 38364, @423e421c
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:---- flow_process_pkt: (thd 3): flow_ctxt type 15, common flag 0x0, mbuf 0x423e4000, rtbl_idx = 0
Jun 13 15:54:10 15:54:10.611915:CID-0:RT: flow process pak fast ifl 70 in_ifp ge-0/0/8.0
Jun 13 15:54:10 15:54:10.611915:CID-0:RT: find flow: table 0x49175b08, hash 9077(0xffff), sa 172.18.21.213, da 172.19.55.20, sp 38362, dp 38888, proto 17, tok 10
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:  flow_first_create_session
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:  flow_first_in_dst_nat: in  0/8.0>, out  A> dst_adr 172.19.55.20, sp 38362, dp 38888
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:  chose interface ge-0/0/8.0 as incoming nat if.
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:flow_first_rule_dst_xlate: DST no-xlate: 0.0.0.0(0) to 172.19.55.20(38888)
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:flow_first_routing: vr_id 0, call flow_route_lookup(): src_ip 172.18.21.213, x_dst_ip 172.19.55.20, in ifp ge-0/0/8.0, out ifp N/A sp 38362, dp 38888, ip_proto 17, tos 0
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:Doing DESTINATION addr route-lookup
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:  routed (x_dst_ip 172.19.55.20) from engineering (ge-0/0/8.0 in 0) to ge-0/0/10.0, Next-hop: 172.19.55.20
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:flow_first_policy_search: policy search from zone engineering-> zone hr (0x0,0x95da97e8,0x97e8)
Jun 13 15:54:10 15:54:10.611915:CID-0:RT:  app 0, timeout 60s, curr ageout 60s
Jun 13 15:54:10 15:54:10.611915:CID-0:RT: Error : get sess plugin info 0x4c390388
Jun 13 15:54:10 15:54:10.611915:CID-0:RT: Error : get sess plugin info 0x4c390388
Jun 13 15:54:10 15:54:10.612416:CID-0:RT:  packet dropped, denied by policy
Jun 13 15:54:10 15:54:10.612416:CID-0:RT:  denied by policy old-policy(6), dropping pkt
Jun 13 15:54:10 15:54:10.612416:CID-0:RT:  packet dropped,  policy deny.
Jun 13 15:54:10 15:54:10.612416:CID-0:RT:  flow didn't create session, code=-1.
Jun 13 15:54:10 15:54:10.612416:CID-0:RT: ----- flow_process_pkt rc 0x7 (fp rc -1)
-- Exhibit -- 
A user added the new-policy policy to permit traffic. However, they report that the traffic is still not permitted by the device. 
Using the information in the exhibit, why is the device denying the traffic?
  1. The traffic does not match the address book entry used in new-policy.
  2. The traffic does not match the application specified in new-policy.
  3. The traffic is being denied by the more specific old-policy prior to the device evaluating new-policy.
  4. The traffic is the first packet in a flow, but is not a SYN.
Correct answer: B
Explanation:
The application is TCP 38888 and the incoming packet is UDP 38888.
The application is TCP 38888 and the incoming packet is UDP 38888.
Question 3
-- Exhibit -- 
user@host> show security flow session 
... 
Session ID. 41, Policy name: allow/5, Timeout: 20, Valid
  In: 172.168.66.143/43886 --> 192.168.100.1/5000;tcp, If: ge-0/0/1.0, Pkts: 1, Bytes: 60
  Out: 10.100.1.100/5555 --> 172.168.66.143/43886;tcp, If: ge-0/0/2.0, Pkts: 0, Bytes: 0
user@host> show configuration 
... 
security { 
    nat { 
        destination { 
            pool server { 
                address 10.100.1.100/32 port 5555; 
            } 
            rule-set rule1 { 
                from zone UNTRUST; 
                rule 1 { 
                    match { 
                        destination-address 192.168.100.1/32; 
                        destination-port 5000; 
                    } 
                    then { 
                        destination-nat pool server; 
                    } 
                } 
            } 
        } 
        proxy-arp { 
            interface ge-0/0/1.0 { 
                address { 
                    192.168.100.1/32; 
                } 
            } 
        } 
    } 
    policies { 
        from-zone UNTRUST to-zone TRUST { 
            policy allow { 
                match { 
                    source-address any; 
                    destination-address any; 
                    application [ junos-ping tcp-5000 ]; 
                } 
                then { 
                    permit; 
                } 
            } 
        } 
    } 
    zones { 
        security-zone TRUST { 
            interfaces { 
                ge-0/0/2.0 { 
                    host-inbound-traffic { 
                        protocols { 
                            all; 
                        } 
                    } 
                } 
            } 
        } 
        security-zone UNTRUST { 
            interfaces { 
                ge-0/0/1.0 { 
                    host-inbound-traffic { 
                        system-services { 
                            ping; 
                        } 
                    } 
                } 
            } 
        } 
    } 
} 
applications { 
    application tcp-5000 { 
        protocol tcp; 
        destination-port 5000; 
    } 
} 
-- Exhibit -- 
Your customer is attempting to reach your new server that should be accessible publicly using 192.168.100.100 on TCP port 5000, and internally using 10.100.100.1 on TCP port 5555. You notice a session forms when they attempt to access the server, but they are unable to reach the server. 
Referring to the exhibit, what will resolve this problem?
  1. There must be a TRUST-to-UNTRUST security policy to allow return traffic.
  2. The NAT pool server address must be changed to 10.100.100.1/32.
  3. The NAT pool server port must be changed to 5000.
  4. The NAT rule set rule1 must match on address 172.168.66.143.
Correct answer: B
Question 4
-- 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 -- 
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?
  1. The traffic is not being accepted by the security policy.
  2. NAT is translating the destination IP addresses.
  3. The loopback interface does not have the correct IP address assigned to it.
  4. The host inbound traffic configuration does not include the BGP parameter.
Correct answer: D
Question 5
-- Exhibit -- 
user@host> show configuration 
... 
security { 
    nat { 
        destination { 
            pool server { 
                address 10.100.100.1/32 port 5555; 
            } 
            rule-set rule1 { 
                from zone UNTRUST; 
                rule 1 { 
                    match { 
                        destination-address 192.168.100.1/32; 
                        destination-port 5000; 
                    } 
                    then { 
                        destination-nat pool server; 
                    } 
                } 
            } 
        } 
        proxy-arp { 
            interface ge-0/0/1.0 { 
                address { 
                    192.168.100.1/32; 
                } 
            } 
        } 
    } 
    policies { 
        from-zone UNTRUST to-zone TRUST { 
            policy allow { 
                match { 
                    source-address any; 
                    destination-address any; 
                    application [ junos-ping tcp-5000 ]; 
                } 
                then { 
                    permit; 
                } 
            } 
        } 
    } 
    zones { 
        security-zone TRUST { 
            interfaces { 
                ge-0/0/2.0 { 
                    host-inbound-traffic { 
                        protocols { 
                            all; 
                        } 
                    } 
                } 
            } 
        } 
        security-zone UNTRUST { 
            interfaces { 
                ge-0/0/1.0 { 
                    host-inbound-traffic { 
                        system-services { 
                            ping; 
                        } 
                    } 
                } 
            } 
        } 
    } 
} 
applications { 
    application tcp-5000 { 
        protocol tcp; 
        destination-port 5000; 
    } 
} 
-- Exhibit -- 
Your customer is attempting to reach a new server that should be accessible publicly using 192.168.100.100 on TCP port 5000, and internally using 10.100.100.1 on TCP port 5555. You notice no sessions form when the customer attempts to access the server. 
Referring to the exhibit, what will resolve this problem?
  1. There must be a TRUST-to-UNTRUST security policy to allow return traffic.
  2. The NAT pool server must use port 5000.
  3. The UNTRUST-to-TRUST security policy must allow port 5555.
  4. The NAT rule set rule1 must match on port 5555.
Correct answer: C
Explanation:
After DNAT application becomes 5555.
After DNAT application becomes 5555.
Question 6
  
Your company has a Web server in the trust zone. You configure a NAT rule to allow Internet users from the untrust zone to access this Web server. Internet users use the public IP address 70.1.1.1 to access this Web server, but they report that the server is not accessible. 
Referring to the exhibit, which configuration change would resolve this problem?
  1. set security nat proxy-arp interface fe-0/0/2 address 70.1.1.0/24
  2. set security zones security-zone untrust host-inbound-traffic system-services http
  3. set security nat destination rule-set http rule 1 match source-address 0.0.0.0/0
  4. set security address-book global address web-server 192.168.1.11/32
Correct answer: D
Explanation:
DNAT is first, followed by Policy look-up.
DNAT is first, followed by Policy look-up.
Question 7
-- Exhibit -- 
user@host> show log flow.log 
Jun 12 20:00:45 host clear-log[ ]: logfile cleared
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:172.23.1.20/2526->10.3.202.56/443;6> matched filter to_https:
... 
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:  fe-0/0/6.0:172.23.1.20/2526->10.3.202.56/443, tcp, flag 2 syn
... 
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:check self-traffic on fe-0/0/6.0, in_tunnel 0x0
... 
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:flow_first_rule_dst_xlate: DST xlate: 10.3.202.56(443) to 10.25.0.3(443), rule/pool id 2/2.
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:flow_first_routing: vr_id 0, call flow_route_lookup(): src_ip 172.23.1.20, x_dst_ip 10.25.0.3, in ifp fe-0/0/6.0, out ifp N/A sp 2526, dp 443, ip_proto 6, tos 0
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:Doing DESTINATION addr route-lookup
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:  routed (x_dst_ip 10.25.0.3) from managed (fe-0/0/6.0 in 0) to ge-0/0/1.4093, Next-hop: 10.25.0.3
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:flow_first_policy_search: policy search from zone managed-> zone trust (0x110,0x9de01bb,0x1bb)
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:  app 58, timeout 1800s, curr ageout 20s
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:  permitted by policy default-policy-00(2)
... 
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:flow_xlate_pak
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:  post addr xlation: 172.23.1.20->10.25.0.3.
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:  post addr xlation: 172.23.1.20->10.25.0.3.
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:skip pre-frag: is_tunnel_if- 0, is_if_mtu_configured- 0
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:mbuf 0x42344180, exit nh 0xb00010
Jun 12 20:01:10 20:01:10.412643:CID-0:RT: ----- flow_process_pkt rc 0x0 (fp rc 0)
-- Exhibit -- 
You want to allow Web-based management of your SRX Series device through fe-0/0/6.0. This interface belongs to the managed zone with an IP address of 10.3.202.56. You are unable to open an HTTPS connection and have enabled traceoptions to troubleshoot the problem. 
Referring to the exhibit, what is causing this problem?
  1. The HTTPS protocol is not enabled in the managed zone.
  2. The HTTPS protocol is not enabled in the trust zone.
  3. The lo0 interface is not configured in the managed zone.
  4. The packet was diverted to the wrong zone.
Correct answer: D
Explanation:
See:Jun 12 20:01:10 20:01:10.412643:CID-0:RT:flow_first_policy_search: policy search from zone managed-> zone trust (0x110,0x9de01bb,0x1bb)
See:
Jun 12 20:01:10 20:01:10.412643:CID-0:RT:flow_first_policy_search: policy search from zone managed-> zone trust (0x110,0x9de01bb,0x1bb)
Question 8
-- Exhibit -- 
user@R1> show security ike security-associations 
user@R1> show security zones 
Security zone: trust
  Send reset for non-SYN session TCP packets: Off
  Policy configurable: Yes
  Interfaces bounD. 3 
  Interfaces:
    ge-0/0/0.0 
    ge-0/0/6.0 
    lo0.0 
Security zone: untrust
  Send reset for non-SYN session TCP packets: Off
  Policy configurable: Yes
  Interfaces bounD. 1 
  Interfaces:
    ge-0/0/1.0 
Security zone: junos-host
  Send reset for non-SYN session TCP packets: Off
  Policy configurable: Yes
  Interfaces bounD. 0 
  Interfaces:
user@R1> show interfaces st0 
Physical interface: st0, Enabled, Physical link is Up
  Interface index: 130, SNMP ifIndex: 503
  Type: Secure-Tunnel, Link-level type: Secure-Tunnel, MTU: 9192
  Device flags   : Present Running
  Interface flags: Point-To-Point
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)
  Logical interface st0.0 (Index 72) (SNMP ifIndex 546) 
    Flags: Link-Layer-Down Point-To-Point SNMP-Traps
    Encapsulation: Secure-Tunnel
    Input packets : 3
    Output packets: 3
    Security: Zone: Null
    Protocol inet, MTU: 9192
      Flags: Sendbcast-pkt-to-re
      Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
        Destination: 172.19.0.0/30, Local: 172.19.0.1
user@R1> show interfaces ge-0/0/1 
Physical interface: ge-0/0/1, Enabled, Physical link is Up
  Interface index: 135, SNMP ifIndex: 508
  Link-level type: Ethernet, MTU: 1514, Link-mode: Full-duplex, SpeeD. 1000mbps,
  BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
  Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
  Remote fault: Online
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x0
  Link flags     : None
  CoS queues     : 8 supported, 8 maximum usable queues
  Current address: b0:c6:9a:73:27:81, Hardware address: b0:c6:9a:73:27:81
  Last flapped   : 2013-06-12 15:22:48 UTC (00:59:41 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)
  Active alarms  : None
  Active defects : None
  Interface transmit statistics: Disabled
  Logical interface ge-0/0/1.0 (Index 71) (SNMP ifIndex 541) 
    Flags: SNMP-Traps 0x0 Encapsulation: ENET2
    Input packets : 40
    Output packets: 27
    Security: Zone: untrust
    Allowed host-inbound traffic : ping
    Protocol inet, MTU: 1500
      Flags: Sendbcast-pkt-to-re
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 184.0.15.0/30, Local: 184.0.15.1, Broadcast: 184.0.15.3
user@R1> show log ipsec-trace | match "500|drop" 
Jun 12 16:32:10 16:32:10.680034:CID-0:RT:ageout 71,184.0.15.2/500->184.0.15.1/500,17, (0/0)
Jun 12 16:32:51 16:32:51.874191:CID-0:RT:184.0.15.2/500->184.0.15.1/500;17> :
Jun 12 16:32:51 16:32:51.874191:CID-0:RT:  ge-0/0/1.0:184.0.15.2/500->184.0.15.1/500, udp
Jun 12 16:32:51 16:32:51.874191:CID-0:RT: find flow: table 0x4f160b38, hash 8769(0xffff), sa 184.0.15.2, da 184.0.15.1, sp 500, dp 500, proto 17, tok 8
Jun 12 16:32:51 16:32:51.874191:CID-0:RT:pak_for_self : proto 17, dst port 500, action 0x0
Jun 12 16:32:51 16:32:51.874191:CID-0:RT:  flow_first_in_dst_nat: in  0/1.0>, out  A> dst_adr 184.0.15.1, sp 500, dp 500
Jun 12 16:32:51 16:32:51.874555:CID-0:RT:  packet droppeD. for self but not interested
Jun 12 16:32:51 16:32:51.874555:CID-0:RT:  packet dropped, packet droppeD. for self but not interested.
Jun 12 16:32:54 16:32:54.680399:CID-0:RT:ageout 71,184.0.15.2/500->184.0.15.1/500,17, (0/0)
Jun 12 16:32:56 16:32:56.888094:CID-0:RT:184.0.15.2/500->184.0.15.1/500;17> :
Jun 12 16:32:56 16:32:56.888094:CID-0:RT:  ge-0/0/1.0:184.0.15.2/500->184.0.15.1/500, udp
Jun 12 16:32:56 16:32:56.888094:CID-0:RT: find flow: table 0x4f160b38, hash 8769(0xffff), sa 184.0.15.2, da 184.0.15.1, sp 500, dp 500, proto 17, tok 8
Jun 12 16:32:56 16:32:56.888094:CID-0:RT:pak_for_self : proto 17, dst port 500, action 0x0
Jun 12 16:32:56 16:32:56.888094:CID-0:RT:  flow_first_in_dst_nat: in  0/1.0>, out  A> dst_adr 184.0.15.1, sp 500, dp 500
Jun 12 16:32:56 16:32:56.888094:CID-0:RT:  packet droppeD. for self but not interested
Jun 12 16:32:56 16:32:56.888094:CID-0:RT:  packet dropped, packet droppeD. for self but not interested.
Jun 12 16:33:00 16:33:00.680794:CID-0:RT:ageout 71,184.0.15.2/500->184.0.15.1/500,17, (0/0)
Jun 12 16:33:07 16:33:06.902220:CID-0:RT:184.0.15.2/500->184.0.15.1/500;17> :
Jun 12 16:33:07 16:33:06.902220:CID-0:RT:  ge-0/0/1.0:184.0.15.2/500->184.0.15.1/500, udp
Jun 12 16:33:07 16:33:06.902220:CID-0:RT: find flow: table 0x4f160b38, hash 8769(0xffff), sa 184.0.15.2, da 184.0.15.1, sp 500, dp 500, proto 17, tok 8
Jun 12 16:33:07 16:33:06.902220:CID-0:RT:pak_for_self : proto 17, dst port 500, action 0x0
Jun 12 16:33:07 16:33:06.902220:CID-0:RT:  flow_first_in_dst_nat: in  0/1.0>, out  A> dst_adr 184.0.15.1, sp 500, dp 500
Jun 12 16:33:07 16:33:06.902220:CID-0:RT:  packet droppeD. for self but not interested
Jun 12 16:33:07 16:33:06.902220:CID-0:RT:  packet dropped, packet droppeD. for self but not interested.
-- Exhibit -- 
You are asked to troubleshoot a new IPsec tunnel that is not establishing between R1 and R2. The remote team has verified that R2's configuration is correct. 
Referring to the exhibit, which two actions are required to resolve the problem? (Choose two.)
  1. Add the st0.0 interface to a security zone.
  2. Change the st0.0 interface MTU to 1400.
  3. Enable IKE for host inbound traffic in the untrust zone.
  4. Enable IKE for host inbound traffic in the trust zone.
Correct answer: AC
Question 9
-- Exhibit -- 
user@R1> show log ike-trace 
Jun 13 07:45:10 ikev2_packet_v1_start: Passing IKE v1.0 packet to IKEv1 library
Jun 13 07:45:10 ike_get_sA. Start, SA = { 7fd86fbe 8a99c1f6 - 00000000 00000000 } / 00000000, remote = 184.0.15.2:500
Jun 13 07:45:10 ike_sa_allocate: Start, SA = { 7fd86fbe 8a99c1f6 - a1bc3f1d e2a45308 }
Jun 13 07:45:10 ike_init_isakmp_sA. Start, remote = 184.0.15.2:500, initiator = 0
Jun 13 07:45:10 ike_decode_packet: Start
Jun 13 07:45:10 ike_decode_packet: Start, SA = { 7fd86fbe 8a99c1f6 - b8f95b2e f92ca733} / 00000000, nego = -1
Jun 13 07:45:10 ike_decode_payload_sA. Start
Jun 13 07:45:10 ike_decode_payload_t: Start, # trans = 1
Jun 13 07:45:10 ike_decode_payload_t: Start, # trans = 1
Jun 13 07:45:10 ike_st_i_viD. VID[0..16] = afcad713 68a1f1c9 ...
Jun 13 07:45:10 ike_st_i_viD. VID[0..16] = 27bab5dc 01ea0760 ...
Jun 13 07:45:10 ike_st_i_viD. VID[0..16] = 6105c422 e76847e4 ...
Jun 13 07:45:10 ike_st_i_viD. VID[0..16] = 4485152d 18b6bbcd ...
Jun 13 07:45:10 ike_st_i_viD. VID[0..16] = cd604643 35df21f8 ...
Jun 13 07:45:10 ike_st_i_viD. VID[0..16] = 90cb8091 3ebb696e ...
Jun 13 07:45:10 ike_st_i_viD. VID[0..16] = 7d9419a6 5310ca6f ...
Jun 13 07:45:10 ike_st_i_viD. VID[0..16] = 4a131c81 07035845 ...
Jun 13 07:45:10 ike_st_i_viD. VID[0..28] = 69936922 8741c6d4 ...
Jun 13 07:45:10 ike_st_i_sa_proposal: Start
Jun 13 07:45:10 P1 SA payload match failed for sa-cfg to-R2. Abortingnegotiation for tunnel type 2 local:184.0.15.1 remote:184.0.15.2 IKEv1.
Jun 13 07:45:10 iked_pm_ike_spd_select_ike_sa failed. rc 1, error_code: No proposal chosen
Jun 13 07:45:10 ikev2_fb_spd_select_sa_cB. IKEv2 SA select failed with error No proposal chosen (neg a7e800)
Jun 13 07:45:10 ike_isakmp_sa_reply: Start
Jun 13 07:45:10 ike_state_restart_packet: Start, restart packet SA = { 7fd86fbe 8a99c1f6 - b8f95b2e f92ca733}, nego = -1
Jun 13 07:45:10 ike_st_i_sa_proposal: Start
Jun 13 07:45:10 ike_st_i_cr: Start
Jun 13 07:45:10 ike_st_i_cert: Start
Jun 13 07:45:10 ike_st_i_private: Start
Jun 13 07:45:10 ike_st_o_sa_values: Start
Jun 13 07:45:10 184.0.15.1:500 (Responder) -> 184.0.15.2:500 { 7fd86fbe 8a99c1f6 - b8f95b2e f92ca733 [-1] / 0x00000000 } IP; Error = No proposal chosen (14)
Jun 13 07:45:10 ike_alloc_negotiation: Start, SA = { 7fd86fbe 8a99c1f6 - b8f95b2e f92ca733}
Jun 13 07:45:10 ike_encode_packet: Start, SA = { 0x7fd86fbe 8a99c1f6 - b8f95b2e f92ca733 } / b20d590c, nego = 0
Jun 13 07:45:10 ike_send_packet: Start, send SA = { 7fd86fbe 8a99c1f6 - b8f95b2e f92ca733}, nego = 0, dst = 184.0.15.2:500,  routing table id = 0
Jun 13 07:45:10 ike_delete_negotiation: Start, SA = { 7fd86fbe 8a99c1f6 - b8f95b2e f92ca733}, nego = 0
Jun 13 07:45:10 ike_free_negotiation_info: Start, nego = 0
Jun 13 07:45:10 ike_free_negotiation: Start, nego = 0
Jun 13 07:45:10 IKE negotiation fail for local:184.0.15.1, remote:184.0.15.2 IKEv1 with status: No proposal chosen
Jun 13 07:45:10   IKEv1 Error : No proposal chosen
Jun 13 07:45:40 P1 SA 3770105 timer expiry. ref cnt 1, timer reason Force delete timer expired (1), flags 0x330.
Jun 13 07:45:40 iked_pm_ike_sa_delete_done_cB. For p1 sa index 3770105, ref cnt 1, status: Error ok
Jun 13 07:45:40 ike_remove_callback: Start, delete SA = { 7fd86fbe 8a99c1f6 - b8f95b2e f92ca733}, nego = -1
Jun 13 07:45:40 ike_delete_negotiation: Start, SA = { 7fd86fbe 8a99c1f6 - b8f95b2e f92ca733}, nego = -1
Jun 13 07:45:40 ssh_ike_tunnel_table_entry_delete: Deleting tunnel_iD. 0 from IKE tunnel table
Jun 13 07:45:40 ssh_ike_tunnel_table_entry_delete: The tunnel iD. 0 doesn't exist in IKE tunnel table
Jun 13 07:45:40 ike_sa_delete: Start, SA = { 7fd86fbe 8a99c1f6 - b8f95b2e f92ca733 }
Jun 13 07:45:40 ike_free_negotiation_isakmp: Start, nego = -1
Jun 13 07:45:40 ike_free_negotiation: Start, nego = -1
Jun 13 07:45:40 IKE SA delete called for p1 sa 3770105 (ref cnt 1) local:184.0.15.1, remote:184.0.15.2, IKEv1
Jun 13 07:45:40 iked_pm_p1_sa_destroy:  p1 sa 3770105 (ref cnt 0), waiting_for_del 0x0
Jun 13 07:45:40 ike_free_sA. Start
-- Exhibit -- 
You are asked to troubleshoot a new IPsec VPN between R1 and R2 that is not coming up. You have captured the traceoptions output shown in the exhibit. 
What is the reason for the problem?
  1. IKE Phase 2 proposal mismatch
  2. IKE preshared key mismatch
  3. IKE Phase 1 proposal mismatch
  4. IKE Phase 1 mode mismatch
Correct answer: C
Question 10
-- Exhibit -- 
user@SRX-1> show configuration security ike 
traceoptions { 
    file ike-trace; 
    flag all; 
} 
policy juniper { 
    proposal-set standard; 
    pre-shared-key ascii-text "$ $ znCO hKMXtuMX - gTz "; ## SECRET-DATA 
} 
gateway juniper { 
    ike-policy juniper; 
    address 192.168.1.11; 
    external-interface fe-0/0/7; 
} 
user@SRX-1> show configuration security ipsec 
traceoptions { 
    flag all; 
} 
policy juniper { 
    proposal-set standard; 
} 
vpn juniper { 
    bind-interface st0.0; 
    ike { 
        gateway juniper; 
        ipsec-policy juniper; 
    } 
} 
user@SRX-1> show security ike security-associations 
user@SRX-1> show security ipsec security-associations 
  Total active tunnels: 0
user@SRX-1> show log ike-trace 
... 
Jun 13 16:21:33 ike_st_o_all_done: MESSAGE: Phase 1 { 0x3f669946 90eba0c7 - 0x76bdffab f8770040 } / 00000000, version = 1.0, xchg = Identity protect, auth_method = Pre shared keys, Responder, cipher = 3des-cbc, hash = sha1, prf = hmac-sha1, life = 0 kB / 28800 sec, key l
Jun 13 16:21:33 192.168.1.10:500 (Responder) -> 192.168.1.11:500 { 3f669946 90eba0c7 - 76bdffab f8770040 [-1] / 0x00000000 } IP; MESSAGE: Phase 1 version = 1.0, auth_method = Pre shared keys, cipher = 3des-cbc, hash = sha1, prf = hmac-sha1, life = 0 kB / 28800 sec, key
Jun 13 16:21:33 ike_encode_packet: Start, SA = { 0x3f669946 90eba0c7 - 76bdffab f8770040 } / 00000000, nego = -1
Jun 13 16:21:33 ike_send_packet: Start, send SA = { 3f669946 90eba0c7 - 76bdffab f8770040}, nego = -1, dst = 192.168.1.11:500,  routing table id = 0
Jun 13 16:21:33 ike_send_notify: Connected, SA = { 3f669946 90eba0c7 - 76bdffab f8770040}, nego = -1
Jun 13 16:21:33 iked_pm_ike_sa_done: local:192.168.1.10, remote:192.168.1.11 IKEv1
Jun 13 16:21:33 iked_pm_id_validate id NOT matched.
Jun 13 16:21:33 P1 SA 3075313 timer expiry. ref cnt 1, timer reason Defer delete timer expired (3), flags 0x331.
Jun 13 16:21:33 iked_pm_ike_sa_delete_notify_done_cB. For p1 sa index 3075313, ref cnt 1, status: Error ok
Jun 13 16:21:33 ike_expire_callback: Start, expire SA = { 3f669946 90eba0c7 - 76bdffab f8770040}, nego = -1
Jun 13 16:21:33 ike_alloc_negotiation: Start, SA = { 3f669946 90eba0c7 - 76bdffab f8770040}
... 
-- Exhibit -- 
You are troubleshooting a new IPsec VPN that is not establishing between SRX-1 and a remote end device. 
Referring to the exhibit, what is causing the problem?
  1. Pre-shared key mismatch
  2. IKE Phase 1 proposals mismatch
  3. IKE Phase 1 IKE ID mismatch
  4. IKE Phase 2 proxy ID mismatch
Correct answer: C
Explanation:
See line:Jun 13 16:21:33 iked_pm_id_validate id NOT matched.
See line:
Jun 13 16:21:33 iked_pm_id_validate id NOT matched.
CONNECT US
HOW TO OPEN VCE FILES

Use VCE Exam Simulator to open VCE files
Avanaset

HOW TO OPEN VCEX AND EXAM FILES

Use ProfExam Simulator to open VCEX and EXAM files
ProfExam Screen

ProfExam
ProfExam at a 20% markdown

You have the opportunity to purchase ProfExam at a 20% reduced price

Get Now!