UiPath-ADPv1 Advanced Data Manipulation Practice Question
An automation developer is building a UiPath workflow that reads a CSV file with thousands of rows using the 'Read CSV' activity. The 'Delimiter' property is left at its default. The CSV file uses semicolons as separators, and the first row contains column headers. After reading, the DataTable has only one column containing the entire row content. What is the most likely cause?
⚠ Common exam trap
The trap here is assuming that the 'Read CSV' activity automatically detects delimiters, when it actually relies on the explicitly configured 'Delimiter' property.
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
✓
The 'Delimiter' property must be set to a semicolon (";") to correctly parse the file.
The 'Read CSV' activity uses a comma as the default delimiter. When the file uses semicolons, the activity fails to split columns, resulting in a single column containing the entire line. Setting the 'Delimiter' property to a semicolon resolves the issue. This is a common configuration oversight when working with regional CSV formats.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The 'ColumnNames' property must be set to the first row index to use headers.
Why it's wrong here
The 'Read CSV' activity automatically uses the first row as headers by default when 'Include Column Names' is checked. Setting 'ColumnNames' to a row index is not a valid property configuration; the property is a boolean. Even if headers were misconfigured, it would not cause all data to appear in one column. This option misidentifies the root cause.
- ✗
The file encoding is incorrect, causing the parser to merge all columns.
Why it's wrong here
Encoding issues typically produce garbled characters or missing characters, not a consistent single-column result. The parser merges columns when the delimiter does not match the file's actual separator. While encoding can affect special characters, it does not cause the entire row to be read as one field. Thus, this option is not the primary cause here.
- ✗
The 'Read CSV' activity cannot handle files with more than 1000 rows.
Why it's wrong here
The 'Read CSV' activity has no hard row limit; it can process very large files, though memory usage increases. The symptom of a single column indicates a delimiter mismatch, not a row limit. The activity is designed for large datasets, and the issue described is unrelated to the number of rows. Therefore, this option does not explain the observed behavior in the scenario.
- ✓
The 'Delimiter' property must be set to a semicolon (";") to correctly parse the file.
Why this is correct
The 'Read CSV' activity defaults to a comma delimiter. Since the file uses semicolons, the parser treats each entire line as one field, resulting in a single column. Setting the 'Delimiter' property to ";" allows the activity to split columns correctly. This is the direct cause of the issue and the appropriate fix for the scenario.
Visual reference
About these practice questions
This UiPath-ADPv1 question is part of Courseiva's 276-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 UiPath exam blueprint
This UiPath-ADPv1 practice question is part of Courseiva's free UiPath 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 UiPath-ADPv1 exam.