Design a data platform enablement
Design a Cloud Data Platform for a Mid-Tier Retail Bank
Design a pragmatic data platform enablement for a mid-tier retail bank that is migrating its operations to the cloud. This platform must strictly adhere to PII (Personally Identifiable Information) and data-residency constraints.
Your design should encompass the target architecture, detailing the following components and aspects:
-
Architectural Components:
- Data Ingestion
- Data Storage
- Data Governance
- Data Transformation
- Data Consumption
-
Specific Design Aspects:
- Data contracts
- Data lineage
- Access patterns
- Service Level Agreements (SLAs) and Service Level Objectives (SLOs)
- Partitioning strategy
- Handling of backfill and late-arriving data
- Cost guardrails
-
Implementation Plan:
- A 3-wave rollout plan, including success metrics for each wave.
- Identify one specific component or feature you would deliberately postpone, providing a clear justification for this decision.
AI interview prep
Core dilemma
Balancing the agility and scalability benefits of cloud data platforms with stringent regulatory compliance (PII, data residency), security, and the operational rigor required for a financial institution, all while managing costs and ensuring a pragmatic, phased rollout.
3 tradeoffs and 3 stress tests locked
Interview prep
Unlock the interviewer X-Ray rubric, tradeoff matrix, stress tests, clarifying questions, and key concepts.
Design a data platform enablement
Design a Cloud Data Platform for a Mid-Tier Retail Bank
Design a pragmatic data platform enablement for a mid-tier retail bank that is migrating its operations to the cloud. This platform must strictly adhere to PII (Personally Identifiable Information) and data-residency constraints.
Your design should encompass the target architecture, detailing the following components and aspects:
-
Architectural Components:
- Data Ingestion
- Data Storage
- Data Governance
- Data Transformation
- Data Consumption
-
Specific Design Aspects:
- Data contracts
- Data lineage
- Access patterns
- Service Level Agreements (SLAs) and Service Level Objectives (SLOs)
- Partitioning strategy
- Handling of backfill and late-arriving data
- Cost guardrails
-
Implementation Plan:
- A 3-wave rollout plan, including success metrics for each wave.
- Identify one specific component or feature you would deliberately postpone, providing a clear justification for this decision.