This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Use the following questions to check what you learned about Dataverse auditing, duplicate detection, and data retention.
An administrator enables auditing at the environment level but discovers that changes to the Contact table aren't being logged. What's the most likely cause?
The environment retention period is set to Forever.
Auditing isn't enabled on the Contact table.
The Read logs setting isn't enabled.
The administrator doesn't have the System Customizer role.
What's the maximum number of published duplicate detection rules allowed per base record type?
Three
Five
Ten
Unlimited
A compliance officer needs to retain seven years of transaction records for PCI-DSS while minimizing Dataverse storage costs. Which approach best meets this requirement?
Set Dataverse audit retention to seven years.
Use long-term data retention to move inactive transactions to the retained store.
Export records to Excel and delete from Dataverse.
Use bulk delete to remove records older than seven years.
Which prerequisite must be met before configuring Dataverse long-term data retention policies?
Azure Synapse Link must be configured for the table.
The table must have auditing enabled.
The environment must be a Managed Environment.
The table must have column-level security enabled.
An administrator wants Dataverse read and export activities to be available for long-term compliance investigations in Microsoft Purview. Which setting must be enabled?
Start Auditing
Log access
Read logs
Enable SAS Logging in Purview
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?