Assess an index rollout by likelihood, impact, and mitigation controls.
A slow customer search query needs an index on a 260-million-row table with high write volume and limited disk headroom. NIST risk assessment: event, likelihood, impact, response Approving an index only because it improves the query plan ignores rollout hazards such as locks, disk pressure, and replica lag. Name events Possible adverse events: write blocking, replica lag over SLO, disk exhaustion, and failed rollback if the build is canceled late. Risk assessment starts by naming what can go wrong specifically enough to control it. Estimate likelihood High write rate and large table make lag likely; online build reduces lock likelihood;…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in