Core Collections · interview question

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

Multiple choiceEasychapter-3-curatedpremiumcore-collectionsdicts

Use dictionaries when the code benefits from named fields or key-based access that reads like the domain.Keep dicts implicit so the script stays short and hope the next engineer infers the rule.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Solve the symptom with comments only and avoid changing the code shape around dicts.

Answer and explanation

Correct answer

A. Use dictionaries when the code benefits from named fields or key-based access that reads like the domain.

Why

Use dictionaries when the code benefits from named fields or key-based access that reads like the domain. That is the stronger engineering move because strong answers mention that dicts are powerful but still need clear contracts. Blindly passing around giant dictionaries without clarifying their expected keys creates fragile code.

Test yourself on Core Collections

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

Start free test

All Core Collections questions →

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

Correct answer

Why

More Core Collections questions