The answer is that the API does not support creating opportunity products inline with the opportunity; they must be created after the opportunity exists. This is because the Dynamics 365 Sales API, built on OData, enforces a strict parent-child creation order where the parent record (the opportunity) must first have a valid ID before any child records (line items) can be posted to the `opportunityproducts` entity. On the MB-910 exam, this tests your understanding of entity relationship constraints and API payload structure—a common trap is assuming you can nest line items in a single POST, similar to how you might in a UI form. Remember the memory tip: "Parent first, child second—line items can't be born before the opportunity exists."
MB-910 Describe Dynamics 365 Sales Practice Question
This MB-910 practice question tests your understanding of describe dynamics 365 sales. 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.
A sales team is using the Dynamics 365 Sales API to create an opportunity. The JSON exhibit shows the payload they are sending. The request fails because the product line items are not being added. 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.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The API does not support creating opportunity products inline with the opportunity; they must be created after the opportunity exists
Option A is correct because the Dynamics 365 Sales API does not allow creating opportunity products (opportunity line items) inline within the same POST request that creates the opportunity. The opportunity must first exist with a valid ID, and then the line items must be added via separate POST requests to the `opportunityproducts` entity. This is a fundamental design constraint of the OData-based API for Dynamics 365, which enforces a parent-child creation order.
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 API does not support creating opportunity products inline with the opportunity; they must be created after the opportunity exists
Why this is correct
Opportunity products are child records and require the opportunity ID to be created separately.
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 pricelevelid is specified at both opportunity and line item levels
Why it's wrong here
This is allowed and not the cause of failure.
✗
The totalamount field is inconsistent with the line items total
Why it's wrong here
While the total might be off, the API does not enforce this at creation, and it would not cause line items to fail to be added.
✗
The product numbers 'PR-001' and 'PR-002' do not exist in the system
Why it's wrong here
If the products did not exist, the error would be about invalid product IDs, not about line items not being added.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume modern REST APIs always support inline creation of child records, but Microsoft deliberately restricts this for certain entities in Dynamics 365 to enforce business logic and validation order.
Detailed technical explanation
How to think about this question
Under the hood, the Dynamics 365 Sales API uses the OData v4 protocol with strict entity relationship constraints. The `opportunity` entity and `opportunityproduct` entity are linked via a navigation property, but the API does not support deep insert (creating related entities in a single batch) for this specific relationship. This is unlike some other entities (e.g., `contact` with `task`) where deep insert is allowed. In real-world scenarios, developers must first create the opportunity, capture the returned `opportunityid`, and then loop through line items to POST each one to the `opportunityproducts` endpoint, often using a batch request for efficiency.
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.
Describe Dynamics 365 Sales — This question tests Describe Dynamics 365 Sales — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The API does not support creating opportunity products inline with the opportunity; they must be created after the opportunity exists — Option A is correct because the Dynamics 365 Sales API does not allow creating opportunity products (opportunity line items) inline within the same POST request that creates the opportunity. The opportunity must first exist with a valid ID, and then the line items must be added via separate POST requests to the `opportunityproducts` entity. This is a fundamental design constraint of the OData-based API for Dynamics 365, which enforces a parent-child creation order.
What should I do if I get this MB-910 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 →
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-910 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-910 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.