Coding (Platform)

Flask: Plan cache invalidation for request hook cache lifecycle

A service boundary accepts valid traffic but mishandles duplicate, stale, or unauthorized records. The affected area is request hook.

Repair the request hook cache lifecycle implementation so it separates purge, refresh, and escalation actions by staleness and risk.

Evidence

Affected surface: Flask / request hook.
Observed failure family: plan cache invalidation.
Scope policy: region must equal eu-west.

What this task practices

This coding (platform) exercise trains the same sequence expected in an interview: understand the prompt, make assumptions explicit, produce a concrete answer, and explain the decisions behind it. The task is marked medium difficulty. The private workspace adds the tools required by this round, such as recording, code execution, diagrams, evidence panels, or structured notes. It also preserves the attempt so later feedback can be compared with previous work. Evaluation is based on task-specific criteria and the candidate seniority selected in the preparation path. Public pages never expose the reference solution, hidden tests, evaluator instructions, or another candidate’s work.