How do you approach designing a lead data governance architecture for a multi-tenant enterprise environment?
For the SQL implementation, produce a tenant-level governance view that identifies consent coverage, latest quality failures, duplicate lead groups, and missing policy coverage.
tenant_name, active_leads, consented_active_leads, consent_rate_pct, failed_latest_quality_leads, duplicate_email_groups, governance_status.tenant_id ascending. Treat only the most recent consent and quality event for each lead as current.| Column | Type | Description |
|---|---|---|
| tenant_idPK | INT | Tenant identifier |
| tenant_name | VARCHAR(100) | Tenant display name |
| region | VARCHAR(30) | Tenant operating region |
| Column | Type | Description |
|---|---|---|
| lead_idPK | INT | Lead identifier |
| tenant_id | INT | Owning tenant identifier |
| VARCHAR(255) | Lead email address | |
| lead_status | VARCHAR(20) | Current lead lifecycle status |
| created_at | DATE | Lead creation date |
| Column | Type | Description |
|---|---|---|
| consent_idPK | INT | Consent event identifier |
| lead_id | INT | Related lead identifier |
| consent_status | VARCHAR(20) | Consent decision |
| recorded_at | TIMESTAMP | Consent event timestamp |
| Column | Type | Description |
|---|---|---|
| quality_event_idPK | INT | Quality event identifier |
| lead_id | INT | Related lead identifier |
| quality_status | VARCHAR(20) | Quality validation result |
| checked_at | TIMESTAMP | Quality check timestamp |
| Column | Type | Description |
|---|---|---|
| policy_idPK | INT | Policy identifier |
| tenant_id | INT | Policy tenant identifier |
| policy_version | VARCHAR(20) | Policy version label |
| effective_from | DATE | Policy effective date |
| is_active | BOOLEAN | Whether the policy is active |