Within SAS Data Integration Studio, automatic mappings are disabled for a job. A transformation has defined source columns and defined target columns. One of the source columns, named COL1, is…

Question

Options

• AThe COL1 columns are successfully mapped, one-to-one, with no warnings.
• BThe COL1 columns are not mapped because the lengths are different.
• CThe COL1 columns are mapped but an expression is defined for the target COL1 that uses a
• DThe COL1 columns are successfully mapped, one-to-one, but a warning occurs.

• A
  2% (1)
• B
  5% (3)
• C
  2% (1)
• D
  92% (55)

Explanation

When two columns share the same name and data type, SAS Data Integration Studio will map them regardless of length differences - the mapping succeeds. However, because the target column (length 25) is shorter than the source (length 50), SAS generates a warning to alert you that data truncation may occur at runtime, making D correct.

Why the distractors are wrong:

• A is wrong because the length mismatch does trigger a warning - it's not silent.
• B is wrong because SAS doesn't block same-type mappings over length differences; type incompatibility (e.g., char vs. numeric) would prevent mapping, not length.
• C is wrong because SAS does not automatically inject a truncation expression (like SUBSTR) into the mapping - it simply maps and warns.

Memory tip: Think type = gate, length = flag. Different types block the mapping entirely; different lengths let it through but raise a yellow warning flag. Same name + same type = always maps, but size mismatches earn a caution notice.

No community discussion yet for this question.