DA0-002 Data Acquisition and Preparation Practice Question
A financial analyst is integrating data from multiple stock exchanges. One exchange provides trade timestamps in UTC, another in Eastern Time. The analyst needs accurate time synchronization for time-series analysis. What is the best approach?
⚠ Common exam trap
The trap here is that candidates might think adding a timezone offset column preserves information and is sufficient, but it still requires runtime conversion and can be error-prone with DST; the exam expects recognition that normalization to UTC during ETL is the best practice for time-series analysis.
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
✓
Convert all timestamps to a single timezone (e.g., UTC) during ETL
Converting all timestamps to a single timezone (e.g., UTC) during ETL ensures that all time-series data is directly comparable and sortable without ambiguity. UTC is a global standard that avoids daylight saving time (DST) shifts, making it ideal for financial analysis where precise ordering of trades across exchanges is critical. This approach eliminates the need for runtime timezone conversions, reducing errors and improving query performance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Keep original timezones and add a timezone offset column
Why it's wrong here
Keeping original timezones plus an offset column leaves timestamps on different axes, so sorting and joining require applying offsets at every query and errors persist across daylight saving changes. Offset columns suit display or audit purposes; converting all timestamps to UTC is the correct approach for synchronised analysis.
- ✗
Use the local time of the analyst's location
Why it's wrong here
Converting timestamps to the analyst's local time introduces an arbitrary third offset unrelated to either exchange, so ordering across sources stays inconsistent and shifts with daylight saving. Local time suits single-region reporting; normalising every source to UTC is the correct approach for synchronised time-series analysis.
- ✓
Convert all timestamps to a single timezone (e.g., UTC) during ETL
Why this is correct
Normalising every timestamp to a single timezone such as UTC during ETL removes the offset ambiguity between exchanges, so time-series joins and orderings align correctly. Converting at load time, not query time, satisfies the accurate time synchronisation constraint for analysis.
- ✗
Ignore timezone differences if analysis is intraday
Why it's wrong here
Ignoring timezone differences misaligns trades from the two exchanges, so intraday ordering and cross-exchange correlation break whenever their offsets diverge, including daylight saving shifts. Ignoring offsets only works when every source already shares one timezone; normalising all timestamps to UTC is the correct approach.
Go deeper
Related to this question
About these practice questions
One of 1,004 original DA0-002 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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 CompTIA exam blueprint
This DA0-002 practice question is part of Courseiva's free CompTIA 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 DA0-002 exam.