MB-230 Manage Cases in Customer Service Practice Question
You need to automate the creation of cases from incoming emails. What is the most efficient way to achieve this in Dynamics 365 Customer Service?
⚠ Common exam trap
Candidates often choose Power Automate flows for this. While possible, 'Automatic Record Creation' is the native, dedicated Dynamics 365 feature designed specifically for email-to-case conversion with built-in mapping and conditions.
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
✓
Automatic record creation rules
Automatic Record Creation (ARC) rules are the native, highly configurable way to convert emails into cases. By using ARC, you can define specific conditions under which a case should be created, map email fields directly to case attributes, and automatically link the case to the correct customer record. This streamlined approach minimizes manual data entry, ensures no customer requests are missed, and significantly speeds up the initial case intake process for the support team.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Manual data entry by agents
Why it's wrong here
Relying on manual entry is highly inefficient, error-prone, and leads to inconsistent data quality. It increases the time-to-first-response and risks losing communication if agents forget to process emails. Automation is required to handle high volumes of incoming support requests in a professional and timely manner.
- ✓
Automatic record creation rules
Why this is correct
Automatic record creation rules are specifically designed to convert incoming activities like emails into cases. They allow for mapping fields, applying filters, and triggering workflows. This is the out-of-the-box, recommended method for ensuring that all incoming customer emails are converted into trackable work items within the system.
- ✗
Custom plugin development
Why it's wrong here
Custom development is overkill for a standard requirement like email-to-case conversion. It introduces unnecessary technical debt, requires ongoing maintenance, and is harder to update than standard configuration. Unless there is a highly complex, non-standard business requirement, native features should always be prioritized over custom code in the environment.
- ✗
Case Merge settings
Why it's wrong here
Case Merge settings handle duplicate records and have no functionality related to creating new cases from incoming emails. They are designed for post-creation cleanup, not for initial record instantiation. Using them for this purpose is logically incorrect and will not result in the creation of new case records.
About these practice questions
This MB-230 question is part of Courseiva's 189-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 →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This MB-230 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-230 exam.