PL-900 Demonstrate the capabilities of Power Apps Practice Question
Exhibit
Refer to the exhibit.
```xml
<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">
<entity name="account">
<attribute name="name" />
<attribute name="accountid" />
<attribute name="createdon" />
<order attribute="name" descending="false" />
<filter type="and">
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="createdon" operator="last-x-days" value="30" />
</filter>
</entity>
</fetch>
```You are reviewing a FetchXML query used in a Power Apps component. The exhibit shows the query. What data will this query return?
⚠ Common exam trap
PL-900 often tests the ability to read FetchXML filters and attribute lists precisely — candidates may overlook the statecode filter or assume all attributes are returned when only specific ones are listed.
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
✓
Active accounts created in the last 30 days, returning name, accountid, and createdon.
The FetchXML query includes a filter on statecode equal to 0 (Active) and a condition on createdon within the last 30 days, and it specifies only the name, accountid, and createdon attributes. Therefore, it returns active accounts created in the last 30 days with only those three attributes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
All inactive accounts created in the last 30 days, including all attributes.
Why it's wrong here
The query's attribute element names specific columns rather than all attributes, so returning every field is wrong. It would be correct if the query omitted the attribute list entirely, letting FetchXML return all columns for the filtered inactive recent accounts.
- ✗
All accounts created in the last 30 days, only name, accountid, and createdon.
Why it's wrong here
The query's attribute list and created-on filter would return only those columns and recent records, but the statecode condition also restricts results, so unfiltered-by-state wording is wrong. It would be correct if the query omitted the statecode filter and returned only the named attributes.
- ✓
Active accounts created in the last 30 days, returning name, accountid, and createdon.
Why this is correct
FetchXML filters records using attribute conditions, so the statecode condition restricts results to active accounts while the createdon condition applies a rolling 30-day window. The attribute element limits returned columns to name, accountid and createdon, satisfying the stem's requirement to identify exactly which account data the query retrieves.
- ✗
All accounts regardless of state, returning all attributes.
Why it's wrong here
The query includes an attribute element listing specific columns and a statecode condition, so it cannot return all attributes regardless of state. Returning every column for all records would be correct only if the query omitted both the attribute list and the statecode filter.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-900 question from scratch — 701 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.