You have75 minutes to complete20 original recovery and release tasks. This different assessment includes invalid drafts, wrong insertion modes, source conflicts, identity-safe changes, delegation-cap experiments and local package evidence. Each task starts with a fresh fictional setup so you must inspect its own records and boundaries.
Keep the clock in view while deciding which evidence matters. A failed write should retain its draft and source, while a package name cannot establish correct target routing. The mock tests the supported browser subset and original workplace decisions. It does not connect a tenant, create external approvals or claim an official certification format. After expiry, use the retained review to inspect the reasoning and rebuild only this mock when starting again.