# Fabric production deployment and requalification: synthetic exercise worksheet

Curriculum reviewed: 2026-10-25. Use public or synthetic data only.
Do not include client evidence, credentials, private identifiers or raw receipts.

## Goal
prepare and defend a complete deployment/recovery plan in a synthetic or approved lab; no production change is part of enrolment or automatic assessment.

## Outcomes
- Design a reviewed production deployment plan.
- Bind identities and approvals to exact artifacts.
- Reason about incremental/history/security contexts.
- Handle uncertain effects and scheduled freshness.

## Synthetic case
Describe a Sales report built from order headers and order lines. State which grain you intend and which independently established expectation you would compare.

## Review each lesson
### 1. Define environments and least privilege
Inventory source, workspace, identity and query/export prerequisites without provisioning them implicitly.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 2. Review exact-plan consent
Bind definition bytes, workspace scope and deployment approvals before execution.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 3. Publish and frame immutable generations
Separate model definitions, data snapshots, refresh and observed serving state.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 4. Qualify incremental and history paths
Test batch predecessors, corrections, MERGE and temporal facts against independent expectations.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 5. Verify security and Import contexts
Require observed role/OLS enforcement and partition lifecycle evidence.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 6. Promote and recover
Preserve ordered environment qualification and avoid resubmitting an uncertain external effect.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 7. Schedule fresh qualification
Separate heartbeat, source freshness, scoped qualification and independent watchdog delivery.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 8. Run a release review
List unobserved controls and pending owner actions before any production decision.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

## Failure case
Generated definitions exist but a required execution observation is missing. Explain why qualification cannot pass and name the next required observation. Do not fabricate a receipt or change a frozen expectation.

## Evidence table
| Claim | Expected observation | Available evidence | Missing/stale | Next owner/action |
| --- | --- | --- | --- | --- |
| | | | | |

## Limitations
This worksheet is a completion check, not live qualification, business acceptance or a professional award. Pro assessment and certification policy remain planned. Keep optional live results in customer-controlled custody.