An analyst is cleaning employee contact data collected from multiple regional systems. The phone number field appears as 555-123-4567, (555) 123-4567, or +1 555 123 4567. The analyst needs to unify these values into a single standardized format but also keep a way to verify the original entries if the help-desk reports mismatches later. Which data-transformation approach best meets both requirements?
Store the reformatted numbers in a new column alongside the existing column
Keep the original data but adjust parts of the numbers step-by-step
Replace the original records while reformatting numbers
Reformat phone numbers at the end of the pipeline and discard raw data
Placing the reformatted version in a separate column helps preserve the initial data for verification or troubleshooting. Overwriting existing data removes the ability to compare older data with the new standardized formats. Delaying transformations to a later stage can cause misaligned information if earlier operations rely on consistent formats. Splitting transformations in steps may produce inconsistent data if partial changes happen multiple times.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why is it important to preserve the original data when reformatting phone numbers?
Open an interactive chat with Bash
What are some common methods to store the reformatted data alongside the original?
Open an interactive chat with Bash
How does reformatting at the end of the pipeline pose risks to data consistency?