SF-Data-Arch Data Modeling and Database Design Practice Question
Which indexing strategy is best to improve performance for queries on a field used in multiple filters?
⚠ Common exam trap
Test-takers frequently select standard indexing or search optimization features instead of recognizing that custom indexes are required for multi-filter query performance improvements.
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
✓
Create a custom index
Custom indexes are necessary when standard indexing is insufficient for complex filtering. By creating a custom index on high-cardinality fields used in 'WHERE' clauses, the optimizer can skip full table scans, drastically reducing query time. This is critical in large data volumes where even a small performance improvement in query speed can make the difference between a successful report and a timeout failure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a formula field
Why it's wrong here
Formula fields are calculated at runtime and cannot be indexed unless they are specifically designated as 'unique' and 'external ID' or indexed via a special request. Even then, they are inefficient compared to a native custom index on a standard data field, making this a poor performance strategy.
- ✓
Create a custom index
Why this is correct
Custom indexes on high-cardinality fields directly address performance issues by allowing the query engine to pinpoint records without a full table scan. This is the optimal way to handle frequently filtered data, ensuring that queries remain performant even as the volume of records in the database grows.
- ✗
Use a text area field
Why it's wrong here
Text area fields (long or rich) are not indexable. Attempting to query or filter on these fields will force a full table scan, which is the worst-case scenario for performance. This strategy would actively degrade the system's responsiveness, especially in an environment with high record volume.
- ✗
Use a standard lookup
Why it's wrong here
Standard lookup fields are automatically indexed, but if the field is not a lookup, you cannot simply change it to one to gain an index. You must explicitly create a custom index if the field type is not one that Salesforce indexes by default, such as a plain text field.
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.