MB-230 Manage Cases in Customer Service Practice Question
An agent needs to track the history of changes made to a case, including who changed the status and when. Which feature should be enabled to support this requirement?
⚠ Common exam trap
Candidates often confuse 'Auditing' with 'Timeline' or 'Activity Feeds.' While the timeline shows activity, only Auditing captures the granular history of field-level changes and user-specific status updates.
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
✓
Entity Auditing
Auditing is the standard feature for tracking history in Dynamics 365. When enabled, it captures every field change, providing a detailed trail that is crucial for compliance, auditing, and troubleshooting. By implementing auditing, managers can hold users accountable, ensure data integrity, and easily reconstruct the timeline of events for complex cases, which is essential for maintaining high service quality and addressing customer disputes regarding case handling history.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Entity Auditing
Why this is correct
Entity Auditing is specifically designed to track data changes across the system. By enabling it for the Case entity, administrators ensure that all field updates, including status changes, are logged with the user, timestamp, and old/new values, providing a complete history of the case's lifecycle for review.
- ✗
Duplicate Detection Rules
Why it's wrong here
Duplicate detection rules are used to identify redundant data entries, not to track field change history. They help prevent the creation of duplicate records but do not store information about when or how a specific field value was modified on an existing record over time.
- ✗
Field Level Security
Why it's wrong here
Field Level Security restricts access to specific data fields for certain users, preventing them from seeing or modifying sensitive information. While it manages security, it does not provide a historical log of changes made to those fields. It governs access rather than recording the history of user interaction.
- ✗
Case Merge settings
Why it's wrong here
Case Merge settings are used to consolidate duplicate cases. They do not maintain a comprehensive log of field-level modifications for individual cases. Relying on merge settings would not provide the detailed audit trail required to see who modified a status and at what specific point in time.
About these practice questions
Courseiva writes every MB-230 question from scratch — 189 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.