How many Troubleshooting Scenario Questions questions are on this page?

This page has 12 Troubleshooting Scenario Questions scenario questions for the PL-900 exam, each with detailed explanations and wrong-answer analysis.

How should I approach PL-900 scenario questions?

Read the full scenario before looking at the answer options. Identify the constraint or requirement in the scenario, then eliminate options that are generally true but wrong for this specific case. Scenario questions reward careful reading over pattern matching.

← Back to Microsoft Power Platform Fundamentals PL-900 questions

Scenario-based practice

Troubleshooting Scenario Questions

Practise Microsoft Power Platform Fundamentals PL-900 practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

Start full practice test Read exam guide

scenario questions

PL-900

exam code

Microsoft

vendor

Scenario guide

How to approach troubleshooting scenario questions

These questions describe a network symptom and ask you to identify the root cause or the correct fix. They appear across all certification exams and reward systematic thinking over memorisation. The best candidates follow a consistent troubleshooting framework even under time pressure.

Quick answer

Troubleshooting Scenario Questions questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Practice scenarios

Question 1hardmultiple choice

Full question →

Refer to the exhibit. You are troubleshooting a Power Automate flow that fails when trying to access an on-premises SQL Server database. The flow uses the SQL connector. Based on the exhibit, what is the most likely cause of the failure?

Exhibit

{
  "connections": [
    {
      "name": "shared_office365",
      "id": "/providers/Microsoft.PowerApps/apis/shared_office365"
    },
    {
      "name": "shared_sql",
      "id": "/providers/Microsoft.PowerApps/apis/shared_sql"
    }
  ],
  "environment": {
    "name": "Production",
    "type": "Production",
    "region": "eastus"
  }
}

A
The Office 365 connector is conflicting with the SQL connector.
Why it fails: Multiple connectors can coexist in a flow without conflict.
B
The flow is using the cloud SQL connector without an on-premises data gateway.
The cloud SQL connector reaches only internet-accessible databases; on-premises SQL Server requires an on-premises data gateway to bridge the network boundary. Without that gateway installed and configured, the flow's connection attempt fails, matching the exhibit's error.
C
The environment type is Production, which restricts access to on-premises data.
Why it fails: Production environments can connect to on-premises data with a gateway.
D
The region 'eastus' does not support on-premises connectivity.
Why it fails: All Azure regions support on-premises data gateways.

Full breakdown with real-world context →

Question 2hardmultiple choice

Full question →

An organization uses Power Automate to process invoices from email attachments. Some invoices are processed incorrectly because the flow fails to parse PDFs with non-standard layouts. What should the administrator do to improve accuracy?

A
Increase the flow run frequency to every minute.
Why it fails: Run frequency governs how often the flow triggers, not how the PDF parser interprets layout. Non-standard invoices fail at extraction regardless of cadence, so more runs simply produce more failures. Higher frequency suits latency-sensitive triggers, such as near-real-time alerts, where throughput timing matters rather than document comprehension.
B
Add a condition to route non-parsed invoices for manual approval.
Why it fails: Routing unparsed invoices to manual approval handles the exception after parsing has already failed; it does not raise extraction accuracy for non-standard layouts. It tempts because approval workflows are a standard Power Automate pattern for human oversight, and they are correct when the requirement is governance sign-off rather than automated data capture.
C
Use AI Builder to create a custom document processing model.
AI Builder's custom document processing model learns your invoice layouts from labelled samples, so it extracts fields from non-standard PDFs that the built-in parser cannot handle, directly addressing the parsing accuracy failure in the flow.
D
Change the trigger to a manual button in Power Apps.
Why it fails: A manual Power Apps button changes who initiates the flow, not how PDFs are parsed. Non-standard layouts still defeat the same extractor, so accuracy is unchanged. Manual triggers suit on-demand user-initiated actions, such as a technician submitting a request, where scheduled or automated triggering is undesirable.

Full breakdown with real-world context →

Question 3hardmultiple choice

Full question →

You are a Power BI administrator for a large retail company. The company has a Power BI workspace that contains a dashboard named 'Sales Overview'. The dashboard is shared with the sales team. Recently, users have reported that the dashboard is loading slowly, and some visuals show 'Data is not available' errors. The dashboard uses a DirectQuery connection to an on-premises SQL Server database. The database team confirms that the server is not under heavy load. You need to troubleshoot and resolve the issue. What should you do first?

A
Check the on-premises data gateway performance and logs for errors
DirectQuery routes every visual query through the on-premises data gateway, so gateway latency or errors produce slow loads and 'Data is not available' messages even when the SQL Server itself is healthy. Checking gateway performance and logs isolates the failing hop first.
B
Replace the DirectQuery connection with an Import connection
Why it fails: Switching to Import would cache data but abandons the near-real-time requirement DirectQuery exists to satisfy, and it does not address the failing gateway causing 'Data is not available'. Import is correct when latency tolerance allows scheduled refreshes instead of live queries.
C
Ask the database team to add more indexes to the SQL Server tables
Why it fails: Adding indexes targets query performance on the SQL Server, yet the database team confirms the server is not under heavy load, so the bottleneck lies elsewhere — most likely the on-premises data gateway. Indexing would be the right move when DirectQuery queries themselves are slow due to poor table scans.
D
Increase the scheduled refresh frequency to every 15 minutes
Why it fails: Scheduled refresh frequency applies only to Import datasets; DirectQuery models query the source live and have no refresh schedule to increase. This would be the right action for an Import model whose cached data is stale, not for a DirectQuery connectivity failure.

Full breakdown with real-world context →

Question 4mediummultiple choice

Full question →

A company uses Power Automate to automate approval workflows for purchase orders. The flow should send an approval request to the manager of the requestor. When the manager approves, the flow should update a SharePoint list and send a confirmation email. However, the flow fails with an error 'Unable to find the manager for the specified user'. What is the most likely cause?

A
The user profile in Microsoft Entra ID does not have a manager assigned.
The approval action resolves the requestor's manager by querying the manager attribute on their Microsoft Entra ID profile. When that attribute is empty, the connector cannot resolve a recipient, producing exactly the 'Unable to find the manager' error rather than a permissions or licensing fault.
B
The SharePoint list column for manager is missing.
Why it fails: The error concerns resolving a manager from Microsoft Entra ID, not reading a SharePoint column; the manager lookup uses the requestor's organisational data, so a missing list column is irrelevant. It tempts because SharePoint lists store request data, and would be correct if the flow failed while updating a nonexistent field.
C
The flow trigger is set to 'When a new item is created' but the item already exists.
Why it fails: An already-existing item does not prevent the trigger from firing on new items, and the error names manager resolution rather than triggering; the manager lookup queries Microsoft Entra ID independently of item creation. It tempts because trigger misconfiguration commonly breaks flows, and would be correct if the flow never started for existing records.
D
The SharePoint list does not have the correct permissions.
Why it fails: Insufficient SharePoint permissions would surface as an access-denied or forbidden error on the list action, not as a manager lookup failure, which queries Microsoft Entra ID. It tempts because permission problems frequently break flows, and would be correct if the failure occurred when updating the SharePoint list after approval.

Full breakdown with real-world context →

Question 5mediummultiple choice

Full question →

A company uses Power Apps to build a canvas app for field technicians to report equipment issues. The app includes a GPS location control and requires offline capability. During a pilot, technicians report that the app fails to load data when they are in remote areas with no internet. Which design change should the app maker implement to address this issue?

A
Adjust the GPS control to use high accuracy mode.
Why it fails: High accuracy mode only refines GPS precision; it does nothing when the device has no connectivity, so data still fails to load. It is tempting because location is mentioned in the scenario, but GPS accuracy is unrelated to offline data availability.
B
Add a Power Automate flow to sync data periodically.
Why it fails: A scheduled flow still requires connectivity to run and cannot populate the app while the technician is offline; it syncs server-side, not on the device. Periodic synchronisation suits keeping Dataverse records current between connected sessions, not enabling offline field use.
C
Enable offline use and configure the app to cache data locally.
Offline capability requires the app to store data on the device, since the stem's constraint is no internet in remote areas. Enabling offline use with local caching lets technicians load and submit records without connectivity, syncing to the data source once the device reconnects.
D
Convert the canvas app to a model-driven app.
Why it fails: Model-driven apps render server-side metadata and require continuous Dataverse connectivity, so they cannot cache records for disconnected use. Converting also discards the canvas GPS control. Model-driven apps suit internal, form-over-data processes where devices stay online, not offline field reporting.

Full breakdown with real-world context →

Question 6hardmultiple choice

Full question →

You are troubleshooting a canvas app that loads slowly. The app uses over 50 data sources and many formulas. Which action is most likely to improve performance?

A
Increase the data row limit for each data source
Why it fails: Raising the data row limit increases the volume each data source retrieves, adding load rather than reducing it. The setting exists to fetch more records when an app genuinely needs them, but with 50 data sources the bottleneck is the number of connections and formula evaluations, not row ceilings.
B
Use delegable queries to filter data at the source
Delegable queries push filtering to the data source rather than pulling entire tables to the client, so the canvas app retrieves only matching records. With over 50 data sources, this sharply cuts the volume transferred and processed locally, directly addressing the slow loading caused by non-delegable operations.
C
Disable the formula-level error checking
Why it fails: Disabling formula-level error checking only suppresses compile-time warnings; it does not reduce the number of data sources, delegable queries or formula evaluations that drive load time. It is tempting because it speeds up authoring in Power Apps Studio, which is the correct choice when editing large apps becomes sluggish, not when runtime performance suffers.
D
Remove unused data sources from the app
Why it fails: Removing unused data sources reduces the number of connections the app establishes at startup, which is a genuine performance lever. However, the stem's slow load stems from excessive data sources and formulas combined; eliminating unused ones alone leaves the heavy formula and delegation load unaddressed.

Full breakdown with real-world context →

Question 7mediummultiple choice

Full question →

Your organization uses Power Automate to automate the creation of support tickets in ServiceNow when a critical alert is triggered in Microsoft Sentinel. The flow uses the 'When a new alert is created' trigger from Sentinel. The flow runs but no tickets are created. You check the Sentinel log and see that alerts are being generated. What should you investigate first?

A
Verify that the flow is enabled.
Why it fails: A disabled flow would produce no run history at all, yet the stem states the flow runs, so enablement is already satisfied. It tempts because a switched-off flow is a common cause of silent non-execution, and checking status is a quick first step in ordinary troubleshooting.
B
Ensure that the Sentinel data connector is properly installed.
Why it fails: Alerts already appear in the Sentinel log, proving ingestion works, so the connector is not the fault. It tempts because a missing or misconfigured data connector is a frequent reason Sentinel shows nothing, but here the trigger fires and the failure lies downstream.
C
Review the trigger condition or filter query.
The Sentinel trigger fires only when an alert matches its configured conditions. If a filter query or trigger condition excludes the generated alerts, the flow never starts, so no ServiceNow tickets appear despite alerts existing. Reviewing these settings first confirms whether the trigger is actually firing.
D
Check if the ServiceNow connector is configured with the correct instance.
Why it fails: The stem says the flow runs, so the trigger fires; a wrong ServiceNow instance would surface as an action failure in run history, not as no tickets. It tempts because connector misconfiguration is a common cause of failed ticket creation, but the question asks what to investigate first.

Full breakdown with real-world context →

Question 8hardmultiple choice

Full question →

Northwind Traders has a production environment named 'Ops-Prod' with Dataverse enabled. A maker reports that after importing a managed solution, a canvas app that previously worked now fails to connect to a custom connector. The admin confirms the connector exists in the environment and the maker holds the Environment Maker role. What is the most likely cause?

A
Managed solutions block all outbound calls from custom connectors until a data loss prevention policy is relaxed.
Why it fails: Managed versus unmanaged status affects how solution components can be modified, not whether connectors can make outbound calls. Data loss prevention policies can restrict connector use, but a managed solution alone does not block outbound traffic, and no policy change was described, so this is not the likely cause.
B
The maker requires the System Administrator role to use any custom connector in a managed solution.
Why it fails: Using a custom connector does not require System Administrator. Environment Maker plus a valid connection to the connector is sufficient for authoring and running an app that uses it. Requiring full environment administration would contradict the least-privilege model, so this explanation does not account for the failure described.
C
The custom connector must be promoted to a certified connector before it can be used inside a canvas app.
Why it fails: Certification is a Microsoft review process for publishing connectors broadly, not a prerequisite for using a custom connector within a single environment. Custom connectors work in canvas apps without certification, so this does not explain the failure, and the connector reportedly already exists and was previously functional.
D
The custom connector's connection was not re-established by the maker after the solution import, so the app references a missing or unauthorized connection.
Connections are user-specific artifacts and are not carried inside a solution. After importing a managed solution that includes a custom connector, each user must create their own connection to that connector, and the app must reference a connection the running user owns. Because the maker holds Environment Maker but no connection existed yet, the app fails at runtime, matching the symptom precisely.

Full breakdown with real-world context →

Question 9mediummultiple choice

Full question →

Refer to the exhibit. A Power BI dashboard is configured with the shown data sources. The dashboard fails to refresh automatically. What is the most likely cause?

Exhibit

{
  "name": "Sales Dashboard",
  "dataSources": [
    {
      "type": "SQL Server",
      "connectionString": "Server=myserver.database.windows.net;Database=SalesDB;..."
    },
    {
      "type": "Excel",
      "path": "https://sharepoint.com/sites/sales/Shared%20Documents/Report.xlsx"
    }
  ],
  "refreshSchedule": {
    "frequency": "Daily",
    "time": "02:00"
  }
}

A
The refresh frequency is set to daily, which is too infrequent
Why it fails: Daily refresh is a valid, supported schedule; infrequency does not prevent a refresh from running. It is tempting because a stale dashboard looks like a failed refresh, and it would be correct if the requirement were near-real-time data rather than automatic refresh succeeding at all.
B
The Excel file is stored in an unsupported location
Why it fails: Power BI's scheduled refresh supports Excel workbooks on OneDrive, SharePoint or a gateway-connected local path, so location alone rarely blocks it; credential and gateway configuration are the usual causes. It is tempting because unsupported storage is a known limitation, and it would be correct if the file sat on a personal drive with no gateway.
C
The SQL Server data source requires an on-premises data gateway
On-premises SQL Server cannot be reached directly by the Power BI cloud service, so refreshes fail until an on-premises data gateway bridges the two. This satisfies the exhibit's hybrid connectivity constraint; cloud-only sources would refresh without a gateway, but local SQL Server requires one.
D
The dashboard uses two data sources, but only one is allowed
Why it fails: Power BI permits many data sources per dataset, so a two-source limit does not exist and cannot block refresh. The tempting idea is that mixing sources breaks refresh, but the real constraint is gateway or credential configuration for on-premises sources. Multiple sources are perfectly valid when each connection is configured correctly.

Full breakdown with real-world context →

Question 10mediummultiple choice

Full question →

A company uses Microsoft Power Apps to build a leave request application. The app uses SharePoint as the data source. Users report that when they submit a leave request, the app sometimes fails to save the data and shows a generic error. Which should you investigate first?

A
Clear the browser cache and cookies.
Why it fails: Clearing browser cache removes locally stored data but cannot resolve intermittent save failures caused by the app's data operations against SharePoint. It tempts as a generic first-line fix for stale UI behaviour, yet the symptom is server-side write failure, so the data connection and formulas warrant investigation first.
B
Verify the connection to the SharePoint data source.
A stale or broken SharePoint connection is the most common cause of intermittent save failures with generic errors. Verifying the connector's authentication and permissions directly addresses the data-write failure described in the stem before investigating formulas or app logic.
C
Check if the app uses delegation for large lists.
Why it fails: Delegation affects how filters and queries are translated to SharePoint; it causes incomplete or missing results, not failures when writing a new record. It tempts because delegation is a common SharePoint data-source pitfall, but it governs retrieval, so it does not explain a save operation returning a generic error.
D
Review the app formulas for syntax errors.
Why it fails: Syntax errors would prevent the app from running or saving in the editor, and would fail consistently rather than intermittently. It tempts because formula mistakes are a frequent canvas app problem, yet a generic error on submit points to the data connection or required-field handling instead.

Full breakdown with real-world context →

Question 11hardmultiple choice

Full question →

You are troubleshooting a canvas app that connects to a SQL Server database through an on-premises data gateway. Users in the finance department receive an error stating the app cannot reach the data source, while users in IT can use the app normally. What is the most likely cause?

A
The finance users lack the necessary permissions on the SQL Server database.
Why it fails: If finance users lacked SQL Server permissions, the error would typically be an authentication or access-denied message from SQL Server, not a generic inability to reach the data source. The gateway connection uses stored credentials, so individual database permissions are less likely to produce a reachability error.
B
The gateway is installed on a machine that is turned off during finance working hours.
Why it fails: If the gateway machine were offline, all users including IT would experience failures, not just finance. A time-based outage would also affect IT users who work the same hours. The selective failure by department points to a permission issue rather than gateway availability.
C
The finance users have not been granted access to the on-premises data gateway connection.
On-premises data gateway connections have their own user list separate from the gateway itself. If finance users are not added as users of the specific connection, their apps cannot use it, producing a data source unreachable error. IT users were likely added, explaining why only they succeed.
D
The SQL Server database has reached its maximum number of concurrent connections.
Why it fails: A connection limit would cause intermittent or global failures, not a consistent failure isolated to one department. The gateway pools and reuses connections, so hitting a hard concurrent limit that only affects finance users is unlikely. This does not explain the department-specific pattern.

Full breakdown with real-world context →

Question 12hardmultiple choice

Full question →

You are troubleshooting a Power Automate flow that uses an HTTP action to call a REST API. The flow fails with a '429 Too Many Requests' error. The API has a rate limit of 100 requests per minute. Which strategy should you implement to handle this error gracefully?

A
Implement retry logic with exponential backoff in the HTTP action settings.
Exponential backoff spaces retries progressively, so the flow waits out the 100-requests-per-minute window rather than hammering the API. This satisfies the rate-limit constraint by letting the HTTP action retry after throttling clears, avoiding repeated 429 failures.
B
Increase the flow's concurrency setting to process more requests simultaneously.
Why it fails: Raising concurrency sends requests in parallel, exhausting the 100-per-minute quota sooner and worsening the 429 responses. Concurrency tuning suits high-volume flows against APIs without tight limits, but graceful handling here requires retry-after delays or throttling to stay within the rate limit.
C
Use a 'Condition' action to check the status code and ignore 429 errors.
Why it fails: Ignoring 429 responses discards the call without retrying, so the API request never completes and data is lost. Condition actions are appropriate for branching on business logic, but rate limiting demands honouring the Retry-After header and reissuing the request after a delay, not suppressing the error.
D
Use the 'Configure Run After' option to skip the action on failure.
Why it fails: Skipping the action on failure abandons the API call permanently, leaving downstream steps without the response data. Configure Run After is designed for optional or non-critical steps, but a rate-limited call must be retried after the Retry-After interval so the request eventually succeeds.

Full breakdown with real-world context →

These PL-900 practice questions are part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style PL-900 questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.

Troubleshooting Scenario Questions

How to approach troubleshooting scenario questions

Quick answer

Related PL-900 topic practice pages

Demonstrate the capabilities of Power Apps practice questions

Demonstrate the capabilities of Power Automate practice questions

Describe the business value of Microsoft Power Platform practice questions

Manage the Microsoft Power Platform environment practice questions

Demonstrate the capabilities of Microsoft Copilot Studio practice questions

PL-900 fundamentals practice questions

PL-900 scenario practice questions

PL-900 troubleshooting practice questions

Practice scenarios

Refer to the exhibit. You are troubleshooting a Power Automate flow that fails when trying to access an on-premises SQL Server database. The flow uses the SQL connector. Based on the exhibit, what is the most likely cause of the failure?

Exhibit

An organization uses Power Automate to process invoices from email attachments. Some invoices are processed incorrectly because the flow fails to parse PDFs with non-standard layouts. What should the administrator do to improve accuracy?

You are troubleshooting a canvas app that loads slowly. The app uses over 50 data sources and many formulas. Which action is most likely to improve performance?

Refer to the exhibit. A Power BI dashboard is configured with the shown data sources. The dashboard fails to refresh automatically. What is the most likely cause?

Exhibit

A company uses Microsoft Power Apps to build a leave request application. The app uses SharePoint as the data source. Users report that when they submit a leave request, the app sometimes fails to save the data and shows a generic error. Which should you investigate first?

You are troubleshooting a canvas app that connects to a SQL Server database through an on-premises data gateway. Users in the finance department receive an error stating the app cannot reach the data source, while users in IT can use the app normally. What is the most likely cause?

You are troubleshooting a Power Automate flow that uses an HTTP action to call a REST API. The flow fails with a '429 Too Many Requests' error. The API has a rate limit of 100 requests per minute. Which strategy should you implement to handle this error gracefully?