Question 397 of 966

Quick Answer

The answer is that the revenue condition uses 'gt' instead of 'ge', so accounts with exactly $1,000,000 are excluded. This is because the FetchXML query operator 'gt' stands for "greater than," meaning it only returns records where the revenue is strictly above the specified value, while 'ge' means "greater than or equal to," which includes the boundary value. On the Microsoft Dynamics 365 Fundamentals ERP MB-920 exam, this distinction tests your understanding of how FetchXML query operators filter data in Dynamics 365 Sales, often appearing in scenario-based questions where a user reports missing results due to a boundary condition. A common trap is assuming "over $1,000,000" includes the exact amount, but in FetchXML, 'gt' excludes it. To remember, think of the letter 'e' in 'ge' as standing for "equal," ensuring the edge case is included.

MB-920 Practice Question: Describe shared features and Copilot capabilities

This MB-920 practice question tests your understanding of describe shared features and copilot capabilities. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.

Exhibit

Refer to the exhibit.

```xml
<retrieveMultiple>
  <entity name="account">
    <filter type="and">
      <condition attribute="address1_city" operator="eq" value="Seattle"/>
      <condition attribute="revenue" operator="gt" value="1000000"/>
    </filter>
    <order attribute="name" descending="false"/>
  </entity>
</retrieveMultiple>
```

A Dynamics 365 Sales user runs a FetchXML query similar to the exhibit to retrieve accounts. The query returns fewer results than expected. The user expects to see accounts from Seattle with revenue over $1,000,000, but some accounts meeting these criteria are missing. What is the most likely cause?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

Question 1hardmultiple choice
Full question →

Exhibit

Refer to the exhibit.

```xml
<retrieveMultiple>
  <entity name="account">
    <filter type="and">
      <condition attribute="address1_city" operator="eq" value="Seattle"/>
      <condition attribute="revenue" operator="gt" value="1000000"/>
    </filter>
    <order attribute="name" descending="false"/>
  </entity>
</retrieveMultiple>
```

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 revenue condition uses 'gt' instead of 'ge', so accounts with exactly $1,000,000 are excluded

Option A is correct because the FetchXML query uses 'gt' (greater than) for the revenue condition, which excludes accounts with revenue exactly $1,000,000. The user expects accounts with revenue over $1,000,000, but 'gt' is strictly greater than, so accounts with revenue equal to $1,000,000 are omitted. Changing the operator to 'ge' (greater than or equal to) would include those accounts, resolving the discrepancy.

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.

  • The revenue condition uses 'gt' instead of 'ge', so accounts with exactly $1,000,000 are excluded

    Why this is correct

    Correct: 'gt' means greater than, so exactly $1,000,000 is not included.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The filter type should be 'or' to include all Seattle accounts regardless of revenue

    Why it's wrong here

    Using 'or' would include accounts that meet either condition, but the user expects both conditions.

  • The order attribute is incorrect, causing some records to be hidden

    Why it's wrong here

    Order only affects sorting, not filtering.

  • The entity name is misspelled as 'account' instead of 'accounts'

    Why it's wrong here

    'account' is the correct entity name in Dynamics 365.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may assume 'over $1,000,000' naturally excludes the exact value, but the FetchXML operator 'gt' strictly excludes it, while 'ge' would include it—testing attention to operator semantics versus natural language interpretation.

Detailed technical explanation

How to think about this question

FetchXML uses XML-based query operators where 'gt' maps to the SQL '>' operator, and 'ge' maps to '>='. In Dynamics 365, the revenue field (typically a money type) stores values with decimal precision, so an account with exactly $1,000,000.00 is excluded by 'gt' but included by 'ge'. This is a common off-by-one error in query logic, especially when users think 'over' includes the boundary value.

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 practice questions

Related MB-920 practice-question pages

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

Practice this exam

Start a free MB-920 practice session

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

FAQ

Questions learners often ask

What does this MB-920 question test?

Describe shared features and Copilot capabilities — This question tests Describe shared features and Copilot capabilities — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The revenue condition uses 'gt' instead of 'ge', so accounts with exactly $1,000,000 are excluded — Option A is correct because the FetchXML query uses 'gt' (greater than) for the revenue condition, which excludes accounts with revenue exactly $1,000,000. The user expects accounts with revenue over $1,000,000, but 'gt' is strictly greater than, so accounts with revenue equal to $1,000,000 are omitted. Changing the operator to 'ge' (greater than or equal to) would include those accounts, resolving the discrepancy.

What should I do if I get this MB-920 question wrong?

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

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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

Last reviewed: Jun 11, 2026

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…

Sign in to join the discussion.

This MB-920 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 MB-920 exam.