20.13 Troubleshooting & Architect Labs
Lab 1 — Transport failure
A package imports with dependency errors.
Diagnose
- identify the first failing object;
- map its dependencies;
- verify target space and privileges;
- check environment-specific configuration;
- redeploy only after correcting the root cause.
Architect question
Should the package be split into smaller capabilities?
Lab 2 — Production drift
A developer reports that PROD contains a model definition absent from the controlled release.
Determine:
- who changed it
- why
- whether it was authorized
- whether source must be updated
- whether PROD should be restored
Lab 3 — Data validation failure
A pipeline succeeds but revenue totals differ from the source.
Investigate:
Source -> acquisition -> transformation -> semantic layer -> consumption
Do not stop at pipeline success.
Lab 4 — Slow release
The same package repeatedly requires manual fixes.
Identify missing automation and environment contracts.
Lab 5 — Recovery exercise
Define RPO, RTO, recovery steps and validation for a critical analytical product.
Architect challenge
Design a three-tenant enterprise landscape for:
- 20 data domains
- 200 developers
- regulated finance data
- daily and near-real-time pipelines
- SAC consumption
- controlled production releases
Produce:
- tenant topology
- space model
- transport route
- security model
- release gates
- monitoring
- recovery strategy
- FinOps controls