Which option is NOT one of the three workflows described for displaying a column from a non-Base Master File?

Which option is NOT one of the three workflows described for displaying a column from a non-Base Master File?

• A. Create a new custom report separate from the template.
• B. Add a parameter to the Query Template that searches the non-Base Master File.
• C. Add a linkage record to the display column.
• D. Add a Setup Data Extension to the template that tells it how to link to other master files.

Answer: (A)

The key idea is how a template accesses and displays data from a non-Base Master File through its built-in integration points. You can extend the template by adding a parameter to the Query Template so it can search that non-base file, allowing the template to pull the needed field. You can also connect the display column to the related data by adding a linkage record, which wires the column to the corresponding master file data. Another route is to provide a Setup Data Extension that tells the template how to link to other master files, configuring cross-file relationships the display relies on. Creating a new custom report separate from the template wouldn’t use these integration methods; it would be a standalone report rather than configuring the template to access and show the non-base Master File’s column. So that option isn’t one of the described workflows.

The key idea is how a template accesses and displays data from a non-Base Master File through its built-in integration points. You can extend the template by adding a parameter to the Query Template so it can search that non-base file, allowing the template to pull the needed field. You can also connect the display column to the related data by adding a linkage record, which wires the column to the corresponding master file data. Another route is to provide a Setup Data Extension that tells the template how to link to other master files, configuring cross-file relationships the display relies on. Creating a new custom report separate from the template wouldn’t use these integration methods; it would be a standalone report rather than configuring the template to access and show the non-base Master File’s column. So that option isn’t one of the described workflows.