C1000-132 · Question #43
Drag and Drop Question What is the appropriate order of phases in order to create a workflow process? Answer:
The correct answer is Create the process.; Validate the process.; Enable the process.; Activate the process.. Workflow Process Creation: Correct Phase Order The four phases follow a logical build → verify → prepare → deploy progression. Each phase gates the next - you cannot skip ahead without completing the prior step. --- 1. Create the process (Build it) Why first: You must define and
Question
Exhibit
Answer Area
Drag items
Correct arrangement
- Create the process.
- Validate the process.
- Enable the process.
- Activate the process.
Explanation
Workflow Process Creation: Correct Phase Order
The four phases follow a logical build → verify → prepare → deploy progression. Each phase gates the next - you cannot skip ahead without completing the prior step.
1. Create the process (Build it)
Why first: You must define and configure the workflow before anything else can happen. This is where you set up steps, rules, conditions, assignments, and logic. Nothing else is possible without an artifact to work with.
2. Validate the process (Verify it)
Why second: Validation checks the process for structural correctness - broken references, missing required fields, logical errors, or configuration gaps. This is a quality gate that prevents a broken process from entering the system. You validate before enabling because enabling a flawed process wastes time and can corrupt downstream behavior.
3. Enable the process (Prepare it)
Why third: Enabling makes the process recognized by the system as ready-to-use, but not yet live. Think of it as "staging" - the process is available but not actively running or triggering. Validation must succeed first; most systems will block enabling an invalid process.
4. Activate the process (Deploy it)
Why last: Activation is the go-live step. The process is now running and will execute for real users/triggers. This is intentionally the final gate so that partially built or unvalidated processes never accidentally go live.
Common Mistakes
| Mistake | Why it's wrong |
|---|---|
| Enabling before validating | Risks deploying a broken process into a ready state |
| Activating before enabling | Activation depends on the enabled state; skipping it is typically blocked by the system |
| Confusing "enable" and "activate" | Enable = available to the system; Activate = live and executing. They are distinct states. |
Key mental model: Think of it like publishing software - you write it (create), test it (validate), stage it (enable), then release it (activate).
Topics
Community Discussion
No community discussion yet for this question.