Courseiva

CCNA Deploy Maintain Questions

27 questions · Deploy Maintain topic · All types, answers revealed

Practice these questionsExam hubAll questions
1
MCQhard

You are reviewing the deployment configuration for a Power BI dataset. The exhibit shows a JSON snippet of the dataset settings. You need to ensure that data is refreshed twice a day at 6:00 AM and 6:00 PM UTC. However, the refresh fails at both scheduled times. What is the most likely cause?

A.The data source uses Integrated Security (SSPI) which is not supported for scheduled refresh.
B.The refresh schedule uses UTC but the data source is in a different time zone.
C.The dataset has DirectQuery enabled, which prevents Import mode refresh.
D.The gateway ID is incorrect.
AnswerA

SSPI requires the user's context; stored credentials cannot be used with SSPI.

Why this answer

Option A is correct because scheduled refresh in Power BI requires a gateway to connect to on-premises data sources, and when the data source uses Integrated Security (SSPI), the gateway cannot delegate credentials for scheduled refresh. SSPI relies on the user's interactive Windows authentication context, which is not available during unattended scheduled refresh operations. This causes the refresh to fail at both scheduled times.

Exam trap

The trap here is that candidates often assume time zone mismatches or DirectQuery settings cause refresh failures, but the real issue is that Integrated Security (SSPI) requires interactive user context and is not supported for unattended scheduled refresh without proper delegation configuration.

How to eliminate wrong answers

Option B is wrong because time zone differences do not cause refresh failures; the refresh schedule simply runs at the specified UTC times regardless of the data source's time zone. Option C is wrong because DirectQuery does not prevent Import mode refresh; a dataset can have both DirectQuery and Import partitions, and scheduled refresh applies only to Import mode tables. Option D is wrong because an incorrect gateway ID would cause a connection error at the time of refresh, but the question states the refresh fails at both scheduled times, which is consistent with a credential delegation issue rather than a gateway misconfiguration.

Practice this question →
2
MCQeasy

You have developed a Power BI report that uses a live connection to an Azure Analysis Services (AAS) model. The AAS model is deployed in a different Azure region. Users report that the report loads slowly, sometimes taking over 30 seconds to render a single visual. You need to improve performance without changing the data model or the report structure. What should you do?

A.Enable the 'Reduce data shown in visuals' option in Power BI Desktop.
B.Implement row-level security (RLS) in the Azure Analysis Services model.
C.Deploy the Azure Analysis Services model to the same region as the Power BI workspace.
D.Convert the report to import mode and schedule a refresh.
AnswerC

Reducing network latency between the data source and Power BI improves query response times.

Why this answer

Option C is correct because deploying the Azure Analysis Services model to the same Azure region as the Power BI workspace minimizes network latency between the live connection client (Power BI) and the tabular model server. A live connection sends DAX queries over the XMLA protocol, and cross-region traffic introduces significant round-trip delays, which directly causes slow visual rendering. By co-locating the AAS server and the Power BI service in the same region, you reduce the physical distance and network hops, improving query response time without altering the model or report.

Exam trap

The trap here is that candidates often confuse client-side optimization settings (like reducing data shown) with server-side performance fixes, or they incorrectly assume that adding RLS or switching to import mode are acceptable solutions when the question explicitly prohibits changing the data model or report structure.

How to eliminate wrong answers

Option A is wrong because 'Reduce data shown in visuals' is a Power BI Desktop setting that limits the number of data points displayed in a visual (e.g., top N), which does not reduce the underlying query workload or network latency for a live connection to AAS; it only affects client-side rendering. Option B is wrong because implementing row-level security (RLS) in the AAS model adds additional DAX evaluation overhead for each query, which would likely worsen performance rather than improve it, and it does not address the cross-region latency issue. Option D is wrong because converting the report to import mode would require changing the data model (from live to import) and would break the live connection requirement; it also introduces a scheduled refresh dependency, which contradicts the constraint of not changing the data model or report structure.

Practice this question →
3
MCQhard

Your Power BI dataset uses DirectQuery to an Azure SQL Database. Users complain that the report is slow. You need to improve query performance without changing the data source. What should you do?

A.Reduce the number of columns and rows retrieved by the report visuals.
B.Add more visuals to the report to distribute the load.
C.Switch the dataset to Import mode.
D.Increase the scheduled refresh frequency.
AnswerA

Less data means faster queries.

Why this answer

Option A is correct because reducing the number of columns and rows retrieved by report visuals directly minimizes the amount of data sent from Azure SQL Database to Power BI via DirectQuery. Since DirectQuery sends native queries to the source for each visual interaction, fewer columns and rows mean smaller, faster queries, which reduces overall latency without altering the underlying data source.

Exam trap

The trap here is that candidates often confuse DirectQuery with Import mode and assume that increasing refresh frequency or switching modes is a valid performance fix, when in fact the question explicitly prohibits changing the data source, and DirectQuery has no refresh schedule.

How to eliminate wrong answers

Option B is wrong because adding more visuals increases the number of separate queries sent to the Azure SQL Database, which compounds the load and worsens performance, not distributes it. Option C is wrong because switching to Import mode changes the data storage method and requires a scheduled refresh, which violates the constraint of not changing the data source (the source remains Azure SQL, but the mode change alters how data is accessed and stored, which is a fundamental change to the dataset architecture). Option D is wrong because increasing scheduled refresh frequency only affects Import mode datasets; in DirectQuery, there is no scheduled refresh—queries are executed live against the source, so this option is irrelevant and would not improve query performance.

Practice this question →
4
Multi-Selectmedium

Which TWO actions are required to set up a Power BI deployment pipeline with separate data sources for Development and Production?

Select 2 answers
A.Define dataset parameters in Power BI Desktop for data source values.
B.Assign the dataset owner to each stage workspace.
C.Configure parameter rules in the deployment pipeline to map parameters to stage-specific values.
D.Re-enter data source credentials for each stage after deployment.
E.Create separate gateways for each stage.
AnswersA, C

Parameters allow you to change data source at deployment time.

Why this answer

Option A is correct because defining dataset parameters in Power BI Desktop for data source values allows you to make the data source connection dynamic. These parameters can then be overridden at each stage of the deployment pipeline, enabling separate data sources for Development and Production without modifying the report file.

Exam trap

The trap here is that candidates often confuse credential management (Option D) with parameter-based data source separation, or assume that separate gateways (Option E) are mandatory, when in fact parameter rules are the correct and efficient method for stage-specific data sources.

Practice this question →
5
MCQmedium

You are troubleshooting connectivity to a Power BI Premium dataset via the XMLA endpoint. A user reports that they cannot connect using SQL Server Management Studio (SSMS) but can view reports in the Power BI service. The user's email is user3@contoso.com. What is the most likely cause?

A.External connections are blocked by the configuration.
B.The user does not have permission to view reports.
C.The user is not in the allowedUsers list for the XMLA endpoint.
D.The XMLA endpoint is disabled.
AnswerC

Only user1 and user2 are allowed.

Why this answer

Option C is correct because the XMLA endpoint for Power BI Premium datasets requires explicit user membership in the allowedUsers list (or allowedGroups) to enable client tools like SSMS to connect. The user can view reports in the Power BI service, which uses a different permission model (workspace roles), but SSMS connectivity via XMLA is gated by this separate list. Since the user is not in the allowedUsers list, the connection fails even though they have report viewing access.

Exam trap

The trap here is that candidates confuse workspace permissions (which control report viewing) with the separate XMLA endpoint access list (which controls client tool connectivity), leading them to incorrectly choose Option B or Option D.

How to eliminate wrong answers

Option A is wrong because external connections are not blocked by default; the XMLA endpoint is enabled by default for Premium workspaces, and the issue is specifically about user-level access control, not a blanket block. Option B is wrong because the user can view reports in the Power BI service, which confirms they have at least Viewer permissions on the workspace, so lack of report permissions is not the cause. Option D is wrong because if the XMLA endpoint were disabled, no one could connect via SSMS, but the user's report viewing in the service would still work; the question states the user cannot connect, implying the endpoint is enabled but access is restricted.

Practice this question →
6
MCQhard

You manage a Power BI deployment that uses deployment pipelines. After promoting content from Development to Test, you notice that the Test workspace dataset uses a different data source than expected. What is the most likely reason?

A.The pipeline didn't deploy the dataset because it was already in Test.
B.The data source credentials were not applied during deployment.
C.The dataset parameters were not configured in the deployment pipeline rules.
D.The Test workspace has a separate dataset that was manually created.
AnswerC

Parameter rules are required to update data source connections across stages.

Why this answer

Option C is correct because deployment pipeline rules allow you to configure dataset parameters (such as data source paths) to differ between pipeline stages. If these rules are not set, the dataset retains the data source configuration from the source stage (Development), causing the Test workspace to use an unexpected data source. The pipeline deploys the dataset artifact, but without parameter overrides, the data source connection string remains unchanged.

Exam trap

The trap here is that candidates confuse data source credentials with data source parameters, assuming that credential issues cause the wrong data source to appear, when in fact parameters control the actual connection string, while credentials only handle authentication after the connection is established.

How to eliminate wrong answers

Option A is wrong because the deployment pipeline deploys datasets regardless of their presence in the target stage; it overwrites the existing dataset with the version from the source stage. Option B is wrong because data source credentials are not applied during deployment; credentials are managed separately in the target workspace after deployment, and their absence would cause a connection error, not a different data source. Option D is wrong because if a separate dataset were manually created in Test, the pipeline deployment would overwrite it with the dataset from Development, not preserve the manually created one.

Practice this question →
7
MCQmedium

You publish a Power BI report to a workspace that uses an organizational app. After updating the report, you want users to see the changes immediately without having to reinstall the app. What should you do?

A.Delete and recreate the app from the workspace.
B.Republish the report from Power BI Desktop.
C.Ask users to refresh their browser cache.
D.Update the app in the workspace by selecting 'Update app'.
AnswerD

Updating the app publishes changes to all users.

Why this answer

Option D is correct because updating the app in the workspace by selecting 'Update app' publishes the latest version of the report (and any other content) to the existing app without requiring users to reinstall. The app is a container that points to the workspace content; updating it refreshes that pointer, making changes immediately available to users who already have the app installed.

Exam trap

The trap here is that candidates confuse updating the workspace content (e.g., republishing a report) with updating the app itself, assuming changes automatically propagate to the app without an explicit 'Update app' step.

How to eliminate wrong answers

Option A is wrong because deleting and recreating the app forces users to reinstall the app from AppSource, causing unnecessary disruption and potential loss of app permissions or custom settings. Option B is wrong because republishing the report from Power BI Desktop only updates the report in the workspace, not the app itself; users would still see the old version until the app is updated. Option C is wrong because refreshing the browser cache does not affect the app's published content; the app is a separate deployment artifact that must be explicitly updated to reflect workspace changes.

Practice this question →
8
Multi-Selecthard

Which THREE steps should you perform to deploy a Power BI solution from development to production using deployment pipelines?

Select 3 answers
A.Create a new workspace manually in production.
B.Set up deployment pipeline rules to modify parameters (e.g., database name).
C.Assign Power BI Pro licenses to all developers.
D.Deploy content from development to test, then to production.
E.Create a development workspace and add content.
AnswersB, D, E

Rules automate configuration changes.

Why this answer

Option B is correct because deployment pipeline rules allow you to modify dataset parameters (e.g., database server or database name) when content moves between pipeline stages, ensuring each stage connects to the appropriate data source without manual reconfiguration. This is a core feature of Power BI deployment pipelines to maintain environment-specific settings.

Exam trap

The trap here is that candidates confuse general prerequisites (like licensing or manual workspace creation) with the specific steps required to use deployment pipelines, leading them to select options that are necessary for Power BI overall but not part of the pipeline deployment workflow.

Practice this question →
9
MCQhard

A Power BI administrator reviews the JSON configuration for a dataset named SalesDataset. The dataset is deployed to a Premium capacity workspace. The data source is an on-premises SQL Server. The administrator notices that the dataset has never refreshed successfully. Based on the exhibit, what is the most likely cause of the refresh failure?

A.The refresh schedule specifies a frequency of Weekly, but the time is in UTC and not adjusted for the local time zone
B.The dataset uses Integrated Security in the connection string, which is not supported for scheduled refresh
C.The dataset's defaultMode is set to Push, which does not support scheduled refresh
D.The dataset is in a Premium capacity workspace, which does not support scheduled refresh for on-premises data sources
AnswerC

Push datasets cannot be refreshed; they must be updated via the Push API.

Why this answer

Option C is correct because when a dataset's defaultMode is set to 'Push', it is designed to receive data only via the Push API and does not support scheduled refresh. Since the dataset has never refreshed successfully and the JSON configuration shows defaultMode as Push, the scheduled refresh will always fail regardless of the gateway or data source configuration.

Exam trap

The trap here is that candidates often focus on connectivity issues like time zones or authentication, overlooking the fundamental dataset mode property that disables scheduled refresh entirely.

How to eliminate wrong answers

Option A is wrong because while UTC time zone differences can cause refresh timing issues, they would not prevent the refresh from ever succeeding; the refresh would still run at the scheduled UTC time. Option B is wrong because Integrated Security (Windows authentication) is supported for scheduled refresh when a proper on-premises data gateway is configured and the user's credentials are stored securely. Option D is wrong because Premium capacity workspaces fully support scheduled refresh for on-premises data sources via an on-premises data gateway; the capacity tier does not impose such a restriction.

Practice this question →
10
Matchingmedium

Match each Power BI license type to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Create personal reports, cannot share

Share and collaborate with others

Dedicated capacity for a user

Reserved compute resources

Embed analytics in applications

Why these pairings

Licenses determine capabilities and sharing options.

Practice this question →
11
MCQeasy

You need to deploy a Power BI report from a development workspace to a production workspace. You want to ensure that the report uses the production dataset connection string without manual changes. What should you use?

A.Manually update the data source in the production workspace after deployment.
B.Use a Power BI template (.pbit) and change the connection string before publishing.
C.Configure a deployment pipeline with parameter rules to override the data source.
D.Publish the report directly to the production workspace and update the dataset.
AnswerC

Pipeline rules can automatically set production parameters.

Why this answer

Option C is correct because deployment pipelines in Power BI allow you to define parameter rules that automatically override data source connection strings when content is deployed from development to production. This ensures the report uses the production dataset without any manual post-deployment changes, maintaining consistency and reducing human error.

Exam trap

The trap here is that candidates often confuse manual post-deployment updates (options A and D) or template-based approaches (option B) with the automated, rule-based override mechanism provided by deployment pipelines, which is the only method that meets the 'no manual changes' requirement.

How to eliminate wrong answers

Option A is wrong because manually updating the data source after deployment contradicts the requirement of avoiding manual changes and introduces risk of errors. Option B is wrong because using a .pbit template still requires manual intervention to change the connection string before publishing, which does not automate the process. Option D is wrong because publishing directly to production and then updating the dataset requires manual steps and does not leverage automated deployment rules.

Practice this question →
12
Matchingmedium

Match each data source type to an example.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

SQL Server

CSV

Salesforce

Azure SQL Database

REST endpoint

Why these pairings

Power BI can connect to a wide variety of data sources.

Practice this question →
13
MCQmedium

You deploy a Power BI app to a workspace with an app-only license (Premium Per User). Users report that they can access the app but cannot see any visuals in the reports. The dataset uses Import mode. What is the most likely issue?

A.The report uses DirectQuery and the data source is offline.
B.The users do not have a Premium Per User license assigned.
C.The report is published to a shared dataset that has been deleted.
D.The dataset has row-level security (RLS) that filters all rows for these users.
AnswerB

PPU content requires PPU license to render.

Why this answer

The workspace uses a Premium Per User (PPU) license, which requires each user accessing content in that workspace to have a PPU license assigned. Without it, users can see the app in the list but cannot render visuals because the dataset (Import mode) is processed on PPU-capacity nodes that enforce license checks. This is the most likely cause given the symptom of empty visuals.

Exam trap

The trap here is that candidates may confuse 'app-only license' with 'shared capacity' or think that publishing an app grants access to all users, but PPU requires individual license assignment even for app viewers.

How to eliminate wrong answers

Option A is wrong because the dataset uses Import mode, not DirectQuery, so the data source being offline would not cause empty visuals (Import mode caches data in memory). Option C is wrong because if the shared dataset were deleted, the report would show a 'Could not load model' error or missing data source, not empty visuals. Option D is wrong because RLS filters rows but does not hide all visuals; users would still see the report layout with empty visuals if all rows are filtered, but the question states 'cannot see any visuals,' which implies the visuals fail to render entirely, not just show no data.

Practice this question →
14
MCQmedium

You are the Power BI administrator for a large enterprise. The company has a Power BI Premium capacity with a single dataset that is used by multiple reports and dashboards. The dataset is refreshed daily at 3:00 AM, and the refresh typically completes within 2 hours. Recently, users have reported that the dataset is not showing the most recent data until after 6:00 AM. You investigate and find that the scheduled refresh is taking 4 hours to complete, and there are no errors in the refresh history. The dataset uses import mode and connects to an on-premises SQL Server data warehouse. The data model contains several large fact tables and multiple calculated tables and measures. What should you do to reduce the refresh time and ensure data is available by 5:00 AM?

A.Remove all calculated tables and measures and replace them with calculated columns in Power Query
B.Implement incremental refresh on the fact tables to refresh only new and changed data
C.Change the dataset storage mode to DirectQuery to avoid the import process
D.Install an additional on-premises data gateway and configure load balancing
AnswerB

Incremental refresh reduces the volume of data processed, speeding up refresh.

Why this answer

Implementing incremental refresh on the fact tables allows Power BI to refresh only new or changed data instead of the entire dataset each time. This significantly reduces the refresh window, especially for large fact tables, because only the latest partition (e.g., today's data) is processed. Since the scheduled refresh starts at 3:00 AM and must complete by 5:00 AM, incremental refresh can cut the refresh time from 4 hours to under 2 hours by avoiding reprocessing historical data.

Exam trap

The trap here is that candidates often choose Option C (DirectQuery) thinking it eliminates refresh time entirely, but they overlook that DirectQuery changes the entire query model and is not a direct fix for a scheduled import refresh that is simply taking too long due to data volume.

How to eliminate wrong answers

Option A is wrong because replacing calculated tables and measures with calculated columns in Power Query does not reduce refresh time; calculated columns are computed during data load and can actually increase memory and processing overhead, while measures are computed at query time and have no impact on refresh duration. Option C is wrong because changing the dataset storage mode to DirectQuery would bypass the import process entirely, but it would also eliminate the benefits of import mode (such as fast query performance) and would require the on-premises SQL Server to handle all query loads, potentially causing performance issues and breaking existing reports that rely on import-mode features like calculated tables. Option D is wrong because installing an additional on-premises data gateway and configuring load balancing improves gateway throughput and reliability but does not address the root cause of slow refresh—the full reload of large fact tables; the gateway is not the bottleneck here since there are no errors in refresh history and the issue is the volume of data being refreshed.

Practice this question →
15
MCQhard

You have a Power BI dataset that is refreshed every hour from an on-premises data source using an enterprise gateway. The refresh consistently fails at 2:00 AM. What is the most likely cause?

A.The on-premises data gateway is scheduled to reboot at 2:00 AM.
B.The refresh is failing due to a transient network error.
C.The data source is undergoing maintenance in the cloud.
D.The scheduled refresh time conflicts with another refresh.
AnswerA

A reboot would cause the gateway to be unavailable.

Why this answer

The consistent failure at exactly 2:00 AM strongly points to a scheduled event on the on-premises data gateway, such as a reboot or maintenance window. Enterprise gateways can be configured to reboot periodically for updates or health reasons, and if this coincides with the refresh schedule, the gateway will be unavailable, causing the refresh to fail. Transient errors or cloud maintenance would not produce a perfectly consistent daily failure at the same time.

Exam trap

Microsoft often tests the concept that consistent, time-specific failures are almost always due to a scheduled event on the gateway or data source, not random network issues or cloud-side problems, which candidates might incorrectly assume due to lack of familiarity with gateway maintenance windows.

How to eliminate wrong answers

Option B is wrong because transient network errors are intermittent and unpredictable, not consistently occurring at the exact same time daily. Option C is wrong because the data source is on-premises, not in the cloud, so cloud maintenance is irrelevant to the refresh failure. Option D is wrong because a refresh time conflict would cause a different error (e.g., 'Refresh is already in progress') and would not be tied to a specific time like 2:00 AM unless another refresh is also scheduled at that exact time, which is less likely than a gateway reboot.

Practice this question →
16
Multi-Selectmedium

Which TWO actions should you take to ensure that a Power BI report deployed to production is available to users even if the gateway is offline for maintenance?

Select 2 answers
A.Create a Power BI Premium capacity to ensure high availability.
B.Schedule the dataset refresh to run during the maintenance window.
C.Use DirectQuery instead of Import mode to avoid gateway dependency.
D.Create a separate dataset in the cloud that caches the data.
E.Implement a disaster recovery plan that includes a secondary gateway.
AnswersD, E

A cloud dataset can be refreshed when the gateway is online.

Why this answer

Option D is correct because creating a separate dataset in the cloud that caches the data (e.g., using a scheduled dataflow or a cloud-based dataset with Import mode) ensures that the report can still serve cached data from the Power BI service even when the on-premises gateway is offline for maintenance. This decouples report availability from gateway connectivity, as long as the cached data is refreshed before the maintenance window.

Exam trap

The trap here is that candidates often assume DirectQuery removes all gateway dependency, but in reality, DirectQuery still requires the gateway for on-premises sources and introduces real-time dependency, making it worse for offline scenarios than Import mode with a cached dataset.

Practice this question →
17
MCQeasy

A company publishes a Power BI dataset to the service. They need to ensure that when the underlying data source is updated, the dataset refreshes automatically within 30 minutes. The data source is an on-premises SQL Server database. Which component must be configured to enable this automatic refresh?

A.Publish the dataset with incremental refresh enabled
B.Change the dataset storage mode to DirectQuery
C.Install and configure an on-premises data gateway
D.Enable the XMLA endpoint for the workspace
AnswerC

The gateway enables Power BI to connect to on-premises data sources for scheduled refresh.

Why this answer

To enable automatic refresh of a Power BI dataset from an on-premises SQL Server database, you must install and configure an on-premises data gateway. The gateway acts as a secure bridge, allowing the Power BI service to connect to on-premises data sources and execute scheduled refreshes. Without it, the cloud service cannot directly access the local database.

Exam trap

The trap here is that candidates often confuse incremental refresh or DirectQuery as alternatives to the gateway, not realizing that any on-premises data source—regardless of storage mode—requires a gateway for the Power BI service to access it.

How to eliminate wrong answers

Option A is wrong because incremental refresh optimizes refresh performance by partitioning data, but it does not enable connectivity to on-premises sources; a gateway is still required. Option B is wrong because DirectQuery mode queries the source in real time without importing data, but it still requires a gateway for on-premises sources and does not address the scheduled refresh requirement within 30 minutes. Option D is wrong because enabling the XMLA endpoint allows programmatic management and advanced analytics, but it does not provide the connectivity needed for automatic refresh from an on-premises database.

Practice this question →
18
MCQmedium

You manage a Power BI workspace used by the sales team. After updating a dataset with new columns, some users report that their reports show old data. You verify that the scheduled refresh completed successfully. What should you do first?

A.Open the report in Power BI Desktop, refresh the dataset, and republish.
B.Clear the users' browser cache.
C.Reconfigure the scheduled refresh to run more frequently.
D.Reset the on-premises data gateway.
AnswerA

Updating the dataset in Desktop and republishing ensures the report uses the new schema.

Why this answer

Option A is correct because when a dataset is updated with new columns in Power BI Desktop, the report's underlying data model must be refreshed and republished to the Power BI service. Even if the scheduled refresh completes successfully, it only refreshes the existing data structure; it does not automatically incorporate schema changes like new columns. Republishing the .pbix file ensures the service has the updated metadata and data.

Exam trap

The trap here is that candidates assume a successful scheduled refresh automatically propagates all changes, including schema modifications, when in fact it only refreshes data within the existing model structure.

How to eliminate wrong answers

Option B is wrong because clearing the users' browser cache would not resolve the issue of missing new columns; the report in the service still has the old schema. Option C is wrong because increasing the scheduled refresh frequency does not add new columns to the dataset; it only refreshes existing data. Option D is wrong because resetting the on-premises data gateway is unrelated to schema changes; the gateway handles data movement, not dataset structure updates.

Practice this question →
19
Drag & Dropmedium

Drag and drop the steps to create a measure in Power BI Desktop into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order

Why this order

Measures are created in the Modeling tab, require a DAX formula that calculates aggregations, and are then used in visuals.

Practice this question →
20
MCQeasy

You need to ensure that a Power BI report uses the latest data from a cloud-based Azure SQL Database. The report is configured with scheduled refresh. What is the minimum required license for the dataset owner to configure a scheduled refresh?

A.Power BI Premium capacity
B.Power BI Premium Per User
C.Power BI Free
D.Power BI Pro
AnswerD

Pro license is required to schedule refresh in shared capacity.

Why this answer

Option D is correct because Power BI Pro is the minimum license required for a dataset owner to configure a scheduled refresh against a cloud-based Azure SQL Database. Scheduled refresh is a premium feature that is not available with a Power BI Free license, and while Power BI Premium capacity or Premium Per User can also support scheduled refresh, they are not the minimum requirement. The dataset owner must have a Pro license to schedule refreshes for datasets hosted in shared capacity.

Exam trap

The trap here is that candidates often assume that because Azure SQL Database is a cloud source, a Free license might suffice, but Power BI Free does not support any form of scheduled refresh, regardless of the data source being cloud or on-premises.

How to eliminate wrong answers

Option A is wrong because Power BI Premium capacity is an organizational-level licensing option that provides dedicated capacity and additional features, but it is not the minimum license required for an individual dataset owner to configure scheduled refresh. Option B is wrong because Power BI Premium Per User is a per-user license that grants premium features, but it is not the minimum requirement; a Pro license suffices for scheduled refresh in shared capacity. Option C is wrong because Power BI Free license does not allow scheduled refresh; it only permits manual refresh via Power BI Desktop or the service, and the dataset owner cannot configure automatic scheduled refresh without a Pro or higher license.

Practice this question →
21
MCQhard

You are a Power BI administrator for a large organization. A team has published a shared dataset to a Premium workspace. They use an XMLA endpoint to programmatically refresh the dataset daily. Recently, the refresh started failing with the error: 'The operation was canceled because the session was terminated by a concurrent operation.' The dataset is not partitioned. You need to ensure the refresh completes without errors. What should you do?

A.Remove all scheduled refreshes and rely solely on the XMLA script.
B.Enable the 'Refresh conflict detection' setting on the dataset to prevent concurrent operations.
C.Change the XMLA script to run less frequently, e.g., once per week.
D.Partition the dataset and refresh partitions sequentially.
AnswerB

This setting detects and blocks overlapping refresh operations, preventing the error.

Why this answer

The error 'The operation was canceled because the session was terminated by a concurrent operation' indicates that two refresh operations are conflicting on the same dataset. Enabling 'Refresh conflict detection' on the dataset prevents concurrent refreshes by queuing or blocking overlapping operations, ensuring the XMLA-triggered refresh completes without interruption.

Exam trap

The trap here is that candidates often assume the error is caused by the XMLA script itself (e.g., frequency or scheduling) and overlook the fact that the conflict is due to concurrent operations, which is directly solved by enabling conflict detection rather than changing the script's schedule or partitioning strategy.

How to eliminate wrong answers

Option A is wrong because removing scheduled refreshes does not address conflicts that could arise from other concurrent operations, such as multiple XMLA scripts or user interactions; the error specifically points to a concurrent session, not just scheduled refreshes. Option C is wrong because reducing the frequency of the XMLA script does not prevent conflicts when the script runs; if another operation occurs at the same time, the conflict persists regardless of frequency. Option D is wrong because partitioning the dataset and refreshing partitions sequentially does not resolve the fundamental issue of concurrent sessions; the error is about session termination, not partition-level parallelism, and sequential partition refreshes can still conflict if multiple sessions attempt to refresh the same dataset.

Practice this question →
22
Drag & Dropmedium

Drag and drop the steps to create a relationship between two tables in Power BI Desktop into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order

Why this order

Relationships are created by dragging columns between tables in the Model view, then confirming settings like cardinality.

Practice this question →
23
MCQeasy

A user reports that a Power BI report is not refreshing data from a SQL Server database. The dataset uses Import mode. The gateway cluster shows all gateways are online. What is the most likely cause?

A.The report is using a scheduled refresh with a conflicting time.
B.The gateway version is incompatible with the SQL Server version.
C.The dataset uses DirectQuery mode which requires a live connection.
D.The data source credentials are incorrect or expired.
AnswerD

Correct. Expired or incorrect credentials are a common cause of refresh failures.

Why this answer

Option D is correct because in Import mode, Power BI caches data and refreshes it on a schedule using stored credentials. If those credentials expire or become invalid, the refresh fails even though the gateway cluster shows as online. The gateway being online only indicates network connectivity, not that the stored credentials are still valid for the SQL Server database.

Exam trap

The trap here is that candidates see 'gateway cluster shows all gateways are online' and assume the issue must be elsewhere, but gateway online status does not validate the stored data source credentials, which are a separate authentication layer that can expire or become invalid independently.

How to eliminate wrong answers

Option A is wrong because a conflicting scheduled refresh time would cause a refresh to be skipped or queued, not a persistent failure; the report would still refresh at the next available window. Option B is wrong because gateway version incompatibility with SQL Server version is extremely rare; the gateway communicates via standard TDS protocol and is backward-compatible with most SQL Server versions. Option C is wrong because the question explicitly states the dataset uses Import mode, not DirectQuery mode, so the requirement for a live connection is irrelevant.

Practice this question →
24
Multi-Selecthard

Which THREE factors should you consider when planning the deployment of Power BI content to a large enterprise with multiple regions?

Select 3 answers
A.Data residency requirements for each region.
B.The number of visuals per report page.
C.The currency format used in reports for each region.
D.The use of deployment pipelines to promote content between regions.
E.The location and performance of on-premises data gateways.
AnswersA, D, E

Data must stay within geographic boundaries due to compliance.

Why this answer

Data residency requirements are critical because Power BI stores data in specific Azure regions. For a multi-region enterprise, you must ensure that data does not leave the required geographic boundary due to compliance or legal mandates. This affects where you provision Power BI tenants, capacity, and data sources.

Exam trap

The trap here is that candidates confuse report-level formatting concerns (like currency or visuals) with infrastructure-level deployment considerations, which are the actual focus of multi-region planning.

Practice this question →
25
MCQmedium

You are deploying a Power BI solution to a customer. The customer requires that all report access be controlled via Azure Active Directory (Azure AD) groups. You have a single workspace with multiple reports. What is the best practice for managing permissions?

A.Create a Power BI group and add users to it.
B.Assign each user directly to the workspace role.
C.Share each report individually with users.
D.Add an Azure AD group to the workspace role.
AnswerD

This is the recommended approach for scalable access.

Why this answer

Option D is correct because using an Azure AD group to manage workspace roles aligns with the customer's requirement for centralized access control via Azure AD. This approach simplifies permission management by allowing group membership changes in Azure AD to automatically propagate to Power BI workspace access, ensuring consistency and reducing administrative overhead.

Exam trap

The trap here is that candidates may confuse Power BI groups (which are legacy and not Azure AD integrated) with Azure AD groups, or assume that direct user assignment or individual report sharing is simpler, missing the requirement for centralized Azure AD-based control.

How to eliminate wrong answers

Option A is wrong because creating a Power BI group (a distribution group or security group within Power BI) does not leverage Azure AD groups as required; it introduces a separate group management layer that is not integrated with the customer's Azure AD-based identity governance. Option B is wrong because assigning each user directly to the workspace role violates the requirement to control access via Azure AD groups, leading to manual, error-prone user management and lack of centralized control. Option C is wrong because sharing each report individually bypasses workspace-level permissions, creating a fragmented permission model that is harder to audit and does not scale; it also does not use Azure AD groups as specified.

Practice this question →
26
MCQmedium

You manage a Power BI workspace that contains a dataset refreshed daily from an on-premises SQL Server. Users report that the report shows data from two days ago. You verify that the scheduled refresh ran successfully this morning. What is the most likely cause?

A.The gateway is using a cached version of the data due to a misconfigured data source.
B.The refresh took longer than expected and timed out.
C.The scheduled refresh is not set to refresh the dataset.
D.The on-premises data gateway is offline.
AnswerA

A misconfigured gateway cache can cause stale data.

Why this answer

Option A is correct because the most likely cause is that the on-premises data gateway is using a cached version of the data due to a misconfigured data source. When the data source is misconfigured (e.g., incorrect credentials or connection string), the gateway may fall back to a previously cached dataset, causing the report to show stale data even though the scheduled refresh appears to have run successfully. This explains why users see data from two days ago despite a successful refresh this morning.

Exam trap

The trap here is that candidates assume a successful refresh always means fresh data, but the gateway's caching behavior can mask a misconfigured data source, leading to stale data without an error.

How to eliminate wrong answers

Option B is wrong because if the refresh took longer than expected and timed out, the refresh would not have completed successfully, but the question states the scheduled refresh ran successfully. Option C is wrong because the scheduled refresh is explicitly set to refresh the dataset daily, and the question confirms it ran successfully this morning. Option D is wrong because if the on-premises data gateway were offline, the scheduled refresh would fail entirely, not run successfully and still show stale data.

Practice this question →
27
MCQeasy

You review the dataset refresh history. The second refresh took 30 minutes and failed. What is the most likely reason for the failure?

A.The refresh schedule conflicted with another refresh.
B.The on-premises data gateway was offline.
C.The refresh exceeded the timeout limit set in the gateway.
D.The data source was unavailable.
AnswerC

Long refresh duration and failure suggest timeout.

Why this answer

The second refresh took 30 minutes and failed, which strongly indicates the refresh exceeded the default 30-minute timeout limit configured in the on-premises data gateway. When a dataset refresh operation in Power BI runs longer than the gateway's timeout setting, the gateway terminates the connection, causing the refresh to fail. This is a common issue when refreshing large datasets or complex queries through a gateway.

Exam trap

The trap here is that candidates often confuse the gateway timeout with the Power BI service refresh timeout, or assume a 30-minute failure is due to a schedule conflict or data source unavailability, rather than recognizing the exact match with the default gateway timeout value.

How to eliminate wrong answers

Option A is wrong because a refresh schedule conflict would typically cause the second refresh to be skipped or queued, not to start and then fail after 30 minutes. Option B is wrong because if the on-premises data gateway were offline, the refresh would fail immediately or very quickly, not after a full 30-minute attempt. Option D is wrong because if the data source were unavailable, the refresh would fail early in the process (e.g., during connection attempt), not after 30 minutes of execution.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Deploy Maintain questions.

Start 20-question session