Coding (Platform)

Angular: Enforce permission rules for lazy feature access policy

An accessibility-safe interaction regressed after state ownership moved across a component boundary. The affected area is lazy feature.

Repair the lazy feature access policy implementation so it returns only permitted actions and explicit denial reasons.

Evidence

Affected surface: Angular / lazy feature.
Observed failure family: enforce permission rules.
Scope policy: contractVersion must equal 2.

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.