The correct choice is a rule that parses JSON and checks for abnormal structures indicating injection. This is because SQL injection in JSON APIs requires context-aware analysis: a WAF must decode the JSON payload, inspect each key-value pair for malicious SQL syntax, and flag anomalies like nested objects or unexpected keys that deviate from the expected schema. Simple keyword matching against SQL terms like “SELECT” or “OR” would cause excessive false positives in legitimate JSON data. On the Cisco SCOR 350-701 exam, this tests your understanding of how modern WAFs handle application-layer attacks in REST APIs, often contrasting signature-based rules with behavioral or structural analysis. A common trap is choosing a rule that blocks SQL keywords without considering JSON encoding, which would block benign payloads. Remember the mnemonic: “Parse before you block—JSON needs a key-by-key unlock.”
350-701 Security Concepts Practice Question
This 350-701 practice question tests your understanding of security concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 security engineer is evaluating a web application firewall (WAF) rule set. The application uses a custom REST API that accepts JSON payloads. Which WAF rule is most effective at preventing SQL injection attacks while minimizing false positives?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a rule that parses JSON and checks for abnormal structures that indicate injection
Option D is correct because JSON-based APIs require context-aware parsing to detect SQL injection within structured payloads. A rule that parses JSON and checks for abnormal structures can identify injection attempts (e.g., nested objects or unexpected keys) without relying on simple keyword matching, which reduces false positives. This approach aligns with the WAF's ability to decode and inspect JSON fields for malicious SQL patterns while ignoring benign data.
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.
✗
Apply a generic SQL injection signature set from the WAF vendor
Why it's wrong here
Generic signatures may cause false positives in JSON data due to different formats.
✗
Block requests containing 'SELECT' or 'UNION' in the URL
Why it's wrong here
Blocking keywords is simplistic and may block legitimate traffic; SQL injection can be encoded.
✗
Set the maximum request size to 10 MB
Why it's wrong here
Request size limits do not prevent SQL injection.
✓
Use a rule that parses JSON and checks for abnormal structures that indicate injection
Why this is correct
JSON-specific validation reduces false positives while catching injection attempts.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that generic signature sets are universally effective, but the trap here is that custom APIs with JSON payloads require context-aware parsing to avoid false positives and catch injection in non-keyword forms.
Trap categories for this question
Keyword trap
Blocking keywords is simplistic and may block legitimate traffic; SQL injection can be encoded.
Detailed technical explanation
How to think about this question
Under the hood, a WAF that parses JSON must first validate the structure (e.g., RFC 8259 compliance) and then apply context-aware rules to each field, such as detecting SQL metacharacters (e.g., single quotes) or abnormal nesting that suggests injection. In a real-world scenario, an attacker might embed SQL in a JSON string like {"username": "admin' OR '1'='1"}, which a generic signature set might miss if it only checks for 'SELECT' or 'UNION'. The JSON parser-based rule can detect the single quote and the OR clause as abnormal patterns, minimizing false positives by ignoring benign JSON structures.
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.
Security Concepts — This question tests Security Concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use a rule that parses JSON and checks for abnormal structures that indicate injection — Option D is correct because JSON-based APIs require context-aware parsing to detect SQL injection within structured payloads. A rule that parses JSON and checks for abnormal structures can identify injection attempts (e.g., nested objects or unexpected keys) without relying on simple keyword matching, which reduces false positives. This approach aligns with the WAF's ability to decode and inspect JSON fields for malicious SQL patterns while ignoring benign data.
What should I do if I get this 350-701 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 350-701 practice question is part of Courseiva's free Cisco 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 350-701 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.