Troubleshooting practice questions

Which TWO are best practices for designing Power Automate flows in a production environment? (Select TWO.)

Trap 1: Disable flow logging to improve performance.

Logging is important for monitoring and troubleshooting.

Trap 2: Nest Apply to each actions to handle large datasets.

Nesting can cause performance issues; use parallel or pagination.

Trap 3: Hardcode connection references for simplicity.

Hardcoding is not a best practice; use secure inputs.

A
Disable flow logging to improve performance.
Why wrong: Logging is important for monitoring and troubleshooting.
B
Use 'Configure Run After' to implement error handling.
This handles failures gracefully.
C
Nest Apply to each actions to handle large datasets.
Why wrong: Nesting can cause performance issues; use parallel or pagination.
D
Hardcode connection references for simplicity.
Why wrong: Hardcoding is not a best practice; use secure inputs.
E
Use secure inputs and outputs for actions handling sensitive data.
Protects sensitive data in logs.

Question 2hardmultiple choice

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"
  }
}

Trap 1: The Office 365 connector is conflicting with the SQL connector.

Multiple connectors can coexist in a flow without conflict.

Trap 2: The environment type is Production, which restricts access to…

Production environments can connect to on-premises data with a gateway.

Trap 3: The region 'eastus' does not support on-premises connectivity.

All Azure regions support on-premises data gateways.

A
The Office 365 connector is conflicting with the SQL connector.
Why wrong: 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 requires a gateway for on-premises databases.
C
The environment type is Production, which restricts access to on-premises data.
Why wrong: Production environments can connect to on-premises data with a gateway.
D
The region 'eastus' does not support on-premises connectivity.
Why wrong: All Azure regions support on-premises data gateways.

Question 3hardmultiple choice

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?

Trap 1: Increase the data row limit for each data source

Increasing row limit can slow performance.

Trap 2: Disable the formula-level error checking

Error checking does not impact app performance.

Trap 3: Remove unused data sources from the app

Unused data sources do not affect runtime performance.

A
Increase the data row limit for each data source
Why wrong: Increasing row limit can slow performance.
B
Use delegable queries to filter data at the source
Delegation pushes filtering to the data source, reducing data transfer.
C
Disable the formula-level error checking
Why wrong: Error checking does not impact app performance.
D
Remove unused data sources from the app
Why wrong: Unused data sources do not affect runtime performance.

Question 4mediummultiple choice

You are troubleshooting a Power Apps issue. Using PowerShell, you run Get-AdminPowerApp and see the exhibit output. What does the EnvironmentName field indicate?

Exhibit

Refer to the exhibit.
```
PowerShell cmdlet: Get-AdminPowerApp
Sample output:
AppName        : SalesPipelineApp
CreatedTime    : 2024-01-15T10:30:00Z
LastModifiedTime : 2024-06-20T14:00:00Z
Owner          : user@contoso.com
EnvironmentName : Default-12345678-1234-1234-1234-123456789abc
```

Trap 1: The license key for Power Apps.

License keys are different.

Trap 2: The name of the custom connector used by the app.

Custom connectors have different identifiers.

Trap 3: The name of the SharePoint site where the app is stored.

Apps are stored in Dataverse environments.

A
The license key for Power Apps.
Why wrong: License keys are different.
B
The unique identifier of the Dataverse environment hosting the app.
Each environment has a unique GUID.
C
The name of the custom connector used by the app.
Why wrong: Custom connectors have different identifiers.
D
The name of the SharePoint site where the app is stored.
Why wrong: Apps are stored in Dataverse environments.

Question 5mediummulti select

Which TWO of the following are capabilities of Power Automate that help with monitoring and troubleshooting flows?

Trap 1: The 'When a flow is completed' trigger

Incorrect. The 'When a flow is completed' trigger is not a monitoring capability; it is used to start another flow when a selected flow finishes, which is an automation trigger, not a monitoring or troubleshooting tool.

Trap 2: Automatic email notifications when a flow fails

Incorrect. While you can configure notifications in a flow, automatic email notifications when a flow fails are not a built-in monitoring feature of Power Automate; they would require additional configuration and are not considered a core monitoring capability.

Trap 3: The 'Configure run after' setting

Incorrect. The 'Configure run after' setting allows you to define the behavior of subsequent actions based on the outcome of a previous action (e.g., run after failure, success, timeout). It is a flow logic configuration, not a monitoring or troubleshooting capability.

A
The 'When a flow is completed' trigger
Why wrong: Incorrect. The 'When a flow is completed' trigger is not a monitoring capability; it is used to start another flow when a selected flow finishes, which is an automation trigger, not a monitoring or troubleshooting tool.
B
Automatic email notifications when a flow fails
Why wrong: Incorrect. While you can configure notifications in a flow, automatic email notifications when a flow fails are not a built-in monitoring feature of Power Automate; they would require additional configuration and are not considered a core monitoring capability.
C
Analytics in the Power Platform admin center
Correct. Analytics in the Power Platform admin center provide dashboards and reports on flow usage, performance, and errors, enabling monitoring and troubleshooting at an administrative level.
D
Run history for each flow execution
Correct. Run history for each flow execution captures detailed logs of each run, including inputs, outputs, and error messages, making it a key troubleshooting tool for flow developers.
E
The 'Configure run after' setting
Why wrong: Incorrect. The 'Configure run after' setting allows you to define the behavior of subsequent actions based on the outcome of a previous action (e.g., run after failure, success, timeout). It is a flow logic configuration, not a monitoring or troubleshooting capability.

Question 6hardmultiple choice

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?

Trap 1: Replace the DirectQuery connection with an Import connection

This would require a full data load and might not address the immediate issue.

Trap 2: Ask the database team to add more indexes to the SQL Server tables

The database team confirmed the server is not under load, so indexing may not be the issue.

Trap 3: Increase the scheduled refresh frequency to every 15 minutes

DirectQuery does not use scheduled refresh; it queries live.

A
Check the on-premises data gateway performance and logs for errors
Slow load and data errors often indicate gateway issues.
B
Replace the DirectQuery connection with an Import connection
Why wrong: This would require a full data load and might not address the immediate issue.
C
Ask the database team to add more indexes to the SQL Server tables
Why wrong: The database team confirmed the server is not under load, so indexing may not be the issue.
D
Increase the scheduled refresh frequency to every 15 minutes
Why wrong: DirectQuery does not use scheduled refresh; it queries live.

Question 7hardmultiple choice

You are troubleshooting a Power Pages site where authenticated users in the 'Partner' web role cannot see any records from a Dataverse table, even though the table permission is set to 'Read' with 'Contact' scope. The site uses a custom page that retrieves data via a Liquid template. What is the most likely cause?

Trap 1: The 'Partner' web role does not inherit the 'Authenticated Users'…

Web roles are independent; inheritance is not automatic.

Trap 2: The Liquid template is using a direct Web API call that bypasses…

Liquid templates respect table permissions when configured properly.

Trap 3: The contact record for the user does not have the correct 'Owner'…

Contact scope matches the user's contact, not ownership.

A
The 'Partner' web role does not inherit the 'Authenticated Users' role permissions.
Why wrong: Web roles are independent; inheritance is not automatic.
B
The table permission is not enabled for the 'Partner' web role.
Each web role must be explicitly granted the table permission.
C
The Liquid template is using a direct Web API call that bypasses table permissions.
Why wrong: Liquid templates respect table permissions when configured properly.
D
The contact record for the user does not have the correct 'Owner' value.
Why wrong: Contact scope matches the user's contact, not ownership.

Question 8hardmultiple choice

A developer is troubleshooting a canvas app that uses a SharePoint list as a data source. The app works for some users but fails for others with the error 'Access denied.' All users have read access to the SharePoint list. What could be the issue?

Trap 1: The SharePoint list is set to private

Private lists would not allow any read access.

Trap 2: The users do not have Power Apps licenses

License would prevent app access entirely, not just data.

Trap 3: The app is in a different environment than the users

Environment does not affect data permissions.

A
The users do not have permissions to the SharePoint list
Power Apps inherits SharePoint permissions; users need read access to the list.
B
The SharePoint list is set to private
Why wrong: Private lists would not allow any read access.
C
The users do not have Power Apps licenses
Why wrong: License would prevent app access entirely, not just data.
D
The app is in a different environment than the users
Why wrong: Environment does not affect data permissions.

Question 9hardmultiple choice

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?

Trap 1: Increase the flow's concurrency setting to process more requests…

More concurrency would increase rate limit hits.

Trap 2: Use a 'Condition' action to check the status code and ignore 429…

Ignoring errors would miss API calls.

Trap 3: Use the 'Configure Run After' option to skip the action on failure.

Skipping on failure does not retry.

A
Implement retry logic with exponential backoff in the HTTP action settings.
Exponential backoff reduces request rate after 429 responses.
B
Increase the flow's concurrency setting to process more requests simultaneously.
Why wrong: More concurrency would increase rate limit hits.
C
Use a 'Condition' action to check the status code and ignore 429 errors.
Why wrong: Ignoring errors would miss API calls.
D
Use the 'Configure Run After' option to skip the action on failure.
Why wrong: Skipping on failure does not retry.