Is it recommended to reuse an existing network parameter to add columns from a non-base master file?

• A. Yes, always reuse existing network parameter
• B. Only if the template is small
• C. No, not recommended because all reports must use the parameter
• D. Only if the network is offline

Answer: (C)

The idea being tested is maintaining consistent data sourcing across all reports. Reusing an existing network parameter to add columns from a non-base master file undermines that consistency. When every report is required to use the same parameter, there’s a single, predictable path for where data comes from, how it’s joined, and how columns are interpreted. Introducing columns from a non-base master file through a reused parameter can create mismatches in data structure, mapping, and governance, making maintenance harder and reports less reliable. That’s why it’s not recommended: all reports should use the designated parameter to ensure uniformity and traceability.

Options that suggest reusing the parameter in certain conditions or based on template size or network status don’t address the underlying need for standardized reporting data sources, so they’re not appropriate.