The exhibit shows an XML request to create a sales order via the Dynamics 365 Finance data service. The request fails with an error 'Customer account not found'. What is the most likely cause?
Leads to 'not found' error.
Why this answer
The error 'Customer account not found' indicates that the value provided in the <CustomerAccount> element of the XML request does not match any existing customer record in Dynamics 365 Finance. The data service validates the customer account against the CustTable before creating the sales order, so an incorrect or missing CustomerAccount value directly triggers this error.
Exam trap
The trap here is that candidates may confuse a data validation error (like missing customer) with a structural or connectivity error (like malformed XML or wrong URL), but the specific error message directly points to a data mismatch in the request payload.
How to eliminate wrong answers
Option A is wrong because a quantity exceeding inventory would cause an inventory reservation or availability error, not a 'Customer account not found' error. Option B is wrong because an incorrect action URL would result in an HTTP 404 or endpoint resolution error, not a data validation error from the service. Option C is wrong because malformed XML would produce an XML parsing error (e.g., 'Invalid XML' or 'Unexpected token'), not a business logic error about a missing customer account.