How can the developers add new fields while keeping the dataset refreshed?

A team of CRM Analytics developers has been working on an existing recipe to add new derived fields. The edited version has been failing ever since, and management is requesting that the dashboard show refreshed data while they work on the edits.

How can the developers add new fields while keeping the dataset refreshed?
A . A recipe for the new fields and when that is successful, add it to the existing recipe as a join node.
B . Clone the existing recipe to add fields and roll back the original recipe to the last working version.
C . Refresh the dataset after working hours to avoid the edited version from failing.

View Answer

Answer: B

Explanation:

When faced with the need to continue refreshing data while developing new features in a recipe, the best practice is:

Clone the Existing Recipe: By cloning the recipe, developers can experiment with adding new fields and transformations without affecting the production data flow. This allows for testing and development in a sandbox-like environment.

Roll Back to a Stable Version: Rolling back the original recipe to the last stable version ensures that the production dashboards continue to receive refreshed data, maintaining business operations without disruption.

This approach not only ensures data continuity but also provides a safe environment to address any

issues that may arise from new developments.