A recent server migration applied an update to dataset naming conventions.

This question falls under theData Governancedomain, focusing on troubleshooting data freshness issues in dashboards. The dashboard shows stale data despite a successful refresh, and the server migration updated naming conventions, suggesting a potential mismatch.

Confirm the dashboard is pointed to the newest dataset (Option A): The server migration updated dataset naming conventions, so the dashboard might still be pointing to an old dataset name, causing stale data. Confirming the dataset connection is the first step.

Filter the data in the dashboard (Option B): Filtering might adjust the view but doesn’t address the root cause of stale data.

Escalate user permissions on the server (Option C): Permissions issues would likely prevent access, not cause stale data, especially since the dataset refreshed successfully.

Verify that the dashboard subscription is not expired (Option D): An expired subscription might prevent access, but the dashboard is accessible, just showing stale data.

The DA0-002 Data Governance domain includes "data quality control concepts," such as ensuring dashboards connect to the correct, updated datasets after changes like server migrations.