You administer a Forefront Identity Management (FIM) 2010 server in your company network. You create a FIM e-mail template of the Complete type. You need to configure a workflow activity that uses…

An Authorization workflow is required because it is the workflow type that processes approval and denial decisions; when a request is rejected within this workflow, it can trigger notification activities such as sending a denial email to the requester.

An Action workflow executes after a request is approved and committed, not during the authorization/denial phase, so it cannot be used to send notifications when a request is rejected.

Changing the template type to 'Approval' is incorrect because the Approval type is used for pending approval requests sent to approvers, not for notifying users that their request was denied.

The email template must be changed to the 'Denied' type because FIM 2010 email templates are categorized by purpose, and only a Denied-type template is appropriate for rejection notifications - the 'Complete' type is used for successful completions and cannot be used in denial notification scenarios.

Creating a new set and including the template is not a required or valid step for configuring denial notification workflows in FIM 2010; email templates are referenced directly in workflow activities, not through sets.

Adding the template to the 'All Email Templates' set as a manually managed member is not a configuration requirement for using a template in a workflow activity; templates are referenced directly by the notification activity, not via set membership.