Security · interview question
Which option describes the most likely pitfall around deserialization safety?
Multiple choiceHardchapter-17-curatedpremiumsecuritydeserialization-safety
Answer and explanation
Correct answer
D. Treating deserialization as harmless plumbing can turn malformed input into surprising runtime behavior.
Why
Treating deserialization as harmless plumbing can turn malformed input into surprising runtime behavior. Calling out that risk matters because good answers mention boundary skepticism and explicit shape checks.
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?