Question 370 of 976

Identify foundational components of Microsoft Power Platform →hardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to modify the submit button to disable after the first click and index the SalesPerson column in Dataverse to enable delegation. This works because disabling the button prevents duplicate records from double-clicking, while indexing the column ensures the Filter function delegates—meaning the query runs server-side on Dataverse, returning only the current user’s rows instead of pulling all 50,000 records client-side, which eliminates the slow load and timeout. On the PL-900 exam, this tests your understanding of delegation as a core performance concept for canvas apps connecting to large data sources; a common trap is assuming all filters delegate by default, but only indexed columns on the server side allow it. Remember the mnemonic “D.I.D.”—Disable, Index, Delegate—to recall the three-part fix for slow, duplicate-prone apps.

PL-900 Practice Question: Identify foundational components of Microsoft Power Platform

This PL-900 practice question tests your understanding of identify foundational components of microsoft power platform. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

You are the Power Platform administrator for Contoso Ltd., a retail company with 500 employees. The company uses Microsoft 365 and has recently adopted Power Platform. The IT department manages a Power Apps canvas app used by the sales team to track customer interactions. The app connects to a Microsoft Dataverse table named 'Customer Interactions' with columns: CustomerID (text), InteractionDate (date), Notes (text), and SalesPerson (text). The app was working fine for three months, but starting last week, users report that the app loads slowly, sometimes timing out, and the 'Customer Interactions' table shows duplicate records. Upon investigation, you find that the app uses a 'Patch' function to create records, and the 'OnStart' property loads all records from the table using 'Filter(Customer Interactions, SalesPerson = User().FullName)' to show only the current user's records. The Dataverse table has grown to 50,000 rows. Additionally, some users have accidentally created multiple submissions by double-clicking the submit button. You need to resolve the performance and duplicate issues with minimal disruption. What should you do?

Question 1hardmultiple choice

Read the full NAT/PAT explanation →

A
Replace the 'Patch' function with 'Collect' in the app and use the 'Distinct' function to remove duplicates from the table every night via a Power Automate flow.
Why wrong: Using 'Collect' does not prevent duplicates at submission time; a nightly cleanup is reactive and does not resolve the performance issue.
B
Increase the 'Data row limit' for the 'Customer Interactions' table in the app settings to 500 and add a 'Remove duplicates' step in the app's 'OnStart'.
Why wrong: Increasing the row limit may help load more records but does not prevent duplicate submissions; the 'Remove duplicates' step would be client-side and inefficient for 50,000 rows.
C
Remove the 'Filter' from 'OnStart' and load all records into a collection, then use 'Filter' on the collection to show current user's records.
Why wrong: Loading all 50,000 records into a collection would cause performance issues and timeouts, and does not address duplicates.
D
Modify the 'Submit' button to set its 'DisplayMode' to 'Disabled' after the first click to prevent double submission, and change the 'OnStart' filter to delegate by ensuring the 'SalesPerson' column is indexed in Dataverse and using 'Filter(Customer Interactions, SalesPerson = User().FullName)' with delegation enabled.
This directly addresses both issues: disabling the button prevents duplicates, and delegated filtering improves performance by only loading relevant records.

Full breakdown with real-world context →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Modify the 'Submit' button to set its 'DisplayMode' to 'Disabled' after the first click to prevent double submission, and change the 'OnStart' filter to delegate by ensuring the 'SalesPerson' column is indexed in Dataverse and using 'Filter(Customer Interactions, SalesPerson = User().FullName)' with delegation enabled.

Option D is correct because it addresses both performance and duplicate issues directly. Disabling the submit button after the first click prevents double submissions, a common cause of duplicates in canvas apps. Indexing the SalesPerson column in Dataverse ensures the Filter function delegates, meaning the query runs on the server side and only returns relevant rows, drastically reducing data transfer and load times compared to pulling all 50,000 rows client-side.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Replace the 'Patch' function with 'Collect' in the app and use the 'Distinct' function to remove duplicates from the table every night via a Power Automate flow.
Why it's wrong here
Using 'Collect' does not prevent duplicates at submission time; a nightly cleanup is reactive and does not resolve the performance issue.
✗
Increase the 'Data row limit' for the 'Customer Interactions' table in the app settings to 500 and add a 'Remove duplicates' step in the app's 'OnStart'.
Why it's wrong here
Increasing the row limit may help load more records but does not prevent duplicate submissions; the 'Remove duplicates' step would be client-side and inefficient for 50,000 rows.
✗
Remove the 'Filter' from 'OnStart' and load all records into a collection, then use 'Filter' on the collection to show current user's records.
Why it's wrong here
Loading all 50,000 records into a collection would cause performance issues and timeouts, and does not address duplicates.
✓
Modify the 'Submit' button to set its 'DisplayMode' to 'Disabled' after the first click to prevent double submission, and change the 'OnStart' filter to delegate by ensuring the 'SalesPerson' column is indexed in Dataverse and using 'Filter(Customer Interactions, SalesPerson = User().FullName)' with delegation enabled.
Why this is correct
This directly addresses both issues: disabling the button prevents duplicates, and delegated filtering improves performance by only loading relevant records.
Related concept
Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often think loading all data into a collection (Option C) or using a nightly cleanup flow (Option A) is acceptable, but they miss that delegation and preventing duplicates at the source are the correct, minimal-disruption solutions for performance and data integrity.

Detailed technical explanation

How to think about this question

Delegation in Power Apps is critical for performance with large Dataverse tables; when a filter cannot be delegated, Power Apps retrieves the full table (up to the data row limit, default 500) and applies the filter locally, which is inefficient for 50,000 rows. Indexing the SalesPerson column in Dataverse allows the Filter function to delegate, so the query is executed server-side and only matching rows are returned. The DisplayMode property of a button can be set to Disabled after the first click using a context variable, which is a simple and effective pattern to prevent duplicate submissions without complex logic.

KKey Concepts to Remember

Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.

TExam Day Tips

Watch for words such as best, first, most likely and least administrative effort.
Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related PL-900 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Identify foundational components of Power Platform practice questions

Practise PL-900 questions linked to Identify foundational components of Power Platform.

Demonstrate capabilities of Power BI practice questions

Practise PL-900 questions linked to Demonstrate capabilities of Power BI.

Describe complementary Microsoft Power Platform solutions practice questions

Practise PL-900 questions linked to Describe complementary Microsoft Power Platform solutions.

Demonstrate the capabilities of Power Automate practice questions

Practise PL-900 questions linked to Demonstrate the capabilities of Power Automate.

Describe the business value of Microsoft Power Platform practice questions

Practise PL-900 questions linked to Describe the business value of Microsoft Power Platform.

Manage the Microsoft Power Platform environment practice questions

Practise PL-900 questions linked to Manage the Microsoft Power Platform environment.

Identify foundational components of Microsoft Power Platform practice questions

Practise PL-900 questions linked to Identify foundational components of Microsoft Power Platform.

Demonstrate the capabilities of Power BI practice questions

Practise PL-900 questions linked to Demonstrate the capabilities of Power BI.

Demonstrate the capabilities of Power Apps practice questions

Practise PL-900 questions linked to Demonstrate the capabilities of Power Apps.

Demonstrate the capabilities of Microsoft Copilot Studio practice questions

Practise PL-900 questions linked to Demonstrate the capabilities of Microsoft Copilot Studio.

Demonstrate the capabilities of Power Pages practice questions

Practise PL-900 questions linked to Demonstrate the capabilities of Power Pages.

PL-900 fundamentals practice questions

Practise PL-900 questions linked to PL-900 fundamentals.

Practice this exam

Start a free PL-900 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

PL-900 practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this PL-900 question test?

Identify foundational components of Microsoft Power Platform — This question tests Identify foundational components of Microsoft Power Platform — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Modify the 'Submit' button to set its 'DisplayMode' to 'Disabled' after the first click to prevent double submission, and change the 'OnStart' filter to delegate by ensuring the 'SalesPerson' column is indexed in Dataverse and using 'Filter(Customer Interactions, SalesPerson = User().FullName)' with delegation enabled. — Option D is correct because it addresses both performance and duplicate issues directly. Disabling the submit button after the first click prevents double submissions, a common cause of duplicates in canvas apps. Indexing the SalesPerson column in Dataverse ensures the Filter function delegates, meaning the query runs on the server side and only returns relevant rows, drastically reducing data transfer and load times compared to pulling all 50,000 rows client-side.

What should I do if I get this PL-900 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on PL-900

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A sales team uses a Canvas app to track leads. Users report that the app loads slowly when accessing on mobile devices. Which component should be optimized to improve performance?

medium

A.Update the app version number
✓ B.Optimize data source connections and queries
C.Increase the app icon size
D.Change the app's background color

Why B: Optimizing data source connections and queries directly reduces the amount of data transferred and the number of round trips between the Canvas app and its data source (e.g., Dataverse, SharePoint, SQL). On mobile devices, network latency and bandwidth are often constrained, so inefficient queries (e.g., loading all records instead of using filters) cause significant slowdowns. This is the primary performance lever for Canvas apps, as per Microsoft's guidance on app optimization.

Keep practising

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

This PL-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-900 exam.