SF-Data-Arch Large Data Volume Considerations Practice Question
A large custom object has 20 million records. A SOQL query is taking too long. What should the architect evaluate first?
⚠ Common exam trap
Candidates often suggest adding more filters or changing the query syntax without checking if the fields are actually indexed, which is the root cause of performance issues.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Verify if the query filters are selective and indexed.
The architect should first inspect the query's filter criteria to determine if it is selective. If the filter is not indexed or is too broad, the system will perform a full table scan. Verifying the selectivity of the query and ensuring an index exists is the fundamental first step in optimizing performance for large data volumes within the Salesforce platform.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Check if the object has too many fields.
Why it's wrong here
Field count is rarely the cause of query performance issues on large objects. The bottleneck is almost always the database's ability to find the records requested, which is dictated by indexing and the query filter's selectivity, not the width of the table or the number of columns.
- ✓
Verify if the query filters are selective and indexed.
Why this is correct
Selectivity is the most critical factor for SOQL performance on large datasets. If the filter is not selective, the database must scan all 20 million records. Adding an index on the filter field allows the engine to jump directly to the relevant records, restoring query performance.
- ✗
Increase the organization's total storage limit.
Why it's wrong here
Increasing storage limits provides more capacity, but it does not change how existing data is indexed or queried. A query on 20 million records will be just as slow regardless of whether the org is at 10% or 90% of its total storage capacity.
- ✗
Rewrite the query to use the Data Loader API.
Why it's wrong here
The Data Loader API is for batch imports and exports, not for real-time querying in the application. Rewriting a query to use a different API does not address the core issue of an inefficient execution plan or missing indexes that are causing the latency in the first place.
About these practice questions
One of 222 original SF-Data-Arch practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.