Transformation & aggregation — quiz
8 questions covering this module. Joining, concatenating, grouping, pivoting.
To build a LEFT JOIN in the Joiner, include:
- Matching rows only
- Matching rows and left unmatched
- All three outputs
- Right unmatched only
Answer: Matching rows and left unmatched — Left unmatched are the rows with no partner.
Output rows exceed the left input. Cause?
- A bug
- Duplicate keys on the right side
- Missing values
- Wrong column types
Answer: Duplicate keys on the right side — GroupBy the right branch by the key first.
Concatenating two tables fails on duplicate row keys. Fix:
- Rename columns
- Let the node append a suffix or generate new RowIDs
- Use the Joiner
- Sort first
Answer: Let the node append a suffix or generate new RowIDs — KNIME requires unique RowIDs.
Column Appender matches rows:
- On a key column
- By row position
- Alphabetically
- By RowID only
Answer: By row position — Which is wrong unless the tables are genuinely parallel.
After GroupBy, downstream nodes cannot find "Revenue". Why?
- It was dropped
- It was renamed to Sum(Revenue) by default
- Wrong type
- It became a RowID
Answer: It was renamed to Sum(Revenue) by default — Set naming to keep original names.
Which node gives a running total?
- GroupBy
- Moving Aggregation after a Sorter
- Pivoting
- Column Appender
Answer: Moving Aggregation after a Sorter — It depends on row order, so sort first.
Which node converts month columns into month rows?
- Pivoting
- Unpivoting
- GroupBy
- Concatenate
Answer: Unpivoting — Unpivoting is the wide-to-long direction.
Why can a workflow break after a Pivoting node?
- It is slow
- New data values create new columns, changing the schema
- It loses rows
- It requires sorting
Answer: New data values create new columns, changing the schema — Reference columns by pattern rather than by name.