Security · interview question
What assumption should be made explicit when working with sql injection prevention?
Multiple choiceMediumchapter-17-curatedpremiumsecuritysql-injection-prevention
Answer and explanation
Correct answer
B. The expected data shape, boundary rule, or invariant that the rest of the code depends on staying true.
Why
Once assumptions are explicit, bugs are easier to detect and test cases are easier to design.
Test yourself on Security
A free test with instant, explained results. No account needed.
More Security questions
- What is the healthiest performance judgment around secrets management?
- What is the clearest sign that code around secrets management should be refactored?
- Which boundary choice best fits log redaction in a maintainable Python system?
- If input validation fails in production, what handling philosophy is strongest?
- Which response shows the healthiest evidence-first mindset around input validation?
- When is log redaction being used in the wrong way?