To ensure that changes to global data pipeline parameters are deployed and the data remains consistent, which action is required?

• A. Simply save them; no further action needed.
• B. Updates take effect automatically on the next run.
• C. Reset the data warehouse and activate functional areas so changes take effect on the next pipeline run.
• D. Publish changes to stakeholders for manual execution.

Answer: (C)

When you change global data pipeline parameters, the runtime environment needs to reload its configuration to apply those changes and keep data consistent. The engine often caches parameter definitions and module metadata, so simply saving the changes doesn’t guarantee that the next run will use the updated values. Resetting the data warehouse clears those caches and reinitializes the metadata, ensuring a clean slate. Activating functional areas then loads the updated components so the next pipeline run uses the new parameters. This combination ensures the changes are fully deployed and consistently applied. Simply saving, or relying on automatic changes at the next run, or asking others to execute changes manually do not provide that guaranteed, synchronized deployment.