DA0-002 Data Acquisition and Preparation 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.

• ✓

  CONCAT()

  Why this is correct

  CONCAT() joins two or more string values into one, directly satisfying the requirement to merge first_name and last_name into a full_name column. Unlike the concatenation operator, it handles NULL inputs by treating them as empty strings, avoiding a NULL result when either name column is missing.

• ✗

  UPPER()

  Why it's wrong here

  UPPER() converts characters in one string to uppercase; it returns a single transformed value and cannot join two columns. It is tempting because it is a common string function applied to name data, and would be correct when the requirement is to normalise casing, such as displaying a surname in capitals.

• ✗

  LENGTH()

  Why it's wrong here

  LENGTH() returns the character count of a single string, so it cannot join first_name and last_name. It is tempting because it is a genuine string function, and it would be correct for validating field sizes or filtering rows by name length, but concatenation requires CONCAT() or the || operator.

• ✗

  SUBSTRING()

  Why it's wrong here

  SUBSTRING() extracts a portion of one string using start and length positions; it cannot concatenate two columns. It is tempting because it manipulates string data and would be correct when the requirement is to pull a fixed segment, such as the first three characters of a code, from a single column.