Automatic Record Creation Rules for Email-to-Case
A company has multiple product lines and wants to route cases to different support teams based on the product category. However, the product field is not always populated when a case is created via email. How can they ensure the product is automatically populated?
Quick Answer
Automatic record creation rules for email-to-case are the answer because they operate at the moment a case is created, parsing the incoming email's content and keywords to populate fields like product before the case ever reaches a queue or an agent. This matters because the requirement is not just routing cases correctly but fixing an upstream data gap - the product field is missing entirely at the point of case creation, and only a mechanism built into the email-to-case pipeline itself can fill it in automatically. Compare that to the alternatives implied here: making the subject line mandatory still depends on the customer typing the right words, which is manual and unreliable; queues are a routing mechanism for cases that already have the fields they need, not a tool for setting field values in the first place; and while a Power Automate flow could technically be built to inspect and update incoming cases, it would be reinventing functionality that automatic record creation rules already provide natively. The pattern to remember is that when a scenario describes data missing at creation time and asks for something to run automatically without extra steps from the customer or agent, look for the platform's built-in creation-time rule engine before reaching for a custom workflow or a routing feature that assumes the data is already there.
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
✓
Configure automatic record creation rules for email-to-case
Automatic record creation rules for email-to-case can be configured to populate the product field based on keywords or content in the email, ensuring cases are automatically assigned to the correct support team. Option B is incorrect because requiring the subject line to include the product does not guarantee automatic population and adds manual effort. Option C is incorrect because queues do not have a mechanism to set field values like product; they are for routing, not field population. Option D is incorrect because while Power Automate could be used, the built-in automatic record creation rule is the more straightforward and intended solution for email-to-case scenarios.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Configure automatic record creation rules for email-to-case
Why this is correct
Automatic record creation rules for email-to-case can be configured to populate the product field based on keywords or content in the email, ensuring cases are automatically assigned to the correct support team.
- ✗
Require the subject line to include the product
Why it's wrong here
Requiring the subject line to include the product does not guarantee automatic population and adds manual effort.
- ✗
Configure the queue to assign a default product
Why it's wrong here
Queues do not have a mechanism to set field values like product; they are for routing, not field population.
- ✗
Use Power Automate to update the case after creation
Why it's wrong here
Power Automate updates records *after* they are created, meaning the product field would still be unpopulated when initial case routing rules evaluate, causing routing to fail or be incorrect. The requirement is for the field to be populated *at creation* for immediate routing. Power Automate is suitable for complex post-creation workflows, integrating with external systems, or updating fields based on subsequent events or conditions. For instance, it could update a case field if a related record changes, or if an external service returns data, but not for initial field population critical for immediate routing.
Go deeper
Related to this question
About these practice questions
This MB-910 question is part of Courseiva's 941-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on MB-910
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company uses Dynamics 365 Customer Service to manage support cases. They want to ensure that when a customer sends an email to the support address, a new case is automatically created from the email. Which feature should be configured?
medium- A.Define a Service Level Agreement (SLA) for email responses
- B.Convert incoming emails to activities
- C.Set up a queue for email
- ✓ D.Configure Email-to-Case automation
Why D: Dynamics 365 Customer Service includes an Email-to-Case feature that automatically creates a new case record from an incoming email sent to a configured support mailbox. This feature parses the email content, maps it to case fields, and can optionally use advanced rules for classification and routing, eliminating manual case creation.
Variation 2. A support team is using Dynamics 365 Customer Service to manage cases. They notice that when a customer replies to an email, a new case is created instead of updating the existing one. What is the most likely cause?
hard- A.The customer's entitlement is expired
- ✓ B.The queue's 'Update existing case based on email subject' setting is disabled
- C.The email-to-case conversion rule is misconfigured
- D.The email template is not set to link to the case
Why B: The Email-to-Case queue's advanced settings need to have 'Update existing case based on email subject' enabled to automatically associate replies with existing cases. Option A is wrong because the conversion rule controls how emails become cases, but not the specific update behavior. Option C is wrong because email templates are for outgoing emails. Option D is wrong because the entitlement defines support coverage, not case updates.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.