PL-900 Demonstrate the capabilities of Power Apps Practice Question
An app maker creates a canvas app that uses Microsoft Dataverse as the data source. The app includes a gallery that displays all accounts. The app maker wants to filter the gallery to show only accounts where the 'City' field equals 'Seattle'. Which formula should be used in the Items property of the gallery?
⚠ Common exam trap
PL-900 often tests the confusion between Filter (returns a table), LookUp (returns one record), and Search (substring match) — candidates pick LookUp or Search because they sound like filtering, but only Filter returns the table shape a gallery requires.
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
✓
Filter(Accounts, City = "Seattle")
The Filter function in Power Apps returns a table of records that satisfy a Boolean condition, which is exactly what the gallery's Items property requires. Filter(Accounts, City = "Seattle") evaluates each record in the Accounts table and returns only those where the City column equals 'Seattle'. This is the canonical delegation-friendly pattern for Dataverse-backed galleries.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Accounts(City = "Seattle")
Why it's wrong here
Accounts is a data source, not a function, so it cannot accept a filter predicate; this syntax is invalid in Power Fx. It is tempting because it resembles SQL-style filtering, which would be correct if writing a query against a relational database rather than a canvas app.
- ✓
Filter(Accounts, City = "Seattle")
Why this is correct
Filter returns only records meeting the predicate, so the gallery shows accounts whose City column equals Seattle. The delegate-friendly syntax matches Dataverse column names directly, satisfying the requirement to restrict the gallery's Items to Seattle accounts rather than all accounts.
- ✗
LookUp(Accounts, City = "Seattle")
Why it's wrong here
LookUp returns a single record, not a table, so the gallery would receive one account rather than all Seattle accounts. It is tempting because LookUp is the right function when you need one matching record, such as populating a detail form.
- ✗
Search(Accounts, "Seattle", "City")
Why it's wrong here
Search matches substrings within a text column and returns partial matches, so it would also return cities such as 'Seattle Heights', not only exact 'Seattle' values. It is tempting because Search is the natural choice when you want fuzzy, contains-style matching across a text field.
Go deeper
Related to this question
About these practice questions
One of 701 original PL-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.