A marketing team determines that in the future, their projects must be reviewed by the Project Sponsor before the project is closed. What is the best practice to ensure that each project is properly reviewed and approved?

The most effective and scalable best practice is to incorporate the approval process directly into the project template used by the marketing team. When a new project is created from this template, it will automatically inherit the pre-configured approval process. This ensures consistency, eliminates the need for manual setup on each project, and prevents the risk of human error where an approval might be forgotten. Triggering the approval when the project status changes to "Complete" correctly places the review step just before the project is formally closed.

A. A global approval process would apply to all projects in the system, not just those for the marketing team, making it too broad and potentially disruptive to other departments.
B. Creating a single-use approval process manually for each new project is inefficient, prone to error, and not a sustainable best practice for a recurring, standardized requirement.

1. Adobe Experience League - Create and modify project templates: "Templates are reusable frameworks that allow you to quickly create new projects... You can attach a template to a project... This includes... Approval processes." This source confirms that adding an approval process to a template is a standard function for ensuring process consistency on new projects. (See section: "Overview of project templates").

2. Adobe Experience League - Add an approval process to a template: "When you add an approval process to a template, any project created from that template automatically includes the approval process." This directly supports the chosen answer (C) as the intended method for automatically applying a standard approval to a set of future projects. (See section: "Add an approval process to a project template").

3. Adobe Experience League - Approval process overview: This document distinguishes between system-wide (global) approvals and those attached to specific objects like templates. It clarifies that global approvals are for processes that must apply to all items of a certain type in the system, which is not the requirement here, thus invalidating option A. (See section: "Associate a new or existing approval process with work").