SF-Data-Arch Salesforce Data Management Practice Question
A company is experiencing slow performance on reports that join multiple objects with millions of records. What architectural change should the Data Architect propose first to improve report performance?
⚠ Common exam trap
Candidates often jump to complex solutions like data warehousing or changing the data model, ignoring that simple custom indexing on report filter fields is the most effective initial step.
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
✓
Request custom indexes for the fields used in report filters.
Indexing is the most fundamental way to improve database performance for filtering and joining large datasets. In Salesforce, ensuring that fields used in report filters and custom indexes are properly configured is the first step. If standard indexing is insufficient, the architect may consider custom indexes or denormalizing the data model. This approach is far less intrusive and more cost-effective than re-architecting the entire data model or moving data to an external warehouse.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Switch to an external reporting tool like Tableau or Power BI.
Why it's wrong here
While external tools are great for advanced analytics, they are not a replacement for native report performance issues. If the underlying data structure is not optimized, the external tool will also experience slow query times. The architect must first optimize the data within Salesforce before adding layers of complexity.
- ✓
Request custom indexes for the fields used in report filters.
Why this is correct
Custom indexes significantly speed up database queries by allowing the query optimizer to quickly find records matching filter criteria. This is the recommended first step when standard reports slow down due to large data volumes, as it directly addresses the inefficiency of full table scans during the reporting process.
- ✗
Force all users to use the Reporting Snapshot feature instead of live reports.
Why it's wrong here
Reporting snapshots are for point-in-time trend analysis, not for general reporting. They do not resolve the performance issues of live reports, as they only capture summary data. Forcing users to snapshots would restrict their ability to drill down into operational details, which is a requirement for most reporting needs.
- ✗
Convert all report types to be 'Joined Reports' to reduce data loads.
Why it's wrong here
Joined reports do not inherently improve performance; in some cases, they can make it worse by requiring multiple separate queries to be combined at the application level. They are intended for multi-block data views, not as an optimization strategy for queries that are already struggling with large record volumes.
About these practice questions
This SF-Data-Arch question is part of Courseiva's 222-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.