How should I use these Troubleshooting practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just Troubleshooting questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Troubleshooting domain.

MB-230 · topic practice

Troubleshooting practice questions

Practise Microsoft Dynamics 365 Customer Service Functional Consultant Troubleshooting practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Editorial oversight:Johnson Ajibi· MSc IT Security, IEEE Senior Member

5 questionsDomain: Troubleshooting

Practice 10 questions Browse domain →

What the exam tests

What to know about Troubleshooting

Troubleshooting questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Troubleshooting exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Troubleshooting questions

5 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full Troubleshooting explanation →

Contoso Ltd. uses Dynamics 365 Customer Service. Support agents frequently encounter recurring customer issues where the resolution steps are identical. Management wants agents to quickly capture these successful resolutions and apply them to future cases without retyping notes. Which feature should you configure to meet this requirement?

Trap 1: Case creation and update rules

Case creation and update rules automatically convert incoming emails or social activities into cases or update existing records based on specific criteria. They do not manage or store reusable resolution steps for support agents to apply during active case troubleshooting.

Trap 2: Parent-child case settings

Parent-child case settings link related cases for hierarchical tracking and rollup, not reusable resolution text. Agents need quick answers or templates that insert prewritten resolution steps into a case. Parent-child relationships suit multi-tier or dependent case structures.

Trap 3: Unified routing diagnostic tools

Unified routing diagnostic tools help administrators troubleshoot work item distribution and evaluate why specific work items matched particular queues or assignment rules. They are strictly administrative utilities and play no role in capturing case resolutions.

Study all Troubleshooting common traps →

A
Case creation and update rules
Why it fails: Case creation and update rules automatically convert incoming emails or social activities into cases or update existing records based on specific criteria. They do not manage or store reusable resolution steps for support agents to apply during active case troubleshooting.
B
Parent-child case settings
Why it fails: Parent-child case settings link related cases for hierarchical tracking and rollup, not reusable resolution text. Agents need quick answers or templates that insert prewritten resolution steps into a case. Parent-child relationships suit multi-tier or dependent case structures.
C
Knowledge management and article templates
Knowledge article templates provide pre-structured resolution content that agents can apply to a case and reuse, avoiding retyping. This satisfies the requirement to capture recurring resolutions quickly and apply them to future cases within Dynamics 365 Customer Service.
D
Unified routing diagnostic tools
Why it fails: Unified routing diagnostic tools help administrators troubleshoot work item distribution and evaluate why specific work items matched particular queues or assignment rules. They are strictly administrative utilities and play no role in capturing case resolutions.

Full breakdown with real-world context →

Question 2hardmultiple choice

Review the full routing breakdown →

Refer to the exhibit. You are troubleshooting a routing issue in Unified Routing. Conversations from French-speaking customers are not reaching the French_Support_Queue. Given the JSON configuration, what is the most likely cause for this failure?

Exhibit

{"routing_rule": {"condition": "customer_language == 'fr'", "action": "route_to_queue", "target": "French_Support_Queue"}, "capacity_profile": "High_Priority_Chat"}

Trap 1: The capacity profile is not attached to the workstream.

Capacity profiles manage how much work an agent can handle, not whether a work item enters a queue. If the capacity profile were missing, the agent might not receive work, but the item would still reach the queue successfully. The routing failure occurs before the assignment phase.

Trap 2: The queue has no active agents assigned to it.

An empty queue does not stop a record from being routed into it. If the routing logic correctly identifies the target, the record will land in the queue regardless of agent availability. The issue described is a failure to route the item to the queue, not a capacity issue.

Trap 3: The routing rule has a syntax error in the JSON structure.

The provided JSON represents logical intent rather than platform configuration schema. Errors in routing are rarely due to syntax in this format; they are almost exclusively due to logic mismatches, such as unpopulated variables or misconfigured rule sets within the Customer Service admin center interface itself.

Study all Troubleshooting common traps →

A
The capacity profile is not attached to the workstream.
Why it fails: Capacity profiles manage how much work an agent can handle, not whether a work item enters a queue. If the capacity profile were missing, the agent might not receive work, but the item would still reach the queue successfully. The routing failure occurs before the assignment phase.
B
A classification rule is missing to populate the context variable.
The routing rule depends on the 'customer_language' variable being populated. If no classification rule exists to analyze the incoming message and set this variable, the routing engine cannot evaluate the condition. Consequently, the routing logic fails to trigger, and the message remains unrouted or goes to a default.
C
The queue has no active agents assigned to it.
Why it fails: An empty queue does not stop a record from being routed into it. If the routing logic correctly identifies the target, the record will land in the queue regardless of agent availability. The issue described is a failure to route the item to the queue, not a capacity issue.
D
The routing rule has a syntax error in the JSON structure.
Why it fails: The provided JSON represents logical intent rather than platform configuration schema. Errors in routing are rarely due to syntax in this format; they are almost exclusively due to logic mismatches, such as unpopulated variables or misconfigured rule sets within the Customer Service admin center interface itself.

Full breakdown with real-world context →

Question 3mediummultiple choice

Review the full routing breakdown →

You are configuring unified routing for a customer service center. You have created a workstream for the 'Email' channel and added a routing rule that assigns work items to the 'Tier 1 Support' queue. However, you notice that incoming emails are not being routed to the queue. What is the most likely cause?

Trap 1: The queue's assignment method is set to 'Round Robin'.

The assignment method determines how work items are distributed to agents within the queue, not whether items reach the queue. Even if the assignment method is misconfigured, emails would still be routed to the queue and then remain unassigned. The failure to route to the queue indicates an issue earlier in the routing pipeline, such as the workstream not being activated or the rule not being triggered.

Trap 2: The email channel is not configured to use unified routing.

While the channel must be enabled for unified routing, the scenario states that a workstream for the Email channel has been created, implying that the channel is already configured. If the channel were not using unified routing, the workstream would not be applicable, but the more direct cause given the setup is the workstream's activation status. The channel configuration is a prerequisite that is already assumed to be in place.

Trap 3: The routing rule condition is set to 'Equals' instead of 'Contains'.

The condition operator affects which work items match the rule, but if the rule is intended to route all emails to the queue regardless of content, the operator choice would not prevent routing. The scenario does not specify that the rule is conditional on email content; it simply states a rule assigns items to the queue. Therefore, the operator is unlikely to be the cause of no routing at all.

Study all Troubleshooting common traps →

A
The queue's assignment method is set to 'Round Robin'.
Why it fails: The assignment method determines how work items are distributed to agents within the queue, not whether items reach the queue. Even if the assignment method is misconfigured, emails would still be routed to the queue and then remain unassigned. The failure to route to the queue indicates an issue earlier in the routing pipeline, such as the workstream not being activated or the rule not being triggered.
B
The email channel is not configured to use unified routing.
Why it fails: While the channel must be enabled for unified routing, the scenario states that a workstream for the Email channel has been created, implying that the channel is already configured. If the channel were not using unified routing, the workstream would not be applicable, but the more direct cause given the setup is the workstream's activation status. The channel configuration is a prerequisite that is already assumed to be in place.
C
The workstream is not activated.
In unified routing, a workstream must be activated to process incoming work items. If the workstream is in a draft or inactive state, routing rules within it are not evaluated, and items will not be routed to any queue. Activating the workstream ensures that the classification and routing logic executes, directing emails to the specified queue based on the configured rules.
D
The routing rule condition is set to 'Equals' instead of 'Contains'.
Why it fails: The condition operator affects which work items match the rule, but if the rule is intended to route all emails to the queue regardless of content, the operator choice would not prevent routing. The scenario does not specify that the rule is conditional on email content; it simply states a rule assigns items to the queue. Therefore, the operator is unlikely to be the cause of no routing at all.

Full breakdown with real-world context →

Question 4mediummultiple choice

Read the full Troubleshooting explanation →

Your customer service team requires that when a parent case is updated to a status of 'Resolved', all active child cases must automatically be resolved as well. Which configuration should you implement?

Trap 1: Service level agreement KPIs

SLA KPIs track elapsed time against entitlements and raise warnings or failures when targets are breached; they never write status values to related records. Cascading resolution demands a workflow or Power Automate flow. SLA items are correct when the requirement is measuring and enforcing response or resolution times.

Trap 2: Queue item routing configurations

Queue routing assigns incoming work items to queues and users based on rules; it governs ownership, not lifecycle state. Resolving child cases when a parent resolves requires a workflow or Power Automate flow acting on the parent's status change. Routing is correct when distributing cases by type, territory or capacity.

Trap 3: Automatic record creation rules

Automatic record creation rules generate new records from incoming activities such as emails or social posts; they cannot cascade status changes across existing parent-child case hierarchies. A Power Automate flow or classic workflow triggered on parent case resolution is required to update child cases.

Study all Troubleshooting common traps →

A
Service level agreement KPIs
Why it fails: SLA KPIs track elapsed time against entitlements and raise warnings or failures when targets are breached; they never write status values to related records. Cascading resolution demands a workflow or Power Automate flow. SLA items are correct when the requirement is measuring and enforcing response or resolution times.
B
Parent-child case closure settings
Parent-child case closure settings define the behaviour applied when a parent case reaches a terminal status, automatically resolving its active child cases. Configuring this satisfies the requirement directly, without custom workflows or plugins, because the platform applies the closure cascade natively.
C
Queue item routing configurations
Why it fails: Queue routing assigns incoming work items to queues and users based on rules; it governs ownership, not lifecycle state. Resolving child cases when a parent resolves requires a workflow or Power Automate flow acting on the parent's status change. Routing is correct when distributing cases by type, territory or capacity.
D
Automatic record creation rules
Why it fails: Automatic record creation rules generate new records from incoming activities such as emails or social posts; they cannot cascade status changes across existing parent-child case hierarchies. A Power Automate flow or classic workflow triggered on parent case resolution is required to update child cases.

Full breakdown with real-world context →

Question 5mediummultiple choice

Read the full Troubleshooting explanation →

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?

Trap 1: Duplicate Detection Rules

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.

Trap 2: Field Level Security

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.

Trap 3: Case Merge settings

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.

Study all Troubleshooting common traps →

A
Entity Auditing
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.
B
Duplicate Detection Rules
Why it fails: 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.
C
Field Level Security
Why it fails: 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.
D
Case Merge settings
Why it fails: 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.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Troubleshooting sessions

Start a Troubleshooting only practice session

Every question in these sessions is drawn from the Troubleshooting domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Troubleshooting questions →Mixed MB-230 session

Frequently asked questions

What does the MB-230 exam test about Troubleshooting?: Troubleshooting questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Troubleshooting questions in a focused session?: Yes — the session launcher on this page draws every question from the Troubleshooting domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other MB-230 topics?: Use the topic links above to move to related areas, or go back to the MB-230 question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the MB-230 exam covers. They are not copied from any real exam or dump site.

Troubleshooting only

10 questions 20 questions 30 questions 50 questions

Mixed MB-230 session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All MB-230 questions Troubleshooting domain overview MB-230 exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Troubleshooting practice questions

What to know about Troubleshooting

Common Troubleshooting exam traps

Troubleshooting questions

Refer to the exhibit. You are troubleshooting a routing issue in Unified Routing. Conversations from French-speaking customers are not reaching the French_Support_Queue. Given the JSON configuration, what is the most likely cause for this failure?

Exhibit

Your customer service team requires that when a parent case is updated to a status of 'Resolved', all active child cases must automatically be resolved as well. Which configuration should you implement?

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?

Track your progress over time

Start a Troubleshooting only practice session

Related MB-230 topic practice pages

Configure Representative Experience and Routing practice questions

Extend Customer Service practice questions

Manage Cases in Customer Service practice questions

MB-230 fundamentals practice questions

MB-230 scenario practice questions

MB-230 troubleshooting practice questions

Frequently asked questions

Track your progress

Study resources

Exam traps to avoid