Sign in
Home/Microsoft/Microsoft Dynamics 365 Customer Service Functional Consultant (MB-230)/Free questions

Microsoft Dynamics 365 Customer Service Functional Consultant (MB-230) — Free Practice Questions

10 free sample questions from a bank of 386, with the correct answers and explanations. No signup required — start practising right now.

1Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You are configuring a business process flow for a case entity. All cases must be flagged for review. You need to complete configuration of the business process flow. Solution: Set the input parameter type as Option set for the action. Does the solution meet the goal?
  • Yes
  • No
Answer: B

The short version

B — No, Option Set input does not satisfy the review flag requirement. Every case must be flagged for review in the business process flow, which needs a review field plus branch logic, not only an input data type choice.

Key concepts in this question

  • Business process flow for Case: Guided stages and steps that enforce consistent handling and move cases toward resolution in Dynamics 365 Customer Service.
  • Flag for review pattern: Usually a Yes-No field plus a branch or workflow that routes flagged records, so no case advances without review.
  • Action input types: Inputs for called actions can be Text, Yes-No, File, Email, Number, Date or Option Set, and each type only defines data shape.
  • Option Set limits: Choosing a value from a list creates no flag, no validation and no routing by itself, so the stated goal stays unmet.

Why B is correct

The proposal only sets an input type to Option Set, which describes shape rather than enforcement. None of the documented input kinds flags all cases for review without an added field and branch condition. Without that flag field plus consuming logic, the flow cannot guarantee review, so No is the settled evaluation of the solution.

Why the others are wrong

  • A. Yes fails because an Option Set type creates no review marker, no required stage, and no check blocking progress until review is recorded.

MB-230 exam tip

Memorize input types, then ask what consumes the input, since MB-230 often tests whether a type alone can enforce a rule without a field or branch.

2Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You are configuring a business process flow for a case entity. All cases must be flagged for review. You need to complete configuration of the business process flow. Solution: For a new action named Ready for review, disable the As a business process flow action step option. Does the solution meet the goal?
  • Yes
  • No
Answer: B

The short version

B — No, disabling run-as-BPF blocks the review flag action. The action must be enabled as a business process flow step to fire from the flow.

Key concepts in this question

  • Business process flow actions: on-demand actions invoked from a stage to perform side effects such as flagging.
  • Run-as-BPF toggle: checkbox that permits the action to execute in BPF context rather than only standalone.
  • All-cases-must-flag goal: requires every case record to trigger the review marker through the flow.
  • Disabled consequence: clearing the option removes the action from BPF invocation, so the flow cannot call it.
  • Yes versus No series: proposal must fully satisfy the stated configuration need to earn Yes.

Why B is correct

A new Ready for review action intended for BPF use must have its as-a-business-process-flow-step option enabled. Disabling it, as the solution proposes, prevents the flow from launching the action at runtime. Vendor prose states the checkbox should be checked for BPF triggering. The flow then skips flagging, the goal fails, and No is the settled verdict with full consensus.

Why the others are wrong

  • A. Yes is wrong because a disabled BPF action cannot execute to flag cases for review.

MB-230 exam tip

BPF action must stay enabled as BPF step, disabling equals No for flagging scenarios.

3You manage Dynamics 365 for Customer Service. You need to configure automatic case creation for emails received by customers who have a support contract. What should you do?
  • Configure service level agreements to be on hold until a call can be made to the customer.
  • Create an automatic record creation and update rule. Set the source type to email. Configure the rule to send automatic email responses to customers when records are created.
  • Create an automatic record creation and update rule. Set the source type to service activity. Configure the rule to send automatic email responses to customers when records are created.
  • Create an automatic record creation and update rule. Set the source type to email. If a valid entitlement exists, configure the rule to create a case.
Answer: D

The short version

D — Email source rule with entitlement check auto-creates entitled cases. Source type plus valid entitlement gating routes only contracted mail to cases.

Key concepts in this question

  • Automatic record creation rule: watches an activity source and creates records without manual triage.
  • Source type email: listens to inbound email, unlike service activity which tracks service scheduling.
  • Entitlement validation: confirms the sender holds active support coverage before case creation.
  • Auto-response option: acknowledges receipt to customers when records are created, aiding experience.
  • SLA hold contrast: pauses timers for action, but does not itself create cases from mail.

Why D is correct

The need is automatic case creation for emails from customers with a support contract. Setting source to email captures the channel, and adding if-valid-entitlement-exists ensures only entitled senders generate cases. Vendor correction marks D as the fix, with unanimous consensus. Email-source without entitlement over-creates, while service-activity source watches the wrong object entirely.

Why the others are wrong

  • A. SLA on-hold pauses timers but creates no cases from incoming email.
  • B. Email rule without entitlement check creates cases for unentitled senders too.
  • C. Service activity source monitors appointments, not inbound customer email.

MB-230 exam tip

Entitled email to case equals auto-rule plus email source plus if-valid-entitlement condition.

4A customer service organization plans to implement knowledge management for a custom entity named Root Cause Analysis. Users must be able to search, link, and rate knowledge articles. Users must be provided with suggested knowledge articles. You need to configure Dynamics 365 for Customer Service. Which three actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
  • Navigate to the Knowledge Base Management Settings wizard. Then, navigate to Record types and select Root Cause Analysis.
  • Add a lookup to the article entity.
  • In Solution Explorer, expand the Root Cause Analysis entity and select Forms. Edit the main form and configure a knowledge base search control.
  • In Solution Explorer, expand the Root Cause Analysis entity and select Forms. Edit the main form and configure a subgrid for knowledge articles.
  • In Solution Explorer, select the Root Cause Analysis entity and then select Knowledge management.
Answer: A, C, E

The short version

ACE — Enable record type plus form search control plus entity knowledge flag. That trio unlocks search plus link plus rate plus suggestions for Root Cause Analysis.

Key concepts in this question

  • Knowledge Base Management Settings: admin wizard where record types are opted into knowledge features.
  • Record type selection: adds the custom Root Cause Analysis entity to the knowledge-enabled set.
  • Knowledge search control: form component placed on the main form for lookup, linking, and suggested articles.
  • Entity knowledge management toggle: Solution Explorer switch that activates article association for the entity.
  • Lookup and subgrid traps: article entity lookups or plain subgrids do not provide full search and suggestion behavior.

Why ACE is correct

Custom entities are excluded from knowledge until explicitly enabled in three places. Selecting Root Cause Analysis in record types authorizes it, adding the search control surfaces search plus link plus rate plus suggestions on the form, and enabling knowledge management on the entity wires the backend. Vendor prose cites ACE with docs linkage. Missing any step leaves suggestions or linking unavailable, so only the trio meets the stated functional set.

Why the others are wrong

  • B. Article lookup alone stores a reference without search or suggestion UX.
  • D. Subgrid for articles lists links but does not provide knowledge search or ratings.

MB-230 exam tip

Custom entity knowledge equals record type plus form search control plus entity toggle, remember ACE.

5A company implements Dynamics 365 for Customer Service. You are assigned a case. You accidently close the case before completing your work. You need to ensure that you can continue to work on the case. What should you do?
  • Reassign the case
  • Reactivate the case
  • Clone the case
  • Change the status reason to In Progress
Answer: B

The short version

B — Reactivate the accidentally closed case to resume work. Reactivation returns it to active state with history preserved.

Key concepts in this question

  • Closed case state: resolved or canceled records become read-only and block edits and activities.
  • Reactivate action: reverses closure, restoring active status so ownership and timeline continue.
  • Reassign contrast: changes owner but requires an active record, so it cannot reopen a closed one.
  • Clone contrast: creates a new separate case, splitting history instead of continuing the original.
  • Status reason edit: adjusts a label on an active record, but does not itself change inactive state.

Why B is correct

Closing ends the lifecycle and locks the case, so continued work needs a state reversal rather than ownership or duplication moves. Reactivate is the documented path that flips closed back to active while retaining activities and entitlements. Vendor consensus is unanimous that no one should miss this. Reassign, clone, or status tweaks leave the original closed and fail the resume goal.

Why the others are wrong

  • A. Reassign changes ownership on active cases but does not reopen a closed record.
  • C. Clone duplicates data into a new case, fragmenting audit trail instead of resuming.
  • D. Changing status reason to In Progress edits labels without reversing closed state.

MB-230 exam tip

Closed by mistake equals Reactivate first, then continue work on the same case number.

6Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You are configuring a business process flow for a case entity. All cases must be flagged for review. You need to complete configuration of the business process flow. Solution: Create an action that generates a task record that is assigned to the case reviewer and appends the text Ready for review to the case topic. Does the solution meet the goal?
  • Yes
  • No
Answer: A

The short version

A — Yes, task-generating action with Ready for review meets the flag goal. Assigned task plus topic stamp ensures every case gets review attention.

Key concepts in this question

  • All-cases review mandate: every case must carry a visible marker that a reviewer can queue on.
  • BPF action capability: can create records such as tasks during stage progression.
  • Task assignment: directs work to the case reviewer with due context from the parent case.
  • Topic append: adds Ready for review text to the case topic for list and view filtering.
  • Prior No contrast: merely disabling run-as-BPF fails, while productive action content succeeds.

Why A is correct

Creating an action that generates an assigned task and appends Ready for review to the topic produces both a work item and a searchable flag on each case. That satisfies flagged-for-review in process and in data, unlike an empty or disabled step. Vendor references to adding actions in BPF confirm the pattern as correct. Consensus is unanimous for Yes because the outcome fully covers the requirement.

Why the others are wrong

  • B. No is wrong because the task plus topic update delivers the required review signal on all cases.

MB-230 exam tip

Flag all cases equals BPF action that creates assigned task plus appends Ready for review to topic.

7A company uses Dynamics 365 for Customer Service. A case in the queue is routed to you. You will be going on a vacation. You need to assign the case to someone else. What should you do?
  • Release the case.
  • Route the case to another queue.
  • Share the case.
  • Escalate the case
Answer: A

The short version

A — Release the routed case back to the queue before vacation. Release clears personal ownership so peers can pick it up.

Key concepts in this question

  • Queue ownership: routed cases sit with a user until released, picked, or assigned onward.
  • Release action: returns the case to the shared queue without choosing a successor.
  • Route to queue contrast: moves to a different queue, unnecessary when the current queue is already correct.
  • Share contrast: grants access but retains ownership, so responsibility stays with the vacationing user.
  • Escalate contrast: raises skill or priority for complex needs, not for simple absence coverage.

Why A is correct

Going on vacation requires relinquishing ownership so the case becomes available for pickup. Release is the documented mechanism that puts a personally held queued case back to available. Vendor notes confirm releasing lets someone else pick it in absence. Routing elsewhere misdirects, sharing keeps ownership, and escalation overstates the need, so only release fits least-effort coverage.

Why the others are wrong

  • B. Routing to another queue is for misrouted work, not for absence on correctly queued cases.
  • C. Sharing adds collaborators but leaves the vacationer as owner responsible for progress.
  • D. Escalation seeks senior handling, not peer pickup during planned leave.

MB-230 exam tip

Vacation with queued case equals Release to queue, not share or escalate.

8A company uses Dynamics 365 Customer Service. You are configuring the advanced similarity rules. You create a similarity rule on cases and put an exact match for the Modified On field in the Match Fields tab. You test the rule and discover that exact matches do not appear. You need to determine why the rule is not working. What are two possible reasons why the rule is not working? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
  • A Power Automate flow was not created.
  • The similarity rule is deactivated.
  • The security role is not set to run the similarity rule.
  • The similarity rule was not published.
  • The Modified On field is not set to searchable in the customization of the case entity in the solution.
Answer: B, E

The short version

BE — Inactive rule plus non-searchable Modified On explains no exact matches. Activation and field searchability both gate similarity results.

Key concepts in this question

  • Advanced similarity rules: suggest similar cases based on match fields, requiring active and published configuration.
  • Deactivated state: prevents the rule engine from evaluating candidates at all.
  • Modified On type: date-time values have limited exact-match eligibility and must be searchable to participate.
  • Exact match demand: timestamp equality is brittle, so engine suppresses unsearchable field matches.
  • Security and flow traps: privileges and Power Automate flows do not drive core similarity matching.

Why BE is correct

Testing shows no exact matches because the rule never runs and the chosen field cannot be matched. A deactivated rule, per option B, yields zero suggestions regardless of data. Modified On, per option E, must be set searchable in customization, and date-time fields face exact-match restrictions noted in docs. Vendor discussion highlights deactivation and field eligibility as the pair. Together they fully explain the symptom, matching settled BE.

Why the others are wrong

  • A. Missing flow does not block native similarity evaluation for cases.
  • C. Security role scope affects visibility, not whether exact timestamp matches appear.
  • D. Unpublished status matters for some artifacts, but deactivation alone already stops this rule.

MB-230 exam tip

No similar cases equals check rule active first, then match-field searchable and eligible type.

9You are a customer service representative using Dynamics 365 for Customer Service. You need to identify and eliminate duplicate cases. What should you do?
  • Configure Dynamics 365 AI for Customer Service
  • Use business rules
  • Merge cases
  • Use parent-child case relationships
Answer: C

The short version

C — Merge cases to remove duplicates while preserving history. Merging keeps one surviving case, rolls activities onto it, and deactivates the duplicate so queues and SLAs stay accurate.

Key concepts in this question

  • Duplicate cases: Come from multiple channels or retries, splitting history and inflating queues when left separate.
  • Merge in Dynamics 365: Native action that picks a master record, consolidates notes and activities, and keeps a single timeline for agent and customer.
  • Business rules: Enforce logic on one form, such as defaults or validation, but cannot fuse two existing records.
  • Parent-child links: Connect related but distinct cases for hierarchy, which preserves both records instead of removing duplication.

Why C is correct

Merge is the purpose-built deduplication tool because it unifies timelines, preserves entitlement and SLA calculation on the survivor, and stops parallel work on the same issue. Microsoft guidance directs merge rather than manual close for duplicates, since only merge retains history without loss. That direct fit makes Merge cases the settled answer.

Why the others are wrong

  • A. AI for Customer Service is wrong because it suggests knowledge or routing but does not consolidate records.
  • B. Business rules are wrong because they act on field logic within one record and cannot combine two cases.
  • D. Parent-child relationships are wrong because they coordinate distinct cases hierarchically while keeping duplicates alive.

MB-230 exam tip

Link merge to deduplicate and parent-child to coordinate, so duplicate stems mean merge while related-workstream stems mean hierarchy.

10You are a system administrator for Dynamics 365 for Customer Service. All child cases must inherit the product, customer name, case title, and case type from the parent case. Parent cases must not be closed until all child cases are closed. You need to configure cases. What should you do?
  • Validate that customer and case title fields have not been removed as fields that child cases inherit from parent cases. Add product and case-type fields to the list. Set the closure preference setting to Don't allow parent case closure until all child cases are closed.
  • On the case entity, update the Parent case-Child case 1:N relationship field mapping to include the fields. Create a business rule on the case entity to prevent the parent from closing if it has one or more open child cases.
  • Create a business rule.
  • Validate that customer and case title fields have not been removed as fields that child cases inherit from the parent cases. Add product and case-type fields to the list. The closure preference setting does not need to be changed. This is default behavior.
Answer: A

The short version

A — Configure inheritance plus block parent closure until children close. Only option A sets field inheritance for product, customer, title and type together with the closure preference that forces child resolution first.

Key concepts in this question

  • Parent-child case settings: Admin area defining which fields copy downward and how parent closure interacts with open children.
  • Field inheritance: Copies customer, title, product and type to children for consistency and cleaner reporting across the family.
  • Closure preference: Strict option named Do not allow parent closure until all child cases are closed, which directly enforces the required sequencing.
  • Custom alternatives: Manual relationship mapping plus business rules can mimic parts, but the supported method uses built-in parental settings.

Why A is correct

Option A validates inherited fields, adds product and case type, and sets the restrictive closure option in one supported step. Documentation confirms None allows independent closure, so leaving the default would violate the rule. By applying native inheritance plus blocked closure, option A fully satisfies both halves of the requirement.

Why the others are wrong

  • B. Relationship mapping plus custom rule is wrong because it bypasses supported parental settings with fragile customization.
  • C. A business rule alone is wrong because one rule cannot define four-field inheritance and closure preference together.
  • D. Keeping default closure is wrong because the default permits independent closure, breaking the must-wait rule.

MB-230 exam tip

Pair inheritance with consistency and closure preference with sequencing, recalling that None means independent, so must-wait stems need the explicit block setting.

Want the full bank of 386 questions for Microsoft Dynamics 365 Customer Service Functional Consultant (MB-230)? See all practice exams.