Skip to main content
🔒 Preview mode. The first 15 Foundations lessons are free; this one is Pro. Start a 7-day trial to unlock the editor, AI hints and the rest of the curriculum. Card required, cancel any time in Dashboard.
Start 7-day trial →
⚡
← Courses
›
Senior Deep-Dives
›
Module 4 · Memory + profiling · Recap
›
Pickling: security warning
quiz
97 / 161
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Why never pickle untrusted input? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Why never pickle untrusted input? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
The wire format changes between Python minor versions, so a 3.11 pickle silently breaks under a 3.12 worker.
B
Pickle deserialization is code execution — `__reduce__` lets pickled data run arbitrary Python.
C
Pickle requires the original class to be importable, so refactoring a module renames the qualified path and breaks loads.
D
Pickled bytes are larger than JSON for the same payload, so cache memory grows linearly with object header overhead.
Submit answer
💬 Discussion
Be the first to ask a question or share a tip.
Sign in
to join the discussion. Reading is free.
Loading discussion…