How many Refer to the Exhibit Practice Questions questions are on this page?

This page has 13 Refer to the Exhibit Practice Questions scenario questions for the MB-230 exam, each with detailed explanations and wrong-answer analysis.

How should I approach MB-230 scenario questions?

Read the full scenario before looking at the answer options. Identify the constraint or requirement in the scenario, then eliminate options that are generally true but wrong for this specific case. Scenario questions reward careful reading over pattern matching.

← Back to Microsoft Dynamics 365 Customer Service Functional Consultant questions

Scenario-based practice

Refer to the Exhibit Practice Questions

Practise Microsoft Dynamics 365 Customer Service Functional Consultant practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

Start full practice test Read exam guide

scenario questions

MB-230

exam code

Microsoft

vendor

Scenario guide

How to approach refer to the exhibit practice questions

Practise exhibit-style questions that ask you to read a topology, table, command output or diagram before choosing the best answer.

Quick answer

Exhibit-style questions test whether you can read a topology, command output, diagram or table before choosing the best answer.

How to extract the relevant detail from an exhibit.

How topology, command output or routing information affects the answer.

How to avoid answering from memory before reading the evidence.

How to map the exhibit back to the exam objective.

Practice scenarios

Question 1mediummultiple choice

Review the full routing breakdown →

Refer to the exhibit. An administrator has configured the routing logic shown in the JSON snippet. A new case is created where the priority is set to 'High' (value 1) and the customer is a 'Contact'. Which of the following statements correctly describes what will happen to this case?

Exhibit

{
  "routing_rule": {
    "name": "High Priority Route",
    "conditions": [
      { "field": "prioritycode", "operator": "equals", "value": 1 },
      { "field": "customerid_type", "operator": "equals", "value": "account" }
    ],
    "output": {
      "queue": "Priority Tier 1"
    }
  }
}

A
The case will be routed to the 'Priority Tier 1' queue because the priority is High.
Why it fails: This statement is incorrect because it ignores the second condition in the rule logic. For the rule to execute, both the priority must be 1 and the customer type must be an account. Since the customer is a contact, the logic evaluates to false, and the output is skipped.
B
The case will remain unassigned and will not be moved to any queue.
Why it fails: While this specific rule fails, cases in Dynamics 365 are typically processed by a sequence of rules. If no rules match, the case usually remains in the default system queue or is handled by a catch-all rule, rather than simply existing in a state of no assignment at all.
C
The rule will fail to evaluate because 'customerid_type' is not a valid field for routing.
Why it fails: In Dynamics 365, 'customerid_type' is a valid attribute used to distinguish between account and contact records in polymorphic lookups. The system can evaluate this field in routing rules to ensure that cases are handled differently based on the type of customer entity associated with the record.
D
The case will not be routed by this specific rule because the customer type condition is not met.
This is correct because the rule requires the customer to be an 'account'. Since the case is associated with a 'contact', the criteria for this specific routing rule are not satisfied, and the system will continue to evaluate other rules in the routing rule set for a match.

Full breakdown with real-world context →

Question 2mediummultiple choice

Full question →

Refer to the exhibit. A consultant is reviewing a session template configuration for cases. What will be the result when an agent opens a case record using this template?

Exhibit

{
  "msdyn_name": "Default Case Session",
  "msdyn_anchortab": "incident_customer_summary",
  "msdyn_sessiontype": "entity"
}

A
The session will open with the customer's account form as the main tab.
Why it fails: The anchor tab is specifically set to 'incident_customer_summary', which is typically a specialized tab for case data. Unless that tab was specifically configured to show the account form, the session would instead default to the case-related information defined in that particular application tab's configuration.
B
A new session will start, and the 'incident_customer_summary' tab will be the anchor.
The 'msdyn_anchortab' attribute identifies the application tab that serves as the fixed point of the session. When this template is used, the system will automatically load the customer summary tab and prevent the agent from closing it, ensuring the most important information remains visible.
C
The agent will be prompted to choose which tab to anchor before the session loads.
Why it fails: Session templates are designed to automate the workspace setup and do not require agent input for structural elements like anchor tabs. The settings defined in the template are applied immediately upon session creation to provide a seamless and standardized experience for every record opened by the agent.
D
The session will fail to load because the session type is set to 'entity'.
Why it fails: 'Entity' is a valid and standard session type in Dynamics 365. It is used when a session is centered around a specific record, such as a Case or an Account. This configuration is perfectly normal and is the foundation for most session-based navigation in the Customer Service workspace.

Full breakdown with real-world context →

Question 3hardmultiple choice

Review the full routing breakdown →

Refer to the exhibit. A consultant is reviewing the routing configuration for a technical support workstream. Based on the provided logic, what will happen if an incoming case requires the 'Azure' skill but all agents with that skill are currently at full capacity?

Exhibit

{
  "logic": "Round Robin",
  "matching": "Exact Match",
  "attribute": "msdyn_skill",
  "behavior": "If no skill match is found, route to default queue"
}

A
The case is immediately routed to the default queue for general handling.
Why it fails: Routing to the default queue usually occurs when intake rules fail or if no assignment rules are met. Since the skill was identified but agents are simply at capacity, the system keeps the item in the current queue awaiting a qualified resource rather than failing over to default.
B
The skill requirement is dropped and the case is assigned to any available agent.
Why it fails: Dropping skill requirements only occurs if the matching logic is set to 'Closest Match' or if there is a timeout rule configured to relax constraints. With 'Exact Match' enforced, the system will not bypass the skill requirement simply because qualified agents are currently busy with other tasks.
C
The case stays in the queue until an agent with the 'Azure' skill becomes available.
Under the Exact Match and Round Robin configuration, the system requires the specific skill to be present. If qualified agents are at capacity, the work item persists in the queue backlog until an agent's capacity frees up to accept the specific skill-tagged work item as defined.
D
The case is assigned to the agent with the lowest capacity usage regardless of skills.
Why it fails: Assigning to the agent with the lowest capacity usage is characteristic of 'Most Idle' routing without skill constraints. Since this configuration specifically mandates an 'Exact Match' for the skill attribute, the system cannot ignore the skill requirement in favor of general agent availability or idle time.

Full breakdown with real-world context →

Question 4hardmultiple 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"}

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 5hardmultiple choice

Review the full routing breakdown →

Refer to the exhibit. You are implementing a custom plugin to handle case routing. Which method should you use to register this logic within the Dynamics 365 environment?

Exhibit

{
  "rule": "Case Priority",
  "logic": "if (case.priority == 'Critical') { return 'Escalation_Queue'; }",
  "error_handling": "log_to_application_insights"
}

A
Use the Power Apps portal to upload the code file.
Why it fails: The Power Apps portal does not support the upload or execution of compiled C# plugin assemblies. Plugins must be built and registered via the Plugin Registration Tool to interact correctly with the Dataverse event execution pipeline, which is a core requirement for server-side logic.
B
Register the assembly using the Plugin Registration Tool.
The Plugin Registration Tool is the standard, supported utility for deploying custom C# code to Dataverse. It allows you to specify the event, entity, and execution stage, ensuring the routing logic triggers reliably and follows the platform's execution model for high-performance server-side operations.
C
Add the code directly to a JavaScript web resource.
Why it fails: JavaScript is a client-side technology and cannot execute server-side logic like custom plugin assemblies. Using JavaScript for server-side routing is impossible because the client-side code is only executed after the data has reached the browser, which is far too late to influence the routing process.
D
Configure an Azure Function in the Power Platform Admin Center.
Why it fails: Azure Functions are external web services. While they can be integrated via webhooks, they are not registered as plugins within the internal Dataverse pipeline. Relying on external functions for core routing logic adds unnecessary complexity and potential points of failure compared to native plugin registration.

Full breakdown with real-world context →

Question 6hardmultiple choice

Full question →

Refer to the exhibit. An agent reports receiving this error when trying to publish a knowledge article. What should you do to resolve this?

Exhibit

{
  "status": "403",
  "error": "InsufficientPrivileges",
  "message": "User does not have Write access to entity: knowledgearticle"
}

A
Grant the System Administrator role
Why it fails: Granting the System Administrator role violates security best practices by providing excessive, unnecessary permissions. Users should only be given the specific privileges required to perform their job duties. Administrative roles should be restricted to a small number of IT staff to ensure the integrity and security of the environment.
B
Update the security role permissions
The error code 'InsufficientPrivileges' directly points to a security role deficiency. By navigating to the Security Roles section and granting the agent the necessary 'Write' and 'Publish' permissions for the Knowledge Article entity, the agent will gain the required access level to perform the action successfully.
C
Rebuild the knowledge management search index
Why it fails: Rebuilding the search index is a troubleshooting step for search result issues, not access or permission errors. The provided error specifically mentions a lack of 'Write' access, which is a structural security issue that indexing does not address. This action would waste time and not resolve the actual problem.
D
Reset the agent's user profile
Why it fails: Resetting a user profile is unrelated to entity-level permission errors. Permissions are controlled by security roles assigned to the user, not by the user profile state. This action would not modify the security role configuration and therefore would not resolve the 'InsufficientPrivileges' error encountered by the user.

Full breakdown with real-world context →

Question 7mediummultiple choice

Review the full routing breakdown →

Refer to the exhibit. The routing configuration is set to 'Closest Match'. If an incoming work item requires a skill level of 5, but the only available agent has a skill level of 4, how will the routing engine respond?

Exhibit

{
  "ruleType": "Skill_Matching",
  "matchType": "Closest_Match",
  "minProficiency": 3,
  "relaxationTimer": "60 seconds"
}

A
The engine will wait for the relaxation timer of 60 seconds before assigning.
Why it fails: The relaxation timer is typically used to lower the requirements further if no match is found at all. However, with 'Closest Match' already enabled, the engine can immediately assign the item to the best available agent who meets the minimum proficiency, rather than waiting for a timer.
B
The engine will reject the assignment because the level 4 is not level 5.
Why it fails: Rejecting the assignment would be the behavior for 'Exact Match'. Since 'Closest Match' is configured, the engine is explicitly told to look for the nearest possible skill level, allowing it to bypass the exact requirement in favor of getting the work assigned to a capable resource.
C
The engine will assign the work item to the agent with level 4 proficiency.
Because 'Closest Match' is active and the agent's proficiency of 4 is above the 'minProficiency' threshold of 3, the engine identifies this agent as the best available match. It will proceed with the assignment even though the agent does not meet the ideal level 5 requirement.
D
The engine will route the item to the default queue immediately.
Why it fails: Routing to the default queue is a fallback for when no suitable agents or rules are found. In this case, a suitable agent (level 4) was found that meets the 'Closest Match' criteria, so the system will successfully assign the item rather than triggering a fallback.

Full breakdown with real-world context →

Question 8mediummultiple choice

Review the full routing breakdown →

Refer to the exhibit. You are reviewing the JSON configuration for a routing rule. Based on the provided exhibit, what will happen when a case with 'High' priority arrives?

Exhibit

{
  "rule_id": "r-9921",
  "condition": "priority == 'High'",
  "action": "assign_to_queue",
  "target": "Emergency_Support_Queue",
  "priority_weight": 10
}

A
The case is automatically escalated to a manager.
Why it fails: The configuration specifies a target queue, not an escalation path to a manager. While queues can be assigned to teams, the rule itself does not define an escalation logic, meaning the case remains in the queue waiting for an available agent to pick it up.
B
The case is assigned to the Emergency_Support_Queue.
The JSON explicitly defines the action as 'assign_to_queue' with the target set to 'Emergency_Support_Queue'. This confirms that the logic correctly maps the high-priority case to the specified queue, which is the intended behavior for prioritizing sensitive or time-critical support requests within the system.
C
The system sends an email to the customer.
Why it fails: There is no configuration block in the JSON that references email notification or outbound communication. The rule is strictly focused on assignment logic within the routing engine, and extending it to send emails would require a separate Power Automate flow or plugin registration.
D
The rule fails because the priority weight is too low.
Why it fails: The priority weight is an integer property used by the routing engine for sorting, not for validation. A value of 10 is perfectly valid and will simply inform the routing engine of the relative importance of this rule compared to other rules in the system.

Full breakdown with real-world context →

Question 9mediummultiple choice

Review the full routing breakdown →

Refer to the exhibit. A case with a priority of 'Normal' (value 2) enters the system. Based on the intake and routing rule configuration shown, what is the expected outcome for this case?

Exhibit

{
  "ruleName": "Priority_Intake",
  "conditions": [
    {
      "entity": "incident",
      "attribute": "prioritycode",
      "operator": "equals",
      "value": "1"
    }
  ],
  "action": {
    "type": "routeToQueue",
    "targetQueue": "High_Priority_Queue"
  }
}

A
The case will be routed to the High_Priority_Queue by default.
Why it fails: The rule explicitly requires the 'prioritycode' to be '1' for the routing action to trigger. Since the incoming case has a value of '2', it fails the condition, and the system will not move it to the High_Priority_Queue based on this specific rule's configuration.
B
The case will be routed to the default queue defined for the workstream.
When an incoming record fails all defined routing rule conditions within a workstream, the Unified Routing engine directs the item to the default queue. This ensures that every work item is captured and assigned to a location where it can eventually be handled by an agent.
C
The case will remain unassigned and will not appear in any queue.
Why it fails: Dynamics 365 Unified Routing is designed to prevent work items from being lost. If a case enters a workstream, it must be routed somewhere; therefore, it will fall back to a default queue rather than simply disappearing or remaining in an unassigned state without a queue.
D
The case will trigger an error and a notification will be sent to the admin.
Why it fails: Failing to match a routing rule is a standard operational scenario and does not constitute a system error. The routing engine handles this through fallback mechanisms like default queues, so no error is generated and no administrative intervention is required for this typical routing behavior.

Full breakdown with real-world context →

Question 10mediummultiple choice

Review the full routing breakdown →

Refer to the exhibit. You are configuring a routing rule. Based on the provided JSON policy, what will occur when a case with 'customer_segment' set to 'premium' is created?

Exhibit

{
  "rule_type": "routing",
  "priority": 1,
  "criteria": {
    "field": "customer_segment",
    "operator": "equals",
    "value": "premium"
  },
  "action": "assign_to_queue",
  "target_queue": "premium_support_team"
}

A
The case is assigned to the default queue.
Why it fails: The JSON structure explicitly defines a target queue named 'premium_support_team'. The routing engine will honor this specific destination rather than defaulting to the standard system queue, assuming the rule is active and processed during the case routing evaluation phase of the record creation.
B
The case is assigned to the premium_support_team queue.
The JSON policy clearly maps cases meeting the premium criteria to the 'premium_support_team' queue. Since the priority is set to 1, this rule will take precedence, ensuring the routing engine directs the record to the specified target queue immediately upon evaluation of the business logic.
C
The routing engine throws an error.
Why it fails: The provided JSON syntax is well-formed and standard for defining routing rule criteria. As long as the environment contains a queue named 'premium_support_team', the engine will process this without error, successfully moving the case record to the intended queue based on the defined rule criteria.
D
The rule is skipped because criteria are missing.
Why it fails: The criteria object contains a field, operator, and value, which provides all necessary data for the evaluation engine. The system has everything required to identify the customer segment and perform the action, so the rule will be processed successfully rather than being ignored by the engine.

Full breakdown with real-world context →

Question 11mediummultiple choice

Review the full routing breakdown →

Refer to the exhibit. These context variables are defined in a Chat Workstream. You want to use the 'CustomerTier' variable in an intake rule to route 'Gold' tier customers to a specific queue. Where does the value for 'CustomerTier' typically originate before it reaches the routing engine?

Exhibit

{
  "context_variables": [
    { "name": "CustomerTier", "type": "string" },
    { "name": "ProductCode", "type": "string" }
  ]
}

A
It is automatically pulled from the 'Tier' field on the Contact record by the system.
Why it fails: The system does not automatically sync Contact fields to context variables without a specific mapping or bot logic. Context variables are designed to hold data passed from the 'context' of the start of the interaction, such as information entered in a pre-chat survey or website metadata.
B
It is entered manually by the agent when they first accept the chat notification.
Why it fails: The routing engine needs the value *before* the chat is assigned to an agent so it can decide which queue the chat belongs in. If the agent had to enter it manually, the chat would have already been routed, which defeats the purpose of using the variable for routing logic.
C
It is passed from the Pre-chat survey or the portal's Chat Javascript snippet.
This is the correct origin. Pre-chat surveys allow customers to provide info (like their tier) before the session begins. Alternatively, developers can use the 'setContextVariable' method in the portal's Javascript to pass authenticated user data directly into the Omnichannel routing engine for immediate rule evaluation.
D
It is calculated by a Macro that runs when the customer clicks the 'Chat' button.
Why it fails: Macros run in the context of the agent's workspace and cannot execute on the customer's browser or before a session has been assigned to an agent. Therefore, they cannot be used to populate context variables that the routing engine needs to perform the initial assignment of the chat.

Full breakdown with real-world context →

Question 12hardmultiple choice

Full question →

Refer to the exhibit. A case has reached a 'Non-compliant' state. Based on the provided JSON data, which action should the system administrator take to ensure the team is proactively alerted before the failure time?

Exhibit

{
  "case_status": "In Progress",
  "sla_status": "Non-compliant",
  "failure_time": "2023-10-27T14:00:00Z",
  "warning_time": "2023-10-27T13:30:00Z"
}

A
Create a workflow to update the failure time
Why it fails: Updating the failure time is a bad practice as it artificially inflates performance metrics and masks underlying process issues. SLAs should reflect actual business requirements rather than being modified to avoid non-compliance. Administrators should instead focus on improving response times or adjusting staffing levels to meet the original deadlines.
B
Configure SLA failure actions
Why it fails: Failure actions only execute once the deadline has already passed and the record is already non-compliant. These are useful for reporting or escalation but do not provide the proactive alert needed to prevent the failure from occurring in the first place, thus failing to meet the stated business requirement.
C
Configure SLA warning actions
SLA warning actions execute at the warning time threshold defined in the SLA KPI item. By setting up email notifications or tasks at this point, agents are alerted while the case is still compliant. This proactive notification is the correct mechanism for ensuring that teams address cases before failure occurs.
D
Enable auto-resolve for non-compliant cases
Why it fails: Automatically resolving cases that are non-compliant is an incorrect business process. It closes unresolved issues without providing a solution, which will frustrate customers and significantly damage the organization's reputation. Proper management requires human intervention to resolve the underlying issue, not a programmatic closure of the ticket record itself.

Full breakdown with real-world context →

Question 13mediummultiple choice

Full question →

Refer to the exhibit. You are reviewing the configuration of an automated case resolution follow-up. What is the impact of this configuration?

Exhibit

{
  "rule": "Auto_Resolve_Case",
  "on_event": "Case_Resolved",
  "delay": "24h",
  "action": "Send_Survey"
}

A
The survey is sent immediately upon resolution.
Why it fails: The configuration explicitly includes a 'delay' parameter set to '24h'. This prevents the survey from being sent immediately, ensuring that the customer has sufficient time to interact with the resolution before being asked for their feedback, which leads to higher-quality responses.
B
The survey is sent 24 hours after the case is resolved.
The JSON clearly defines a 24-hour delay ('24h') triggered by the 'Case_Resolved' event. This confirms that the survey is queued for delivery one full day after the case status changes to resolved, which is the intended business process for collecting delayed customer feedback.
C
The case is automatically reopened if no survey is sent.
Why it fails: There is no logic in the exhibit that links survey sending to case reopening. The rule is strictly focused on sending feedback surveys, and any reopening logic would need to be defined as a separate business rule or workflow, which is not present here.
D
The survey is sent to the manager instead of the customer.
Why it fails: The configuration does not specify a recipient for the survey. In a standard setup, this would default to the primary contact associated with the case. There is no mention of a manager in the JSON, making it an incorrect assumption about the survey's routing logic.

Full breakdown with real-world context →

These MB-230 practice questions are part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style MB-230 questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.

Refer to the Exhibit Practice Questions

How to approach refer to the exhibit practice questions

Quick answer

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

Practice scenarios

Refer to the exhibit. An administrator has configured the routing logic shown in the JSON snippet. A new case is created where the priority is set to 'High' (value 1) and the customer is a 'Contact'. Which of the following statements correctly describes what will happen to this case?

Exhibit

Refer to the exhibit. A consultant is reviewing a session template configuration for cases. What will be the result when an agent opens a case record using this template?

Exhibit

Refer to the exhibit. A consultant is reviewing the routing configuration for a technical support workstream. Based on the provided logic, what will happen if an incoming case requires the 'Azure' skill but all agents with that skill are currently at full capacity?

Exhibit

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

Refer to the exhibit. You are implementing a custom plugin to handle case routing. Which method should you use to register this logic within the Dynamics 365 environment?

Exhibit

Refer to the exhibit. An agent reports receiving this error when trying to publish a knowledge article. What should you do to resolve this?

Exhibit

Refer to the exhibit. The routing configuration is set to 'Closest Match'. If an incoming work item requires a skill level of 5, but the only available agent has a skill level of 4, how will the routing engine respond?

Exhibit

Refer to the exhibit. You are reviewing the JSON configuration for a routing rule. Based on the provided exhibit, what will happen when a case with 'High' priority arrives?

Exhibit

Refer to the exhibit. A case with a priority of 'Normal' (value 2) enters the system. Based on the intake and routing rule configuration shown, what is the expected outcome for this case?

Exhibit

Refer to the exhibit. You are configuring a routing rule. Based on the provided JSON policy, what will occur when a case with 'customer_segment' set to 'premium' is created?

Exhibit

Refer to the exhibit. These context variables are defined in a Chat Workstream. You want to use the 'CustomerTier' variable in an intake rule to route 'Gold' tier customers to a specific queue. Where does the value for 'CustomerTier' typically originate before it reaches the routing engine?

Exhibit

Refer to the exhibit. A case has reached a 'Non-compliant' state. Based on the provided JSON data, which action should the system administrator take to ensure the team is proactively alerted before the failure time?

Exhibit

Refer to the exhibit. You are reviewing the configuration of an automated case resolution follow-up. What is the impact of this configuration?

Exhibit