ApexArchitect (Hardest)ldvperformanceindexing
Architect custom index strategy before LDV object reaches 10 million rows
Real World Scenario
Transaction__c at 8M rows. New reporting filters on Merchant_Id__c and Transaction_Date__c cause full table scans and timeout.
Expected Answer
• Identify filter fields in all batch, report, and integration queries
• Submit custom index request via Salesforce support before crisis
• Leading WHERE on indexed Merchant_Id__c plus Transaction_Date__c range
• Avoid OR conditions across non-indexed fields in same query
• Query Plan tool in sandbox with production-scale data clone
• Archive records older than retention to Big Object reducing hot table size
• Document selective predicate requirements for integration team
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Identify filter fields in all batch, report, and integration queries Also consider: Submit custom index request via Salesforce support before crisis In practice: Leading WHERE on indexed Merchant_Id__c plus Transaction_Date__c range Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Custom indexes take weeks—request at 1M rows when filter pattern is known, not at 10M crisis.