Which of the following Cisco UCS Director Orchestrator components are stateful processes that are created when a workflow executes?

Explanation

Cisco Unified Computing System (UCS) Director Orchestrator service requests are stateful processes that are created when a workflow executes. Cisco UCS Director uses hardware abstraction to convert hardware and software into programmable actions that can then be combined into an automated custom workflow. Cisco UCS Director Orchestrator is the Cisco UCS Director engine that enables this automation.
Service requests are Cisco UCS Director processes that can exist in one of several states. For example, a service request that has not run yet might exist in a scheduled state. A service request that has been successfully executed exists in a completed state. A service request that was attempted but not successfully executed might exist in a failed state.
Tasks are best described as the atomic units of work in Cisco UCS Director Orchestrator. A task is a single action and is therefore the smallest unit of work. A workflow is a series of tasks; it is a container that defines the order in which tasks should be performed. However, it is possible for a workflow to contain a single task. Workflows can be created and deployed from workflow templates.
Approvals are points in a workflow that require user intervention. For example, a service request might exist in a blocked state if the request cannot complete until an administrator approves the service request. Approvals enable administrators to provide input values that can affect the product of a given workflow.
Rollbacks can be used to undo the results of workflows. For example, a workflow that creates unintended objects or components in a system can be rolled back so that those objects or components are removed. Cisco UCS Director Orchestrator rollbacks are different from relational database rollbacks in that they are not transactional. Instead, tasks in the workflow are executed in reverse order when a workflow is rolled back.