MB-230 Practice Question: Configure Representative Experience and Routing

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use a single queue with the 'Highest capacity' assignment method and rely on the capacity profile to prioritize high-priority cases.

  Why it's wrong here

  The 'Highest capacity' assignment method assigns to agents with the most available capacity, but it does not differentiate based on case priority. All cases in the queue would be assigned the same way. The requirement is to have high-priority cases use highest capacity and low-priority use round robin. A single queue with one assignment method cannot satisfy both. Therefore, this configuration fails to meet the requirement.

• ✗

  Configure a single queue with a custom assignment method using a Power Automate flow to check priority and assign accordingly.

  Why it's wrong here

  While custom assignment via Power Automate is possible, it is not the standard or recommended approach for this scenario. Unified routing provides built-in assignment methods like highest capacity and round robin. Using a custom flow adds complexity and may not integrate seamlessly with capacity profiles. The requirement can be met using native queue-level assignment methods, making this option unnecessarily complex and not the intended solution.

• ✗

  Set up a single queue and use a routing rule to assign high-priority cases to specific agents and low-priority cases to others.

  Why it's wrong here

  Routing rules route to queues, not directly to agents. Assigning to specific agents would bypass the capacity-based assignment and round robin logic. Moreover, this approach does not dynamically consider agent capacity. The scenario requires assignment based on capacity for high priority and round robin for low priority, which is best handled by different assignment methods at the queue level, not by routing rules targeting individual agents.

• ✓

  Create two queues, one for high priority and one for low priority, and assign different assignment methods to each queue.

  Why this is correct

  In unified routing, you can define multiple queues within a workstream. Each queue can have its own assignment method. By creating a high-priority queue with 'Highest capacity' assignment and a low-priority queue with 'Round robin', and then using routing rules to direct cases to the appropriate queue based on priority, you achieve the desired behavior. This approach leverages queue-level assignment methods, which is the correct way to implement different assignment strategies per priority.