Following best practices for workflow implementation is crucial for maintaining the performance and stability of the Adobe Campaign Classic platform. Purging logs (A) is essential for database health, preventing tables from growing excessively and slowing down the system. Avoiding paused workflows (C) is critical because they hold onto database connections and temporary resources, which can lead to performance degradation over time. Finally, scheduling workflows with a reasonable frequency, such as not more than every 15 minutes (D), prevents system overload from constant, resource-intensive processes, ensuring the platform remains responsive for all operations.

B. Checking the ‘Keep Interim Results’ option is a debugging tool, not a best practice. It consumes significant temporary disk space and should be disabled for production workflows to conserve resources and improve performance.

1. Adobe Experience League - Campaign Classic v7 Documentation - Workflow best practices: This document explicitly advises on several key practices.

For option A & C: Under the "Recommendations" section

it states

"Purge the logs and the history" and "Avoid leaving workflows in a paused state for too long as it can overload the database."

For option D: The same section advises

"Plan the execution of the most resource-intensive workflows during off-peak hours to avoid slowing down the entire platform." This supports the principle of careful scheduling to manage system load

making "not more than every 15 minutes" a valid best practice guideline.

2. Adobe Experience League - Campaign Classic v7 Documentation - Workflow properties: This page details the workflow execution properties.

For option B: In the "Execution" section

it describes the option "Keep the result of interim populations". It is noted that this option is useful for debugging but consumes considerable disk space

reinforcing that it is not a standard best practice for production workflows.

3. Adobe Experience League - Campaign Classic v7 Documentation - Database cleanup workflow: This document details the importance of data retention management.

For option A: The "Introduction" section explains that the cleanup workflow's purpose is to delete obsolete data to "avoid exponential growth of the database" and maintain performance

which directly supports the practice of purging logs.