Your company has a Power BI dashboard that displays sales data from a SQL Server database hosted on-premises. The dashboard is used by the sales team to monitor daily performance. Recently, the dashboard has been showing stale data. The data is supposed to refresh every night at 2:00 AM. You have confirmed that the SQL Server database is updated with new data each night. However, the Power BI dataset refresh fails. You need to ensure that the dashboard shows up-to-date data every morning. What should you do?
On-premises data gateway enables connectivity for scheduled refresh.
Why this answer
The correct answer is B because an on-premises data gateway is required to bridge the connection between Power BI (a cloud service) and an on-premises SQL Server database. Since the dataset refresh fails despite the database being updated, the gateway is either missing or misconfigured. Installing and configuring the gateway allows the scheduled refresh to access the on-premises data source securely, ensuring the dashboard displays up-to-date data each morning.
Exam trap
The trap here is that candidates may think republishing the report (Option D) will fix the refresh issue, but they overlook that the scheduled refresh relies on a persistent gateway connection, not the report file itself.
How to eliminate wrong answers
Option A is wrong because disabling scheduled refresh and manually refreshing the dataset is not a sustainable solution for daily updates and does not address the root cause of the refresh failure. Option C is wrong because changing the data source to an Excel file in SharePoint Online avoids the on-premises connectivity issue but is a workaround that may not meet the company's data requirements and could introduce new data freshness or security concerns. Option D is wrong because republishing the Power BI report from Power BI Desktop does not fix the underlying connectivity problem; it only re-uploads the report without resolving the gateway or refresh failure.