Which of the following is not true when using the Resources filesystem?

• A. Data can be used by any workspace, without having to upload it every time
• B. Data can be stored locally (to the FME Flow Engines), even when access to the operating system's filesystem is restricted by an FME Flow Administrator
• C. System cleanup will regularly clean the Data folder to free up space
• D. A Resources folder can be mapped and shared among many users as a physical drive

Answer: (C)

The Resources filesystem provides a centralized, shared place for data and resources that multiple workspaces can access without re-uploading. This means data stored in Resources can be used by any workspace that references it, simplifying reuse across projects. It can also live on the Flow Engines themselves, so even if access to the operating system’s filesystem is restricted by an administrator, the data remains accessible to the engine where the workflow runs. Additionally, a Resources folder can be mapped as a network drive and shared among many users, enabling collaborative access and convenient distribution of data.

The statement about the system regularly cleaning the Data folder isn’t accurate. The Resources data is not a temporary scratch area that is automatically purged; data persists unless an administrator or a policy removes it, or a retention/quotas mechanism is configured to trigger cleanup.