Control Tower Operator — Assessment

1. What is the control tower mainly for?

Running batch imports from external systems Configuring custom fields for individual modules Reviewing report certification requests only Managing alerts, anomalies, approvals, and operational exceptions

2. Why should operators drill down before acting?

Drilldowns hide the issue It removes all approvals Source records provide the evidence behind the alert It deletes old alerts

3. What should a good escalation include?

Only a vague complaint No source record Only a screenshot with no context Issue, source, impact, owner, action taken, decision needed, and deadline

4. What do repeated exceptions usually suggest?

A process problem that needs ownership A sign the control tower alert thresholds are set too sensitively A successful outcome reported with the wrong status label A normal variation that clears itself over time

5. How should alerts be prioritized?

By the time the alert was created without regard to impact By module type before considering operational urgency By severity and business impact Alphabetically by record name only

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.