Workday Report Writer Practice Test

When two data sets are joined, the relationship between them determines how rows combine. If the join uses keys that aren’t unique or the wrong type of join for the data’s real relationship, rows multiply. A single row from one side can match several rows on the other side, so the same item appears multiple times in the results—duplicates become the clear symptom. For example, joining a customer to their orders on customer_id will naturally produce multiple rows for customers with multiple orders, which is expected; but when the intention is a single-row view per entity, those extra rows signal an improper join. Latency might increase as data volume grows, but that isn’t the defining symptom, and the result shape will change (duplicates surface) rather than staying the same.