Which three workflows are used to display a column from a non-Base Master File?

• A. Add a parameter to the Query Template; Add a linkage record to the display column; Add a Setup Data Extension to the template.
• B. Add a parameter only; Add a linkage; None.
• C. All three require coding in M.
• D. Use a separate report outside the template.

Answer: (A)

Displaying a column from a non-base Master File hinges on three configuration steps that work together. First, adding a parameter to the Query Template lets the template receive which external column to display, making the template flexible to different data inputs. Second, establishing a linkage record for the display column creates the explicit connection between the template’s data flow and the non-base Master File, so the system knows how to pull that column’s data in context. Third, configuring a Setup Data Extension within the template provides the actual data source and metadata that supply the column’s content, enabling the display to render correctly even though the data isn’t in the Base Master File. Together, these steps allow dynamic selection, proper association, and data provisioning for the non-base column.

The other options don’t fit because adding only a parameter misses the essential connection and data provisioning, and claiming that coding in M is required goes against the typical admin workflow which relies on configuration rather than programming. Using a separate report outside the template would not display the column within the intended template environment.