Custom Field and Workflow Governance — Assessment

1. Who can see a custom field while it is a draft?

Everyone using the form Nobody on forms, the API or the app until it is published Only mobile app users Only vendors

2. Is custom field change approval on in a new workspace?

No; the workspace switches it on Yes, always Only for Admins Only on the Enterprise plan

3. What do you give up by encrypting a sensitive custom field at rest?

Showing it on forms Filtering, searching and reporting by its value Nothing The ability to edit it

4. A bulk edit set the wrong values on 600 records. What is the quickest fix?

Edit each record Roll back the batch Delete the field Restore a database backup

5. What does a simulation suite do when it runs?

Executes the workflow on live records Publishes the workflow Replays saved cases and records pass or fail without executing anything Emails the workflow owner

6. What must a workflow have before it goes live?

A backup owner A named owner and a runbook link 100% branch coverage Approval from AWRA

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.