Advanced Python · interview question
A bug appears around timing and audit scopes. What is the strongest first debugging move?
Multiple choiceHardchapter-14-curatedpremiumadvanced-pythontiming-and-audit-scopes
import time
def timed(fn):
def wrapper(*args, **kwargs):
started = time.perf_counter()
try:
return fn(*args, **kwargs)
finally:
print(time.perf_counter() - started)
return wrapperAnswer and explanation
Correct answer
D. 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. If instrumentation changes the business logic shape too much, the abstraction is working against you.
Test yourself on Advanced Python
A free test with instant, explained results. No account needed.
More Advanced Python questions
- What assumption should be made explicit when working with resource cleanup?
- Which explanation would best help the team align on timing and audit scopes?
- What do interviewers usually hear as a strong signal when you discuss timing and audit scopes well?
- Another engineer will maintain this code later. What choice helps the most around timing and audit scopes?
- A senior interviewer asks for one tradeoff behind resource cleanup. What is the strongest follow-up?
- Which judgment is strongest when choosing a data shape for functools.wraps?