Security · interview question

Which move is the best default when deserialization safety becomes part of this workflow?

Multiple choiceHardchapter-17-curatedpremiumsecuritydeserialization-safety

Parse data with clear expectations and avoid unsafe object-loading patterns that execute or infer too much.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Keep deserialization safety implicit so the script stays short and hope the next engineer infers the rule.Solve the symptom with comments only and avoid changing the code shape around deserialization safety.

Answer and explanation

Correct answer

A. Parse data with clear expectations and avoid unsafe object-loading patterns that execute or infer too much.

Why

Parse data with clear expectations and avoid unsafe object-loading patterns that execute or infer too much. That is the stronger engineering move because good answers mention boundary skepticism and explicit shape checks. Treating deserialization as harmless plumbing can turn malformed input into surprising runtime behavior.

Test yourself on Security

A free test with instant, explained results. No account needed.

Start free test

All Security questions →

Which move is the best default when deserialization safety becomes part of this workflow?

Correct answer

Why

More Security questions