Tableau-Desktop-Found Connecting to and Preparing Data Practice Question
When connecting to a flat file, you notice that Tableau is interpreting a 'Date' column as a String. Which action should you take to ensure the field is recognized correctly for time-series analysis?
⚠ Common exam trap
Candidates frequently attempt to create a calculated field using DATEPARSE or DATE() functions instead of simply changing the metadata type, which is unnecessary and prone to syntax errors.
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
✓
Click the data type icon in the Data Source tab and change it to Date
Changing the data type is a fundamental step in data preparation. Tableau's ability to create hierarchies and perform date-part aggregations relies on the field being recognized as a date. If the data type remains a string, you lose the ability to use continuous date axes or drill-down functionality, which are essential for visualizing trends over time and performing accurate year-over-year or month-over-month comparisons.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a calculated field using the DATE() function
Why it's wrong here
While this method works, it is unnecessarily complex for a simple data type mismatch. You should first attempt to change the type directly in the data source tab, as creating unnecessary calculated fields can impact workbook performance and increase maintenance overhead for other developers on the team.
- ✓
Click the data type icon in the Data Source tab and change it to Date
Why this is correct
This is the most efficient and direct way to resolve data type issues. By modifying the metadata in the Data Source tab, you inform Tableau how to interpret the underlying values, enabling automatic date recognition and unlocking advanced date functions without needing complex formulas or transformations.
- ✗
Split the column into Year, Month, and Day segments
Why it's wrong here
Splitting a date into separate columns creates redundant data and complicates future analysis. You would then need to manually concatenate or parse them back into a valid date format, which is prone to errors and prevents you from utilizing Tableau's native date intelligence features effectively.
- ✗
Filter the data to remove non-date entries
Why it's wrong here
Filtering does not change the data type of the column. Even if you remove invalid entries, Tableau will still treat the remaining data as a string until you explicitly change the metadata definition in the data source configuration to a date format to enable date functions.
About these practice questions
This Tableau-Desktop-Found question is part of Courseiva's 126-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 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.