Demonstrate the capabilities of Power Apps →easyMultiple Choice

PL-900 Demonstrate the capabilities of Power Apps Practice Question

Exhibit

{
  "name": "Filter",
  "parameters": [
    {
      "name": "source",
      "type": "table",
      "description": "The data source to filter"
    },
    {
      "name": "formula",
      "type": "boolean",
      "description": "A boolean expression to evaluate for each record"
    }
  ],
  "returnType": "table"
}

Refer to the exhibit. The JSON describes a Power Apps function. Which call to this function will return a table of records where the 'Status' column equals 'Active'?

⚠ Common exam trap

PL-900 often tests the correct argument order and syntax of the Filter function, causing candidates to reverse the arguments or misuse quotes around column names.

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, Status = 'Active')

The Filter function in Power Apps takes a data source as the first argument and a logical expression as the second argument. The correct syntax is Filter(Accounts, Status = 'Active'), which returns records where the Status column equals 'Active'.

Answer analysis

Option-by-option breakdown

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

✗
Filter(Accounts, 'Active')
Why it's wrong here
Filter requires a logical expression, not a bare string; 'Active' is passed as the condition itself, so no comparison against the Status column occurs. It is tempting because Filter's first argument is the data source, and Accounts is correctly placed there — that pattern would be right if the second argument were a boolean predicate.
✓
Filter(Accounts, Status = 'Active')
Why this is correct
Filter returns a table of records matching the condition, and Status = 'Active' selects only rows where the Status column equals Active. This satisfies the requirement to return a table filtered by that column value.
✗
Filter('Active', Accounts)
Why it's wrong here
The arguments are reversed: Filter expects the data source first and the predicate second, so 'Active' is treated as the table and Accounts as the condition. It is tempting because both required elements appear, and swapping them would be correct if 'Active' named a collection of records to filter.
✗
Filter(Status = 'Active', Accounts)
Why it's wrong here
The predicate is placed first and the data source second, so Filter receives a boolean where a table is expected. It is tempting because the comparison Status = 'Active' is exactly the right condition, and would be correct if written as the second argument after Accounts.

Go deeper

PL-900 Demonstrate the capabilities of Power Apps Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question