Financial Services CloudArchitect (Hardest)client-onboardingomniscripthousehold
Design client onboarding OmniScript feeding FSC Household and FA creation sequence
Real World Scenario
Digital onboarding collects KYC opens brokerage account; OmniScript must create Person Account Household FA roles without orphan records on partial failure.
Expected Answer
• Integration Procedure transaction order: Person Account then Household then FA then FA Roles
• Rollback compensation delete created records IP failure mid-chain
• External Id client onboarding Id idempotent retry safe
• OmniScript review step confirm before Load DR commit
• Action Plan spawn on successful onboarding IP completion
• Experience Cloud authenticated user linked Contact post-onboarding
• E2E test partial failure at each IP step verify no orphans
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Integration Procedure transaction order: Person Account then Household then FA then FA Roles. Rollback compensation delete created records IP failure mid-chain. Pick based on your integration pattern and team capability. Onboarding OS is ordered DML saga—IP rollback strategy mandatory before production digital open. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Onboarding OS is ordered DML saga—IP rollback strategy mandatory before production digital open.