Financial Services CloudArchitect (Hardest)integrationbankingcustodian
Architect FSC integration with core banking and custodian systems
Real World Scenario
Nightly batch loads 2M position records from custodian into FSC while advisors need intraday balance for client calls.
Expected Answer
• Define freshness SLA: positions nightly balances hourly if API available
• Staging objects for custodian feed validation before FA update
• External ID on Financial Account and Securities for idempotent upsert
• Error quarantine bad rows without failing entire batch
• Intraday cache Platform Cache or Data Cloud CI for hot balances
• Reconciliation report custodian total vs FSC aggregated AUM
• Async processing never synchronous custodian callout on record page load
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Define freshness SLA: positions nightly balances hourly if API available. Staging objects for custodian feed validation before FA update. Pick based on your integration pattern and team capability. Custodian integration is batch-first—architect intraday subset not full portfolio sync per page view. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Custodian integration is batch-first—architect intraday subset not full portfolio sync per page view.