Get App

Python: Which practice avoids a common mistake with Profiling with cProfile and timeit?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Profiling with cProfile and timeit?

  1. Ignore the Profiling with cProfile and timeit issue and rely on team discipline instead of clearer APIs or invariants.
  2. Silence the Profiling with cProfile and timeit problem by using broad catches, hidden globals, or extra shared mutable state.
  3. Do not claim a performance optimization is valuable without showing where the bottleneck was and how the change affected it.
  4. Prefer the version of Profiling with cProfile and timeit that makes behavior less predictable as long as the code still runs.

Hint

Look for the option that protects correctness instead of hiding the problem.

Answer and rationale

Correct answer: C. Do not claim a performance optimization is valuable without showing where the bottleneck was and how the change affected it.

Do not claim a performance optimization is valuable without showing where the bottleneck was and how the change affected it. This is a common failure mode in real Python code and a frequent interview follow-up.

Track: Python