UiPath-ADAv1 Files, Folders, and Data Manipulation Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Use the Write Range activity inside an Excel Application Scope to write the DataTable to a specified sheet.

  Why this is correct

  Write Range within an Excel Application Scope writes a DataTable directly to a worksheet, mapping columns and rows automatically. It preserves the DataTable's column structure and writes values to the target sheet starting at the specified cell. This is the standard UiPath approach for exporting a transformed DataTable to Excel while maintaining its schema.

• ✗

  Use Write CSV instead of Write Range to ensure Excel compatibility.

  Why it's wrong here

  Write CSV produces a delimited text file, not an Excel workbook, so it does not meet the requirement of creating a new Excel file with preserved structure. CSV also loses type information entirely, storing everything as text. It is the wrong output format when the target is an .xlsx workbook.

• ✓

  Ensure the DataTable columns have the correct data types before writing, using Build Data Table or casting during transformation.

  Why this is correct

  Excel cells are loosely typed, but DataTable columns carry explicit types such as Int32 or DateTime. If transformations produce incorrect types, values may be written as text or cause errors. Ensuring correct column types before writing preserves numeric and date semantics when the data lands in Excel, which directly supports the requirement to preserve data types.

• ✗

  Delete all columns from the DataTable before writing to avoid schema conflicts.

  Why it's wrong here

  Removing columns would eliminate the data the automation is meant to export and directly contradicts the goal of preserving column structure. There is no schema conflict that requires deleting columns when using Write Range. This action would produce an empty or meaningless output file.

• ✗

  Convert the DataTable to a JSON string and write it into a single Excel cell.

  Why it's wrong here

  Serializing the DataTable to JSON and placing it in one cell destroys the tabular structure, so columns and rows are no longer individually addressable in Excel. This defeats the purpose of preserving column structure and makes downstream Excel-based reporting impossible. It is not an appropriate export strategy for a workbook that others will consume.