The answer is an incorrect filter field name, specifically that 'AccountingDate' does not match the actual source data field name in the export job. In Dynamics 365 Finance, data export filters rely on exact field name matching between the filter expression and the source data structure; if the source uses a different field like 'TransactionDate' or 'PostingDate', the filter is silently ignored, causing the export to return all records including those from 2024. This scenario tests your understanding of how the Data management export framework processes filters against CSV or other source formats, a common pitfall on the MB-920 exam where candidates assume the filter syntax is correct without verifying field alignment. The trap here is that the filter expression itself looks valid—'AccountingDate ge 2025-01-01' uses proper operators—but the mismatch in field names renders it ineffective. Remember the memory tip: "Filter fields must match source fields, not your expectations."
MB-920 Describe Dynamics 365 Finance Practice Question
This MB-920 practice question tests your understanding of describe dynamics 365 finance. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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. The following JSON snippet is from a data management export job in Dynamics 365 Finance:
{
"EntityName": "GeneralJournalEntry",
"ExportFormat": "CSV",
"Filter": "AccountingDate ge 2025-01-01",
"IncludeFields": ["JournalNumber", "AccountingDate", "AmountInTransactionCurrency"],
"SourceDataFormat": "CSV"
}
A financial analyst runs the above export job but notices that the exported file contains entries from 2024 as well. 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.
Refer to the exhibit. The following JSON snippet is from a data management export job in Dynamics 365 Finance:
{
"EntityName": "GeneralJournalEntry",
"ExportFormat": "CSV",
"Filter": "AccountingDate ge 2025-01-01",
"IncludeFields": ["JournalNumber", "AccountingDate", "AmountInTransactionCurrency"],
"SourceDataFormat": "CSV"
}
A
The filter condition is case-sensitive and should be 'GE'
Why wrong: 'ge' is valid in lowercase.
B
The export format should be XML instead of CSV
Why wrong: Export format does not affect filtering.
C
The filter field name 'AccountingDate' does not match the source data field name
The source data format is CSV, and the field name in the CSV might be different, causing the filter to be ignored.
D
The export job needs to be run with the 'Apply filter' option enabled
Why wrong: The filter is included in the JSON, so it should be applied automatically.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The filter field name 'AccountingDate' does not match the source data field name
The filter uses 'AccountingDate ge 2025-01-01' which should filter from Jan 1, 2025, but the filter might not be applied correctly due to the source data format being CSV, which may cause date format interpretation issues. However, the exhibit shows the filter is set correctly. The most likely cause is that the filter is not applied because the data source format is CSV and the filter may use a different date format. But among options, the filter expression is case-sensitive and 'ge' is correct. Actually, the filter should work. The issue might be that the filter is not being applied because the job was run without filter. But the exhibit shows filter present. Option C is most plausible: the filter uses 'AccountingDate' but the field might be 'TransactionDate' in the source. Option D is also possible. However, the typical mistake is that the filter field name does not match. I'll go with C: The filter field name is incorrect.
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 filter condition is case-sensitive and should be 'GE'
Why it's wrong here
'ge' is valid in lowercase.
✗
The export format should be XML instead of CSV
Why it's wrong here
Export format does not affect filtering.
✓
The filter field name 'AccountingDate' does not match the source data field name
Why this is correct
The source data format is CSV, and the field name in the CSV might be different, causing the filter to be ignored.
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 export job needs to be run with the 'Apply filter' option enabled
Why it's wrong here
The filter is included in the JSON, so it should be applied automatically.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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 MB-920 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Describe Dynamics 365 Finance — This question tests Describe Dynamics 365 Finance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The filter field name 'AccountingDate' does not match the source data field name — The filter uses 'AccountingDate ge 2025-01-01' which should filter from Jan 1, 2025, but the filter might not be applied correctly due to the source data format being CSV, which may cause date format interpretation issues. However, the exhibit shows the filter is set correctly. The most likely cause is that the filter is not applied because the data source format is CSV and the filter may use a different date format. But among options, the filter expression is case-sensitive and 'ge' is correct. Actually, the filter should work. The issue might be that the filter is not being applied because the job was run without filter. But the exhibit shows filter present. Option C is most plausible: the filter uses 'AccountingDate' but the field might be 'TransactionDate' in the source. Option D is also possible. However, the typical mistake is that the filter field name does not match. I'll go with C: The filter field name is incorrect.
What should I do if I get this MB-920 question wrong?
Identify which MB-920 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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 →
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.
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.
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.
Sign in to join the discussion.