Tableau-Desktop-Found Connecting to and Preparing Data Practice Question
When you have a large dataset that is slow to load, what is the 'first' step you should take to improve performance in Tableau?
⚠ Common exam trap
Candidates often choose dashboard-level actions like hiding fields in the view or using quick filters, forgetting that performance optimization must happen at the data source level before data is loaded.
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
✓
Hide unused columns and apply a data source filter.
Minimizing data before it reaches the dashboard is the fundamental rule of Tableau performance. By excluding unnecessary columns and applying data source filters early, you reduce the workload on both the local environment and the underlying database. These initial steps are the most impactful, as they prevent unnecessary data from being processed and stored, leading to a much snappier user experience in the final interactive dashboards.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add a dashboard filter.
Why it's wrong here
Dashboard filters are applied after the data has already been loaded and queried. While they help with user interaction performance, they do not help with the initial load time of the workbook. You must filter at the data source level to achieve meaningful improvements in overall performance.
- ✗
Create a hide/unhide dashboard action.
Why it's wrong here
Dashboard actions are for user interactivity, not data optimization. Hiding a container on a dashboard does not prevent the underlying data from being queried when the workbook opens. To see performance gains, you must reduce the data being queried at the data connection layer, not the presentation layer.
- ✓
Hide unused columns and apply a data source filter.
Why this is correct
Hiding unused columns reduces memory consumption, while data source filters reduce the row count processed. Together, these actions drastically shrink the data footprint, leading to the fastest possible initial load times. This is the industry-standard 'first step' for any performance-tuning effort in Tableau Desktop.
- ✗
Increase the number of CPU cores on the machine.
Why it's wrong here
While hardware improvements can help, optimizing the data model is far more impactful and cost-effective. Throwing hardware at an unoptimized data model is a poor strategy. You should always ensure your data source is as lean as possible before looking to external hardware or server upgrades for performance.
About these practice questions
Courseiva writes every Tableau-Desktop-Found question from scratch — 126 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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 Tableau (Salesforce) exam blueprint
This Tableau-Desktop-Found practice question is part of Courseiva's free Tableau (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 Tableau-Desktop-Found exam.