Transaction Audit Fundamentals — Assessment

1. What is the main purpose of Transaction Audit Fundamentals?

To hide operational exceptions from managers To bypass approvals and audit trails To duplicate records across modules To prove transaction history by reading actor, action, time, record, impact, and evidence

2. What should users check before taking action?

Only the source record from last week Actor, role, timestamp, action, old and new values, approval, and attachments Nothing; action should be automatic every time Only the newest notification

3. Why does evidence matter in this course?

It lets users delete history It replaces the need for source records It makes ownership unclear It supports the audit finding with facts from the source record

4. What risk does the routine help reduce?

Approval steps taking too long to complete Audit trails accumulating too many records Acting on assumptions instead of verified transaction history Reports being generated too frequently

5. What should happen when work is handed off or closed?

The finding should state fact, evidence, impact, and follow-up owner All attachments should be moved to a shared folder first The next owner should reconstruct context from the report alone The source record should be closed before the handoff is confirmed

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.