Decide which launch step the evidence authorizes.

Instruction: Approve, hold or reject the next exposure step; calculate the gate results and separate initial launch from later expansion.

Context:

A fictional read-only reporting API is planned for 100 named tenants, with forecast peak demand of 100 requests/second for that full cohort. Its long-term objective is 99.9% eligible-request availability over 30 days. The service/release owners approved the following local rollout policy; these thresholds are exercise facts, not universal defaults.

  • Exposure steps: pilot 10 tenants, then 25, 50 and 100. Each increase requires a recorded release-owner decision; no new write operations are covered.
  • Expansion gate at the current step: at least 15 minutes and 10,000 eligible requests, plus two consecutive completed five-minute windows each with at least 2,000 requests, bad-request rate at most 0.1%, and p95 at most 500 ms. Telemetry must be complete and healthy.
  • Hold expansion if that gate is not met. Stop expansion and reverse the latest step for a verified release-related bad-request rate above 0.5% in a five-minute window with at least 1,000 requests, or p95 above 750 ms in two such consecutive windows. Any credible security/data-integrity finding triggers immediate containment, regardless of sample size.
EvidenceRecorded result
10-tenant pilot, current artifact/configuration20 minutes; 20,000 eligible requests; 8 bad; representative supported report types and tenant classes.
Last two completed five-minute windowsWindow A: 5,500 eligible, 2 bad, p95 410 ms. Window B: 5,000 eligible, 3 bad, p95 430 ms. Telemetry completeness checks pass.
Performance and failure exercisePassed at 200 requests/second with one instance unavailable; same read-only workload mix and dependency envelope.
Recovery and operationRestore met RPO/RTO; paging delivery exercised; on-call owner accepted runbook; previous artifact and traffic-reversal path are verified compatible.
Required reviewsNo unresolved security/data-integrity findings. One cosmetic alignment defect is documented and accepted by product.

At this decision point, may 25 tenants receive the release? Does the same evidence authorize 50 or 100 immediately? State what happens if the next tier has 0.2% bad requests but does not cross a stop threshold.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would approve the bounded increase from 10 to 25 tenants...

Upgrade to view official answer

Related Questions