SF-Data-Arch Large Data Volume Considerations Practice Question
Which TWO of the following are true regarding the impact of 'Formula Fields' on Large Data Volumes?
⚠ Common exam trap
Candidates often assume formula fields are stored in the database and indexed like standard fields. They fail to realize that calculations happen at runtime, forcing full table scans on large datasets.
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
✓
Filtering on formula fields causes full table scans.
Formula fields are calculated at runtime, which means their values are not stored in the database. When querying or filtering on a formula field, the system must compute the value for every record, which is computationally expensive. As the data volume grows, this causes significant performance issues because the database cannot utilize indexes on formula fields (unless they are deterministic and specifically indexed), leading to slow, resource-intensive queries.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Formula fields are indexed by default.
Why it's wrong here
Formula fields are calculated at runtime and are generally not indexed. Because their values can change based on external factors or related records, the system cannot maintain a static index on them, making queries that filter by formula fields inefficient and slow for large object datasets.
- ✓
Filtering on formula fields causes full table scans.
Why this is correct
Because formula fields are not indexed and must be calculated on the fly during a query, the Salesforce database engine must perform a full table scan to evaluate every record against the filter criteria. For objects with millions of records, this is a major performance bottleneck.
- ✗
They improve query performance by pre-calculating data.
Why it's wrong here
Formula fields do the opposite of pre-calculating; they calculate results on demand at runtime. Pre-calculating data is done through fields that are populated via Apex or Flow, allowing for indexing. Formulas add significant CPU load during query execution, which degrades performance for large datasets.
- ✗
Values are stored in the database for fast retrieval.
Why it's wrong here
Formula values are not stored in the database. They are ephemeral calculations performed in the application layer. This lack of storage is why they cannot be used in traditional database indexes, resulting in slower performance when they are used in query filters compared to standard fields.
- ✓
Complex formulas can lead to 'CPU Time Exceeded' errors.
Why this is correct
Because formulas are evaluated during record retrieval or update, highly complex nested formulas consume significant CPU time. In high-volume scenarios, the cumulative effect of evaluating these formulas across thousands of records can easily exceed the CPU governor limits, causing the entire transaction or query to fail.
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.