Your final practice queue crosses language internals, service operations and domain design. The variety is deliberate. A cache invalidation bug, a secret in a nested log and an unavailable dispatch option need different fixes even when they all appear in one review.
Each function reuses a technique you have already practiced on fresh fictional data. Identify the output contract and the exceptional boundary before writing code. Keep the distinction between evidence and inference: supplied profile rows support a cost comparison, while a dependency trace supports a risk model. Neither proves a performance measurement that was never taken. Finish with results that retain their evidence and preserve the requested order. The course ends with transfer work rather than another new feature.