Skip to main content

Cloud foundations assessment and calibration

Score 0 absent/incorrect, 1 prompted/incomplete, 2 independently supported with limits, 3 justified fresh transfer. All CF1–CF6 categories require at least 2.

  • CF1 — Boundary: trace one operation through ingress, app, data, naming, identity and required egress. Name a correlated failure and distinguish request from recovery dependencies.
  • CF2 — Capacity: calculate every single-zone loss and one correlated loss using per-tier units/demand. State redistribution, capacity and dependency assumptions.
  • CF3 — Model: independently implement the archive, explain the oracle and add asymmetric three-zone, missing-dependency and correlated-loss cases. Explain why cycles are rejected rather than silently declared ready.
  • CF4 — Identity/network evidence: retain original allowed/denied identity cases, federation trust scope, emergency path, route/traffic-rule evidence and failure trace. A local model lane must explicitly identify hypothetical behavior and what must later be verified against provider semantics. The capacity model alone cannot pass this category.
  • CF5 — Resource choice/cost: retain original compute/storage/database comparison, dated units/assumptions, egress/retention costs and budget-notification limitations. A local estimate must use explicitly fictional prices or cited current prices, not pretend to be a bill.
  • CF6 — Inventory closure: preserve before/after scoped inventory and deliberate retention. Demonstrate that a failed or incomplete listing prevents a clean teardown claim; identify owner and follow-up for leftovers. Never delete unrelated resources to obtain a pass.

Calibration​

API replicas of 60 in A and B at demand 50 can survive either zone's compute loss. With a sole required database in A, losing A still breaks the operation. Report surviving API capacity 60 and readiness false; do not erase capacity simply because the dependency failed.

Three zones of 50 at demand 90 leave 100 after a single loss, but demand 120 fails. A capacity exactly equal to demand passes this finite contract; real margin and uncertainty must be justified separately. A graph cycle is outside the contract and raises ValueError, even if a participant already has zero capacity.

Four hours × 0.20 plus ten units × 0.03 for one month equals 1.10 fictional currency units. It excludes additional charge categories. A deleted VM with a retained disk or inaccessible inventory is not a verified empty environment. A budget notification is not a hard cap.

Delayed transfer​

At least 48 hours later, solve a fresh three-zone graph with a changed demand, shared dependency and incomplete inventory. Defend what the local model establishes and what still needs a real experiment. Preserve predictions, errors, repairs and assistance disclosures. Author checks are not learner service or cloud execution.