Juniper JN0-696 問題集

質問 1：
You are having problems establishing an IPsec tunnel between two SRX Series devices.
What are two explanations for this problem? (Choose two.)
A. antivirus configuration
B. preshared key mismatch
C. proposal mismatch
D. TCP MSS clamping is disabled
正解：A,D

質問 2：
-- Exhibit -{hold:node0} user@host1> show chassis cluster status Cluster ID. 1 Node Priority Status Preempt Manual failover
Redundancy group: 0 , Failover count: 0 node0 1 hold no no node1 0 lost n/a n/a {hold:node0}
user@host1> show configuration | no-more
system { host-name host1; root-authentication { encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA } name-server { 172.16.10.100; } services { ssh; telnet; web-management { http; } } syslog { user * { any emergency; } file messages { any any; authorization info; } file interactive-commands { interactive-commands any;
}
} } interfaces {
ge-0/0/0 {
unit 0 {
family inet {
address 10.210.14.131/26;
}
}
}
ge-0/0/8 {
unit 0 {
family inet {
address 172.16.1.1/24;
}
}
}
ge-0/0/9 {
unit 0 {
family inet {
address 172.16.10.1/24;
} } } }
security {
policies {
default-policy {
permit-all;
}
}
zones {
functional-zone management {
interfaces {
ge-0/0/0.0;
}
host-inbound-traffic {
system-services {
ssh;
telnet;
ping;
traceroute;
http;
snmp;
}
}
}
security-zone Trust {
host-inbound-traffic {
system-services {
any-service;
}
}
interfaces {
ge-0/0/9.0;
}
}
security-zone Untrust {
host-inbound-traffic {
system-services {
any-service;
}
}
interfaces {
ge-0/0/8.0;
}
}
}
}
{hold:node1} user@host2> show chassis cluster status Cluster ID. 1 Node Priority Status Preempt Manual failover
Redundancy group: 0 , Failover count: 0 node0 0 lost n/a n/a node1 1 hold no no
{hold:node1}
user@host2> show configuration | no-more
system { host-name host2; root-authentication { encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA } name-server { 172.16.10.100; } services { ssh; telnet; web-management { http; } } syslog { user * { any emergency; } file messages { any any; authorization info; } file interactive-commands {
interactive-commands any;
}
} } interfaces {
ge-0/0/0 {
unit 0 {
family inet {
address 10.210.14.132/26;
}
}
}
ge-0/0/8 {
unit 0 {
family inet {
address 172.16.1.1/24;
}
}
}
ge-0/0/9 {
unit 0 {
family inet {
address 172.16.10.1/24;
}
}
} }
security {
policies {
default-policy {
permit-all;
}
}
zones {
functional-zone management {
interfaces {
ge-0/0/0.0;
}
host-inbound-traffic {
system-services {
ssh;
telnet;
ping;
traceroute;
http;
snmp;
}
}
}
security-zone Trust {
host-inbound-traffic {
system-services {
any-service; } } interfaces { ge-0/0/9.0; } } security-zone Untrust { host-inbound-traffic { system-services { any-service; } } interfaces { ge-0/0/8.0; } } }
}
-- Exhibit -
Click the Exhibit button.
A user attempted to form a chassis cluster on an SRX240; however, the cluster did not form. While investigating the problem, you see the output shown in the exhibit.
What is causing the problem?
A. The cluster IDs do not match.
B. The fxp0 interface is not configured.
C. The configurations are not identical.
D. The ge-0/0/0 interface is configured.
正解：D

質問 3：
-- Exhibit --
{primary:node0}
user@host> show configuration chassis | display inheritance
cluster {
redundancy-group 1 {
node 0 priority 200;
node 1 priority 100;
interface-monitor {
ge-0/0/12 weight 255;
ge-5/0/12 weight 255;
}
}
}
-- Exhibit --
Click the Exhibit button.
A customer reports that their SRX failover is not working as expected. They expected node1 to become the primary node for the control plane when interface ge-0/0/12 failed. However, when ge0/0/12 failed, node0 remained the primary node. They send you the output shown in the exhibit.
What is causing this problem?
A. The redundancy-group configuration should include the preempt parameter.
B. The interface-monitor configuration should be applied to redundancy-group 0.
C. The weight parameter applied to ge-5/0/12 is too high.
D. The weight parameter applied to ge-0/0/12 is too low.
正解：B

質問 4：
You recently configured the antivirus feature profile on your Junos device. The security policy is sending traffic for antivirus scanning. However, the traffic is being blocked and you repeatedly receive the system log message that the scan engine is not ready. You must not allow the traffic to be dropped when the scan engine is not ready.
Which action will resolve this problem?
A. Configure an antivirus fallback option to permit the traffic when the scan engine is not ready.
B. Configure an antivirus content size limit to minimize the scanning of large files.
C. Configure an antivirus file scanning extension list to reduce the number of files for scanning.
D. Configure antivirus trickling to prevent the scan engine from timing out.
正解：A