To improve data quality when a log contains dates written as 01/06/2024 and 2024-01-06, what issue does this illustrate?

To improve data quality when a log contains dates written as 01/06/2024 and 2024-01-06, what issue does this illustrate?

• A. Lack of standardized date formatting.
• B. Time zone inconsistency
• C. Data duplication
• D. Missing dates

Answer: (B)

The main idea here is standardized date formatting. When dates appear in different representations, the system and people reading the data can’t reliably interpret them, leading to confusion and errors in sorting, filtering, or merging records. Here, one date uses a day/month/year-style look, which can be read as either January 6 or June 1 depending on locale, while the other date uses a clear year-month-day format (ISO-like). The inconsistency in how dates are written is what harms data quality, because it introduces ambiguity and makes it hard to compare or combine entries. To fix this, adopt a single, unambiguous format across all records, such as ISO 8601 (YYYY-MM-DD). It’s also helpful to store dates as a proper date datatype rather than free-text strings and to validate inputs so new logs conform to the chosen format. This isn’t about time zones, which would involve times and offsets rather than just date notation. It also doesn’t imply data duplication or missing dates—the issue shown is the mixed formatting itself.

The main idea here is standardized date formatting. When dates appear in different representations, the system and people reading the data can’t reliably interpret them, leading to confusion and errors in sorting, filtering, or merging records.

Here, one date uses a day/month/year-style look, which can be read as either January 6 or June 1 depending on locale, while the other date uses a clear year-month-day format (ISO-like). The inconsistency in how dates are written is what harms data quality, because it introduces ambiguity and makes it hard to compare or combine entries.

To fix this, adopt a single, unambiguous format across all records, such as ISO 8601 (YYYY-MM-DD). It’s also helpful to store dates as a proper date datatype rather than free-text strings and to validate inputs so new logs conform to the chosen format.

This isn’t about time zones, which would involve times and offsets rather than just date notation. It also doesn’t imply data duplication or missing dates—the issue shown is the mixed formatting itself.