Demonstrate the capabilities of Power Apps →mediumMultiple Choice

PL-900 Demonstrate the capabilities of Power Apps Practice Question

Refer to the exhibit. The following JSON shows a Power Apps component (canvas app) manifest snippet:

{
  "properties": {
    "dataSources": [
      {
        "name": "SalesData",
        "type": "Microsoft Dataverse",
        "entity": "accounts"
      }
    ],
    "screens": [
      {
        "name": "MainScreen",
        "controls": [
          {
            "name": "AccountGallery",
            "type": "Gallery",
            "items": "Filter(SalesData, status = 'Active')"
          }
        ]
      }
    ]
  }
}

What is the data source for the gallery named AccountGallery?

⚠ Common exam trap

The trap is overlooking the Filter function and assuming the gallery uses the raw entity; candidates might pick the raw entity instead of the filtered data source.

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

✓

The filtered Dataverse Accounts data source

The gallery named AccountGallery has its Items property set to 'Filter(SalesData, status = 'Active')'. SalesData is defined as a data source of type Microsoft Dataverse, entity 'accounts'. Therefore, the data source is the filtered Dataverse Accounts data source. The filter is applied to the Accounts entity, so it is not the raw entity but a filtered view.

Answer analysis

Option-by-option breakdown

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

✓
The filtered Dataverse Accounts data source
Why this is correct
The gallery's Items property binds to SalesData, a Microsoft Dataverse data source pointing at the accounts entity, with a Filter expression restricting rows to status = 'Active'. The gallery therefore draws its records from that filtered Dataverse Accounts source, satisfying the manifest's declared dataSources constraint.
✗
A SQL Server table named Accounts
Why it's wrong here
The manifest declares the data source as Microsoft Dataverse, entity accounts, so the gallery binds to that Dataverse table. A SQL Server table would appear as a SQL connector data source, which this JSON does not reference.
✗
A SharePoint list named SalesData
Why it's wrong here
The manifest declares the gallery's items as Filter(SalesData, ...) where SalesData maps to the Microsoft Dataverse accounts entity, not SharePoint. SharePoint lists are the source when the connector type is SharePoint and a site/list is bound, which this snippet does not show.
✗
The raw Dataverse Accounts entity
Why it's wrong here
The gallery's Items property applies Filter(SalesData, status = 'Active'), so it binds to a filtered subset of active account records, not the unfiltered entity. The raw Accounts entity is tempting because SalesData points at Dataverse accounts, and an unfiltered gallery would legitimately use that entity as its source.

Go deeper

PL-900 Demonstrate the capabilities of Power Apps Practice Question

Why each option matters

Option-by-option breakdown

Related to this question