Courseiva

Fortinet NSE7 Specialty Modules (SD-WAN and Enterprise Firewall tracks) (FORTINET-NSE7-SPECIALTY) (FORTINET-NSE7-SPECIALTY) — Questions 151–152

152 questions total · 3 pages · All types, answers revealed

Page 2

Page 3 of 3

151
Multi-Selecthard

Which THREE types of traffic are typically inspected by an IPS policy?

Select 3 answers
A.HTTP/HTTPS traffic
B.SMTP traffic
C.SNMP monitoring traffic
D.FTP traffic
E.ICMP echo requests
AnswersA, B, D

IPS policies inspect HTTP and HTTPS traffic, matching signatures against web requests and responses to block exploits, malicious payloads and known attack patterns. This satisfies the requirement because web protocols carry the majority of client-facing attack traffic that signature-based inspection targets.

Why this answer

An IPS policy typically inspects application-layer protocols that carry user data and are common attack vectors, so HTTP/HTTPS traffic (A) is correct because the IPS performs deep packet inspection on web requests/responses to block exploits like SQL injection and cross-site scripting. SMTP traffic (B) is correct because mail transfer sessions are inspected for malicious attachments, spam relays, and SMTP command exploits. FTP traffic (D) is correct because FTP control and data channels are inspected for credential theft, directory traversal, and unauthorized file transfers.

SNMP monitoring traffic (C) is not typically inspected by an IPS policy since it is management-plane traffic usually handled by monitoring systems rather than deep content inspection. ICMP echo requests (E) are network-layer diagnostic traffic, not application-layer content that an IPS policy inspects for threats.

Exam trap

FORTINET-NSE7-SPECIALTY often tests the distinction between application-layer protocols that are commonly inspected by IPS (HTTP, SMTP, FTP) and network-layer or management protocols (ICMP, SNMP) that are not typically part of IPS inspection, causing candidates to over-select.

152
Multi-Selecthard

Which TWO of the following can cause an SD-WAN member to be marked as 'down' in an SLA?

Select 2 answers
A.The probe times out.
B.The system clock is updated.
C.The packet loss exceeds the threshold.
D.The firewall policy is disabled.
E.The interface IP address is changed.
AnswersA, C

SLA probes send periodic health checks to configured targets. If replies stop arriving before the timeout expires, the probe is marked as timed out, the member fails its SLA check, and FortiGate transitions that member to the down state, removing it from eligible routing.

Why this answer

In SD-WAN SLA monitoring, a member is marked down when an SLA probe fails to receive a response within the configured timeout, so option A (the probe times out) directly triggers the down state. Option C (packet loss exceeds the threshold) is also correct because SLA criteria include metrics such as packet loss, latency, and jitter, and exceeding the configured loss threshold causes the member to fail the SLA and be marked down. Options B, D, and E do not by themselves cause an SLA member to be marked down: a system clock update does not affect probe reachability, disabling a firewall policy is a configuration change rather than an SLA metric violation, and changing an interface IP address would typically break connectivity or require reconfiguration but is not itself an SLA threshold breach that marks the member down.

Exam trap

FORTINET-NSE7-SPECIALTY often tests the distinction between SLA health-check triggers (probe timeout, packet loss, latency, jitter) and unrelated administrative changes like clock updates or policy edits, which candidates mistakenly associate with link state.

Page 2

Page 3 of 3

All pages