If a workspace's source data is likely to change in the future, which upload method should be used?

• A. Publish the data to an FME Flow repository, along with the workspace
• B. Publish the data to the Resources folder, separate from the workspace
• C. Publish to a remote Google Drive folder
• D. Publish as a single ZIP file to a repository

Answer: (B)

Keeping the source data separate from the workspace is important when the data is expected to change. Publishing the source data to the Resources folder, separate from the workspace, lets the workspace reference the data without bundling it in with the workspace itself. When the data updates, you can swap or refresh the files in the Resources area without needing to republish the entire workspace, making maintenance faster and reducing the risk of breaking the workflow.

Publishing the data together with the workspace ties the two together, so any data change would typically require republishing a new package, adding overhead. Using a remote Google Drive folder introduces external dependencies and potential access or latency issues, which is less reliable for production pipelines. Publishing as a single ZIP file combines data and workspace into one bundle, making incremental data updates cumbersome.