ApexAdvancedldvbig-objectsarchive
Handle Big Object ingestion from Apex for audit and telemetry archive
Real World Scenario
Api_Log__c at 20M rows degrades org performance. Architecture mandates Big Object archive with Apex write path from API gateway.
Expected Answer
• Define Big Object Api_Log_Archive__b with index on Request_Date__c
• Async Apex inserts to Big Object—cannot DML Big Object synchronously in all contexts
• Query Big Object only by indexed fields; no full scan for UI
• Batch purge Api_Log__c after successful Big Object write confirmation
• Big Object query for compliance export via batch CSV generation
• Test Big Object DML in scratch org with Big Object defined
• Document 7-day async indexing delay for Big Object queries
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Define Big Object Api_Log_Archive__b with index on Request_Date__c. Async Apex inserts to Big Object—cannot DML Big Object synchronously in all contexts. Pick based on your integration pattern and team capability. Big Objects are archive not operational store—design read paths before write migration. Optimize for scale and operational observability.
Architect Perspective
Big Objects are archive not operational store—design read paths before write migration.