Python Fundamentals · interview question

A bug appears around built-in types and none. What is the strongest first debugging move?

Multiple choiceEasychapter-1-curatedpremiumpython-fundamentalsbuilt-in-types-and-none

python

quantity = 3
coupon_code = None
is_expedited = False
print(type(quantity).__name__, coupon_code, is_expedited)

Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.Solve the symptom with comments only and avoid changing the code shape around built-in types and none.Keep built-in types and none 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.

Answer and explanation

Correct answer

A. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.

Why

That approach is reliable because it creates evidence. Forcing everything into strings or treating missing data as a fake value creates confusion that shows up later in comparisons and validation.

Test yourself on Python Fundamentals

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

Start free test

All Python Fundamentals questions →

A bug appears around built-in types and none. What is the strongest first debugging move?

Correct answer

Why

More Python Fundamentals questions