A Prism data writer has two pipelines of data that need to be joined together:•...

Comprehensive and Detailed Explanation From Exact Extract:

In Workday Prism Analytics, the requirement to keep all data from the primary pipeline (point of sale data by sales agent) and blend in matching data from the secondary pipeline (performance rating by sales agent) where it exists indicates the need for a specific type of join. According to the official Workday Prism Analytics study path documents, a Left Outer Join (option C) is the appropriate join type for this scenario. A Left Outer Join includes all rows from the primary pipeline and matches them with rows from the secondary pipeline based on the join condition (e.g., sales agent ID). If no match is found in the secondary pipeline, the fields from the secondary pipeline will have NULL values, but the primary pipeline’s data is fully retained, meeting the requirement to keep all point of sale data while blending in performance ratings where available.

The other options do not meet the requirement:

A. Inner Join: An Inner Join only includes rows where matches exist in both pipelines, which would exclude point of sale data for sales agents without performance ratings, violating the requirement to keep all primary pipeline data.

B. Right Outer Join: A Right Outer Join includes all rows from the secondary pipeline and matching rows from the primary pipeline, which prioritizes the secondary pipeline and may exclude some point of sale data, not meeting the requirement.

D. Full Outer Join: A Full Outer Join includes all rows from both pipelines, with NULLs for non-matching rows, but this is broader than the requirement, which only needs all data from the primary pipeline, not necessarily all data from the secondary pipeline.

A Left Outer Join ensures that all point of sale data is retained while blending in performance ratings where they exist, aligning with the stated requirement.