Salesforce ArchitectureAdvanceddata-modelstandard-objectscustomization
Architect data model strategy for custom objects vs standard
Real World Scenario
Implementation team proposes 40 custom objects duplicating Account Contact Opportunity patterns for subsidiary business line.
Expected Answer
• Prefer standard objects for CRM semantics: sales, service, marketing clouds alignment
• Custom objects when domain not modeled: industry-specific entities
• Evaluate Big Objects for append-only high-volume logs
• External objects for reference data virtualization
• Object count and relationship complexity impact sharing and reporting
• Enterprise data dictionary governing new object approval
• Extension via record types and fields before new objects
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Prefer standard objects for CRM semantics: sales, service, marketing clouds alignment. Custom objects when domain not modeled: industry-specific entities. Pick based on your integration pattern and team capability. Object sprawl increases TCO exponentially—architects challenge every new object with standard object fit analysis. Optimize for scale and operational observability.
Architect Perspective
Object sprawl increases TCO exponentially—architects challenge every new object with standard object fit analysis.