Workflow Builder Basics — Assessment

1. What does a trigger do in a workflow?

Starts the workflow when an event happens Assigns the action to a role after the workflow ends Sets the condition that decides whether to continue Publishes the workflow to all users immediately

2. Why are conditions useful?

They make every record fail They remove the trigger They keep workflows precise and policy-based They hide tasks from owners

3. When should a workflow create a task?

When a human owner must review, decide, or follow up Whenever the trigger fires, even if no decision is needed Only for approvals above a very high value threshold Only when every workflow step is fully automated

4. What should happen before publishing a workflow?

Test it with sample records and confirm expected output Disable every notification Publish without reading it Remove all owner notes

5. What makes a workflow easier to govern later?

Clear name, description, version notes, and owner No conditions Hidden approvals A blank title

Your details for the certificate

This is the name that will appear on your certificate.

Full name

Email

We email your result to this address with a link to confirm it is yours. If you are signed in, or once you confirm, the administrators of an organisation this email belongs to on AWRA OpsHub can see your attempts and certificate. Your name is as you type it here; only the email is confirmed.

Send me AWRA’s monthly email: new guides, product updates and courses. Unsubscribe anytime.

Graded server-side. No peeking at answers in the page source.