PL-900 · topic practice
Practise Microsoft Power Platform Fundamentals PL-900 Demonstrate the capabilities of Power Apps practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.
Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.
What the exam tests
Demonstrate the capabilities of Power Apps 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.
Watch out for
Practice set
20 questions · select your answer, then reveal the explanation
Trap 1: Screens
Screens are for canvas apps.
Trap 2: Triggers
Triggers are for Power Automate.
Forms
Forms display data entry.
Views
Views define data lists.
Screens
Why wrong: Screens are for canvas apps.
Triggers
Why wrong: Triggers are for Power Automate.
Sitemap
Sitemap defines navigation.
Trap 1: Use a SQL Server database instead of SharePoint
Migrating to SQL Server does not address the specific 5,000-item delegation limit in SharePoint that causes the Canvas app to freeze; the app would still need to load data through SharePoint connectors unless the data source is fully replaced. This option is tempting because SQL Server handles large datasets efficiently, making it a correct choice when the requirement is to store and query high-volume relational data independently of SharePoint’s list thresholds.
Trap 2: Move the data to a Microsoft Dataverse table
Dataverse does not have the 5,000 item limit, but moving data is not the immediate solution.
Trap 3: Increase the data row limit in Power Apps settings to 10,000
The delegate limit in SharePoint is 5,000; increasing the row limit does not bypass delegation.
Use a SQL Server database instead of SharePoint
Why wrong: Migrating to SQL Server does not address the specific 5,000-item delegation limit in SharePoint that causes the Canvas app to freeze; the app would still need to load data through SharePoint connectors unless the data source is fully replaced. This option is tempting because SQL Server handles large datasets efficiently, making it a correct choice when the requirement is to store and query high-volume relational data independently of SharePoint’s list thresholds.
Add filters to the data source to delegate the query and reduce the data loaded
Delegation ensures only filtered data is retrieved, avoiding the 5,000 item limit.
Move the data to a Microsoft Dataverse table
Why wrong: Dataverse does not have the 5,000 item limit, but moving data is not the immediate solution.
Increase the data row limit in Power Apps settings to 10,000
Why wrong: The delegate limit in SharePoint is 5,000; increasing the row limit does not bypass delegation.
Trap 1: Use a business rule to hide closed opportunities
Business rules affect form fields, not subgrid filtering.
Trap 2: Set a calculated field to mark opportunities as open
Calculated fields compute values but do not filter subgrids.
Trap 3: Create a workflow to remove closed opportunities from the subgrid
Workflows run asynchronously and cannot filter subgrids dynamically.
Add a subgrid and select a view that filters for status equals 'Open'
Views define the filter criteria for subgrid rows.
Use a business rule to hide closed opportunities
Why wrong: Business rules affect form fields, not subgrid filtering.
Set a calculated field to mark opportunities as open
Why wrong: Calculated fields compute values but do not filter subgrids.
Create a workflow to remove closed opportunities from the subgrid
Why wrong: Workflows run asynchronously and cannot filter subgrids dynamically.
Trap 1: Model-driven app, because it uses standard Dataverse forms
Model-driven apps are less customizable for custom input forms.
Trap 2: AI Builder app, because it can process receipts automatically
AI Builder is a component, not an app type.
Trap 3: Power Apps portal, because it allows external users to submit…
Portals are for external users, not internal employees.
Canvas app, because it provides flexible form design and supports file attachments
Canvas apps allow custom layouts and attachment controls.
Model-driven app, because it uses standard Dataverse forms
Why wrong: Model-driven apps are less customizable for custom input forms.
AI Builder app, because it can process receipts automatically
Why wrong: AI Builder is a component, not an app type.
Power Apps portal, because it allows external users to submit expenses
Why wrong: Portals are for external users, not internal employees.
Refer to the exhibit.
```json
{
"name": "TestPolicy",
"rules": [
{
"entity": "account",
"conditions": [
{
"attribute": "revenue",
"operator": "greater-than",
"value": 1000000
}
],
"actions": [
{
"type": "set-attribute",
"attribute": "description",
"value": "High-value account"
}
]
}
]
}
```Trap 1: The save operation will be blocked
Incorrect. The policy does not include a 'Block save' action; it only sets a field value.
Trap 2: A task will be created for the account owner
Incorrect. The action is to set description, not to change revenue.
Trap 3: The revenue field will be updated to 1,000,000
Incorrect. The action is to set an attribute, not to create a task.
The description field will be updated to 'High-value account'
Correct. The policy condition (revenue > 1,000,000) is true, so the action sets description to 'High-value account'.
The save operation will be blocked
Why wrong: Incorrect. The policy does not include a 'Block save' action; it only sets a field value.
A task will be created for the account owner
Why wrong: Incorrect. The action is to set description, not to change revenue.
The revenue field will be updated to 1,000,000
Why wrong: Incorrect. The action is to set an attribute, not to create a task.
Trap 1: A calculated field that computes the difference between created and…
Calculated fields work on the same record only and cannot reference status changes.
Trap 2: A business rule that sets the resolution time field when the status…
Business rules can set fields but they run on form load or field change, not on save or status change.
Trap 3: A scheduled Power Automate flow that runs every hour and updates…
Scheduled flows are not triggered by status change and would be inefficient.
A calculated field that computes the difference between created and resolved dates.
Why wrong: Calculated fields work on the same record only and cannot reference status changes.
A real-time workflow (cloud flow) triggered when a case is resolved.
Real-time workflows can run synchronously when a record's status changes and perform calculations.
A business rule that sets the resolution time field when the status changes.
Why wrong: Business rules can set fields but they run on form load or field change, not on save or status change.
A scheduled Power Automate flow that runs every hour and updates resolved cases.
Why wrong: Scheduled flows are not triggered by status change and would be inefficient.
Trap 1: Use SharePoint external sharing settings
Does not apply to Power Apps authentication.
Trap 2: Enable anonymous access in Power Apps
Anonymous access is not suitable for authenticated partners.
Trap 3: Configure Azure AD B2C for the app
B2C is for customer identities, not B2B partner scenarios.
Use SharePoint external sharing settings
Why wrong: Does not apply to Power Apps authentication.
Enable anonymous access in Power Apps
Why wrong: Anonymous access is not suitable for authenticated partners.
Set up Azure AD B2B guest user access
Allows external partners to use their own Azure AD credentials.
Configure Azure AD B2C for the app
Why wrong: B2C is for customer identities, not B2B partner scenarios.
Trap 1: Object detection in images
Object Detection is not a prebuilt AI Builder model; it requires custom model training or integration with Azure Cognitive Services, so it is incorrect.
Trap 2: Predictive forecasting
Predictive Forecasting is not an AI Builder feature; it is part of Power BI or other services, so it is incorrect.
Form processing
Form Processing is a prebuilt AI Builder model that extracts key-value pairs from documents, making it correct.
Text classification
Text Classification is a prebuilt AI Builder model that categorizes text into custom categories, so it is correct.
Sentiment analysis
Sentiment Analysis is a prebuilt AI Builder model that identifies positive, negative, or neutral sentiment, so it is correct.
Object detection in images
Why wrong: Object Detection is not a prebuilt AI Builder model; it requires custom model training or integration with Azure Cognitive Services, so it is incorrect.
Predictive forecasting
Why wrong: Predictive Forecasting is not an AI Builder feature; it is part of Power BI or other services, so it is incorrect.
Trap 1: Power Pages form
Power Pages forms are not data sources.
Trap 2: Power Virtual Agents topic
Power Virtual Agents is not a data source.
Trap 3: Power BI dataset
Power BI datasets cannot be directly used as a data source in canvas apps.
Power Pages form
Why wrong: Power Pages forms are not data sources.
SharePoint list
Canvas apps can connect to SharePoint lists directly.
Power Virtual Agents topic
Why wrong: Power Virtual Agents is not a data source.
SQL Server database
Canvas apps can connect to SQL Server via connector.
Power BI dataset
Why wrong: Power BI datasets cannot be directly used as a data source in canvas apps.
Trap 1: Add users as co-owners of the app
Co-owners can edit, not just use.
Trap 2: Create a Power Automate flow to grant access
Not necessary.
Trap 3: Share the app with the group and grant Can Use permission
Missing data permission.
Add users as co-owners of the app
Why wrong: Co-owners can edit, not just use.
Create a Power Automate flow to grant access
Why wrong: Not necessary.
Share the app with the group and ensure the group has access to the SharePoint list
Both app and data permissions required.
Share the app with the group and grant Can Use permission
Why wrong: Missing data permission.
Trap 1: Power Automate
Incorrect: Power Automate automates workflows, not AI suggestions.
Trap 2: Power Virtual Agents
Incorrect: Used for chatbots, not inline suggestions.
Trap 3: Copilot in Power Apps
Incorrect: Copilot helps build apps but doesn't add AI suggestions.
Power Automate
Why wrong: Incorrect: Power Automate automates workflows, not AI suggestions.
AI Builder
Correct: AI Builder provides prebuilt AI models to integrate into apps.
Power Virtual Agents
Why wrong: Incorrect: Used for chatbots, not inline suggestions.
Copilot in Power Apps
Why wrong: Incorrect: Copilot helps build apps but doesn't add AI suggestions.
Trap 1: The group membership change takes 24 hours to propagate
This is incorrect. Group membership propagation typically takes only a few minutes, not 24 hours. While there might be a short delay, the 24-hour claim is inaccurate.
Trap 2: The app share does not automatically include new group members; the…
This is incorrect. In Power Apps, when an app is shared with a group, new members added to the group automatically gain access after a short propagation period. Re-sharing the app is not necessary.
Trap 3: The app has a caching issue that prevents permission updates
This is incorrect. While caching issues could cause temporary delays, they are not the most likely reason for persistent access denial. The issue is more likely related to sharing configuration.
The group membership change takes 24 hours to propagate
Why wrong: This is incorrect. Group membership propagation typically takes only a few minutes, not 24 hours. While there might be a short delay, the 24-hour claim is inaccurate.
The app share does not automatically include new group members; the app must be re-shared
Why wrong: This is incorrect. In Power Apps, when an app is shared with a group, new members added to the group automatically gain access after a short propagation period. Re-sharing the app is not necessary.
The app is shared with individual users, not the group
This is correct. If the app was shared with individual users instead of the group, adding users to the group will not grant them access. The app must be shared with the group for group membership to control access.
The app has a caching issue that prevents permission updates
Why wrong: This is incorrect. While caching issues could cause temporary delays, they are not the most likely reason for persistent access denial. The issue is more likely related to sharing configuration.
Trap 1: Copilot Studio
Incorrect: Not for offline apps.
Trap 2: Power Pages
Incorrect: Power Pages require internet.
Trap 3: Model-driven app
Incorrect: Model-driven apps require connectivity.
Canvas app
Correct: Canvas apps can be enabled for offline use.
Copilot Studio
Why wrong: Incorrect: Not for offline apps.
Power Pages
Why wrong: Incorrect: Power Pages require internet.
Model-driven app
Why wrong: Incorrect: Model-driven apps require connectivity.
Trap 1: Canvas app with standard connector to travel API and Power Automate
Incorrect: Standard connectors may not exist for the travel system; custom connector is needed.
Trap 2: Canvas app with AI Builder to extract trip details and Power…
Incorrect: AI Builder is not needed; the travel system has an API.
Trap 3: Model-driven app with Dataverse and Power Automate for approval
Incorrect: Model-driven apps are not as customizable for mobile UI.
Canvas app with custom connector to travel API, and Power Automate for conditional approval
Correct: Canvas app provides mobile UI, custom connector integrates API, Power Automate handles approval logic.
Canvas app with standard connector to travel API and Power Automate
Why wrong: Incorrect: Standard connectors may not exist for the travel system; custom connector is needed.
Canvas app with AI Builder to extract trip details and Power Automate for approval
Why wrong: Incorrect: AI Builder is not needed; the travel system has an API.
Model-driven app with Dataverse and Power Automate for approval
Why wrong: Incorrect: Model-driven apps are not as customizable for mobile UI.
Trap 1: Real-time co-authoring of canvas apps
Co-authoring is a Power Apps feature, not a Dataverse capability.
Trap 2: Server-side pagination for large datasets
Pagination is handled at the app or query level.
Role-based security to control access to data
Dataverse uses role-based security to control data access.
Calculated fields and rollup fields
Dataverse supports calculated and rollup fields.
Real-time co-authoring of canvas apps
Why wrong: Co-authoring is a Power Apps feature, not a Dataverse capability.
Business rules to enforce logic on forms
Business rules can be configured in Dataverse to run on forms.
Server-side pagination for large datasets
Why wrong: Pagination is handled at the app or query level.
Trap 1: Copilot Studio bot
Copilot Studio creates chatbots, not Power Apps.
Trap 2: Flow app
Flow is not an app type; it's Power Automate.
Trap 3: Power BI report
Power BI reports are analytics, not apps.
Model-driven app
Model-driven apps are data-centric and use Dataverse.
Copilot Studio bot
Why wrong: Copilot Studio creates chatbots, not Power Apps.
Canvas app
Canvas apps allow custom layout and design.
Flow app
Why wrong: Flow is not an app type; it's Power Automate.
Power BI report
Why wrong: Power BI reports are analytics, not apps.
Trap 1: Add a business rule to the Dataverse table that sets a validation…
Incorrect. Dataverse business rules are not triggered by canvas app submissions; they apply in model-driven apps and cannot prevent the invalid data entry in a canvas app.
Trap 2: Add a workflow in Power Automate to validate the quantity after…
Incorrect. A Power Automate workflow runs after submission and cannot prevent the invalid data entry from being saved.
Trap 3: Add a validation rule in the form control to check if…
Incorrect. Form validation rules in a canvas app are client-side but may still allow submission if the rule is bypassed; using Patch with If is a more direct approach.
Add a business rule to the Dataverse table that sets a validation message when QuantityOnHand < 0.
Why wrong: Incorrect. Dataverse business rules are not triggered by canvas app submissions; they apply in model-driven apps and cannot prevent the invalid data entry in a canvas app.
Use the Patch function with an If condition to check the value before updating.
Correct. Using the Patch function with an If condition allows real-time client-side validation before the data is sent to Dataverse. This ensures that the quantity is not reduced below zero and an error can be displayed to the user immediately.
Add a workflow in Power Automate to validate the quantity after submission.
Why wrong: Incorrect. A Power Automate workflow runs after submission and cannot prevent the invalid data entry from being saved.
Add a validation rule in the form control to check if QuantityOnHand >= 0 before submitting.
Why wrong: Incorrect. Form validation rules in a canvas app are client-side but may still allow submission if the rule is bypassed; using Patch with If is a more direct approach.
Trap 1: Use Power BI to notify managers.
Power BI is not designed for approval workflows.
Trap 2: Add an approval step in the canvas app using the 'Approval'…
The Approval connector is used in Power Automate, not directly in canvas apps.
Trap 3: Create a business rule in Dataverse to send email.
Business rules cannot initiate approval workflows.
Use Power BI to notify managers.
Why wrong: Power BI is not designed for approval workflows.
Use Power Automate with the 'Start and wait for an approval' action.
Power Automate has built-in approval actions that can be triggered from the app.
Add an approval step in the canvas app using the 'Approval' connector.
Why wrong: The Approval connector is used in Power Automate, not directly in canvas apps.
Create a business rule in Dataverse to send email.
Why wrong: Business rules cannot initiate approval workflows.
Trap 1: Portal
Portals are for external users and require connectivity.
Trap 2: Model-driven app
Model-driven apps are not designed for offline use.
Trap 3: Power Automate
Power Automate is a workflow tool, not an app type.
Portal
Why wrong: Portals are for external users and require connectivity.
Model-driven app
Why wrong: Model-driven apps are not designed for offline use.
Canvas app
Canvas apps can be built to work offline with the Power Apps mobile player.
Power Automate
Why wrong: Power Automate is a workflow tool, not an app type.
Trap 1: Portal
Portals are not suitable for internal tracking.
Trap 2: Power Automate
Power Automate is a separate product.
Trap 3: Canvas app
Canvas apps require custom components for timeline.
Portal
Why wrong: Portals are not suitable for internal tracking.
Model-driven app
Model-driven apps provide built-in timeline and Dataverse integration.
Power Automate
Why wrong: Power Automate is a separate product.
Canvas app
Why wrong: Canvas apps require custom components for timeline.
Free account
Create a free account to save your results and see which topics improve across sessions.
Focused Demonstrate the capabilities of Power Apps sessions
Every question in these sessions is drawn from the Demonstrate the capabilities of Power Apps domain — nothing else.
Related practice questions
Move into related areas when this topic feels solid.
Practise PL-900 questions linked to Demonstrate the capabilities of Power Automate.
Describe the business value of Microsoft Power Platform practice questions for PL-900.
Manage the Microsoft Power Platform environment practice questions for PL-900.
Sharpen your PL-900 knowledge of Demonstrate the capabilities of Power Apps.
Targeted PL-900 practice covering Demonstrate the capabilities of Microsoft Copilot Studio.
Work through PL-900 questions on PL-900 fundamentals.
Work through PL-900 questions on PL-900 scenario.
Targeted PL-900 practice covering PL-900 troubleshooting.
Demonstrate the capabilities of Power Apps only
Mixed PL-900 sessionA free account saves results across sessions and highlights which topics need work.
Sign up free