Security, Compliance, and Recovery — Assessment

1. Which layers shape access in AWRA?

Roles and billing plan only; devices are managed outside AWRA Permissions alone; MFA is optional and does not affect module access Roles, permissions, MFA, devices, sessions, and support controls Only login credentials, since downstream access is set per record

2. Why use evidence packs?

To share read-only access with external auditors automatically To create a compressed backup of all documents for offline storage To lock records so no further edits can be made during a review To gather structured proof for review

3. What should be checked before force deleting a record?

Whether the record is linked to an active Academy course Impact preview and approval requirements Only whether the record is currently visible in search results Whether the record was created before the last billing cycle

4. When is a legal hold useful?

When a record has been inactive for more than 90 days When a record is under dispute, audit, or must not be purged When the trash retention period is about to expire automatically When a customer requests deletion under data privacy rules

5. What does a strong audit trail answer?

Actions across the current session only; older logs require an export Only the most recent change per record, with earlier history purged Who did what, when, where, and why Only actions flagged as sensitive by an administrator

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.