The answer is that the SQL injection signature set is disabled within the WAF profile. This is the most likely reason because a FortiGate WAF profile relies on individual signature sets to inspect traffic for specific attack patterns; if the SQL injection signature set is turned off, the WAF simply skips that inspection, allowing malicious payloads to reach the web server untouched. On the Fortinet NSE 7 Advanced Security NSE7 exam, this scenario tests your understanding that enabling a WAF profile is not enough—you must verify that the relevant signature sets are active, as a common trap is assuming the profile’s default settings block all attacks. A key memory tip is “profile on, signatures off” to recall that the WAF can be enabled yet still fail to block SQL injection if its signature set is disabled.
NSE7 Advanced Threat Protection Practice Question
This NSE7 practice question tests your understanding of advanced threat protection. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A FortiGate is configured with a WAF profile to protect a web server. The administrator notices that SQL injection attacks are still reaching the server despite the WAF being enabled. What is the MOST likely reason?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The SQL injection signature set is disabled in the WAF profile
The WAF profile contains signature sets that detect and block common attack patterns, including SQL injection. If the SQL injection signature set is disabled within the profile, the WAF will not inspect traffic for those patterns, allowing attacks to pass through. This is the most direct and likely reason why SQL injection attacks are reaching the server despite the WAF being enabled.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
The SQL injection signature set is disabled in the WAF profile
Why this is correct
WAF signatures are organized in groups; SQL injection must be enabled.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The attack is coming from a trusted IP
Why it's wrong here
Trusted IPs bypass WAF, but that is not mentioned.
✗
The web server is using HTTPS without SSL inspection
Why it's wrong here
WAF can inspect HTTPS if configured; but if SSL inspection is off, WAF still sees encrypted payload and cannot detect SQL injection.
✗
The WAF profile is not applied to the correct policy
Why it's wrong here
If applied to wrong policy, no inspection occurs. But the admin says enabled.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume a WAF profile is a monolithic block of protection, but FortiGate allows granular disabling of individual signature sets, and the exam tests whether you understand that a disabled signature set is the most direct cause of a specific attack type bypassing the WAF.
Detailed technical explanation
How to think about this question
FortiGate WAF profiles use signature-based detection with pre-defined signature sets for SQL injection, XSS, and other OWASP Top 10 threats. Each signature set can be individually enabled or disabled under 'Inline Protection' in the WAF profile configuration. In a real-world scenario, an administrator might disable the SQL injection signature set to reduce false positives from custom application queries, inadvertently leaving the application vulnerable. The WAF logs would show 'monitor' actions for SQL injection if the signature set is disabled but the profile is set to 'monitor' mode, which can mislead administrators into thinking protection is active.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Advanced Threat Protection — This question tests Advanced Threat Protection — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The SQL injection signature set is disabled in the WAF profile — The WAF profile contains signature sets that detect and block common attack patterns, including SQL injection. If the SQL injection signature set is disabled within the profile, the WAF will not inspect traffic for those patterns, allowing attacks to pass through. This is the most direct and likely reason why SQL injection attacks are reaching the server despite the WAF being enabled.
What should I do if I get this NSE7 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This NSE7 practice question is part of Courseiva's free Fortinet certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the NSE7 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.