Correct Answer:
Explanation/Reference:
Note:
* (box 1) Step 1: Plan your deployment.
Plan Your Orchestrator Deployment
Step 2: Review the system prerequisites.
Step 3: Install Orchestrator.
Step 4: Perform post-installation tasks.
Includes:
Install an Integration Pack
* Activities that make up a service request can be mapped to runbook activities, which in turn are mapped to an Orchestrator runbook. For example, the parameters that are necessary for a custom start activity to invoke a runbook in Orchestrator, such as a computer name, can go into as Service Manager as objects. You start this process by importing runbook objects into the Service Manager database using an Orchestrator connector (box 2).
* You can implement a new request offering using an Orchestrator runbook to automate it. Then, you can go to the Runbooks view in the Library workspace, select a runbook, and create a runbook automation activity template (box 3). You can go to the templates view and verify that the template is created. You can then add the Orchestrator activity template to a service request template (box 4) and create the request offering (box 5).
Reference: How to Create a Runbook Automation Activity Template
