Select Two (Multi-Select) Questions

Intake rules

Why it fails: Intake rules are used at the very beginning of the process to decide which workstream a record should enter. They are generally too high-level to handle the specific, multi-attribute logic required to differentiate between numerous regional and language-based queues within a single unified workstream for a channel.

Prioritization rules

Why it fails: Prioritization rules determine the order in which items within a queue are assigned to agents, but they do not decide which queue the item belongs to. They focus on urgency and service level agreements rather than the categorical routing based on customer location or spoken language requirements.

Assignment rules

Why it fails: Assignment rules manage how work is handed to specific agents once it is already inside a queue. While they can consider skills, they do not manage the initial routing of the work item into the queue itself, which is the primary requirement described in the business scenario.

Create a routing rule that checks the customer's language preference and routes to a Spanish-speaking agent.

Why it fails: While routing rules can route based on language, the requirement is to route to agents with the Spanish skill, not based on customer language. The scenario specifies agents must have the skill, not that the customer's language triggers routing. This option adds unnecessary complexity and does not guarantee the skill requirement is met.

Set up a capacity profile that limits each agent to one voice call and assign it to the queue.

Why it fails: Capacity profiles control how many concurrent sessions an agent can handle, but they do not enforce skill-based routing or overflow timing. While they can prevent overloading, they do not ensure that only Spanish-skilled agents receive the call or that the call overflows after 60 seconds. This does not meet the core requirements.

Enable sentiment analysis to detect frustration and escalate to a supervisor if the wait exceeds 60 seconds.

Why it fails: Sentiment analysis is used to detect customer emotion and can trigger escalations, but it does not address the need to redirect to a backup queue after a time limit. The requirement is about agent skill and timeout, not sentiment. This option is irrelevant to the scenario and would not ensure the call is routed correctly.

A Power Automate flow that queries Dataverse for similar cases when the title changes.

Why it fails: While a flow could be built to search for similar cases, it is not a required component for the built-in suggestion experience and would duplicate functionality. The native experience uses relevance search and knowledge management rather than a custom flow. Requiring a flow would also contradict the goal of using supported, out-of-the-box behavior.

A routing rule set that assigns cases to the knowledge manager.

Why it fails: Routing rule sets assign cases to queues or agents based on conditions and have no role in surfacing similar cases or articles to an agent. Configuring one would not affect suggestions and would add unnecessary routing logic. The suggestion experience is driven by search and knowledge configuration, not by case routing.

An SLA with a first response KPI applied to the case table.

Why it fails: SLAs and KPIs track response and resolution timing; they do not index content or power similarity suggestions. Applying an SLA would change timer behavior but leave agents without suggested articles. This option is a common distractor because SLAs are prominent in case management, but they are unrelated to the suggestion feature.

SLA KPI.

Why it fails: SLA KPIs are used to track service level agreements, such as response times, but they do not control routing of cases to agents. While SLAs may influence priority, they are not required for automatic routing based on skills and availability. Thus, this component is not needed for the routing requirement.

Queue.

Why it fails: While a queue is mentioned in the scenario, it is the container for the cases, not the component that performs routing. Unified routing and a workstream are needed to route cases from the queue. The queue itself does not determine agent assignment based on skills; it simply holds the cases until routed.

Case merge rule.

Why it fails: Case merge rules are used to combine duplicate cases, not to route them. They are unrelated to the process of assigning cases to agents based on skills. Configuring a merge rule would not help achieve the desired automatic routing, so it is not a required component here.

Add the Power Virtual Agents connector to the flow and configure the 'Send a message' action.

Why it fails: The Power Virtual Agents connector is used in Power Automate to send messages to a bot, but this is not required for the bot to call the flow. In fact, the flow is called from the bot, not the other way around. Adding this connector would create a reverse communication path and is not part of the standard integration for triggering a flow from a bot topic.

Register the flow as a custom connector in the Power Platform admin center.

Why it fails: Custom connectors are used to connect to external APIs, not to call Power Automate flows from Power Virtual Agents. Flows are directly integrated into the bot via the 'Call an action' node, without needing to be wrapped in a custom connector. Registering a flow as a custom connector is unnecessary and would not enable the bot to call the flow.

Create a flow with the 'When a Power Virtual Agents message is received' trigger.

Why it fails: This trigger is not available. Power Virtual Agents flows are triggered from within the bot using the 'Call an action' node. The flow must have a manual trigger or be a cloud flow that is called from the bot. The 'When a Power Virtual Agents message is received' trigger does not exist; instead, you use the 'Power Virtual Agents' connector or call the flow from the bot's authoring canvas.

A capacity profile assigned to the queue

Why it fails: A capacity profile determines how many work items agents can handle concurrently, but it does not affect the routing logic based on priority and location. While capacity profiles are important for workload management, they are not required to route cases to a specific queue based on conditions. The scenario focuses on routing criteria, not capacity.

A skill-based routing rule to match agent skills

Why it fails: Skill-based routing is used to match work items to agents with specific skills, but the requirement is to route to a specialized queue, not to specific agents. While skills could be used later in assignment, the initial routing to a queue does not require skill rules. The conditions specified are priority and location, not skills.

A real-time analytics dashboard to monitor routing

Why it fails: Real-time analytics dashboards are for monitoring and reporting, not for routing configuration. They do not influence how cases are routed. While useful for oversight, they are not a component required to achieve the routing behavior described. The core components are the workstream with rules and the destination queue.

Configure the voice channel to use a specific language model for speech recognition.

Why it fails: Speech recognition language models affect transcription and IVR understanding, not routing. While they may be necessary for voice input, they do not determine which agent receives the call based on language skill. Routing rules and agent skills are the correct components.

Set the queue's assignment method to 'Round Robin' to ensure even distribution among language speakers.

Why it fails: Assignment method determines how work is distributed among qualified agents, but it does not filter by language. Round Robin would distribute calls regardless of language, potentially sending a call to an agent who does not speak the required language. The filtering must happen via routing rules and skills.

Enable 'Presence-based routing' on the workstream to check agent availability for the language.

Why it fails: Presence-based routing ensures work is only routed to agents who are available, but it does not consider language skills. It is a complementary setting, not a requirement for language-based routing. The core components are the skill definition and the routing rule.

Skill-based assignment rules

Why it fails: Skill-based assignment rules are not a separate configuration component; instead, skills are attached to agents and work items, and the routing engine matches them. There is no specific 'skill-based assignment rule' entity to configure. The matching is inherent in the routing logic when skills are present. Creating such rules is not a prerequisite; the system uses the skill attachments directly.

Skill-based queues

Why it fails: Queues are used to group work items, but they do not inherently enable skill-based routing. While you can route work items to a queue based on skills, the queue itself is not a component that must be configured for skill-based routing to function. The key is that agents have skills and work items have required skills; queues are just containers. Thus, skill-based queues are not a prerequisite.

Skill-based routing rules

Why it fails: There is no separate entity called 'skill-based routing rules' in unified routing. Routing rules are used to route work items to queues, not to match skills directly. The skill matching is handled by the assignment logic, which automatically considers skills if they are present. Creating such rules is not a required step and would not directly enable skill-based routing.

Automatically create child cases when a parent case is created.

Why it fails: This setting automatically generates child cases upon parent case creation, which is not required here. The scenario does not mention automatic creation of child cases; it focuses on resolution behavior. Enabling this would create unnecessary child cases and could complicate case management. It does not address the requirements of resolving children with the parent or blocking parent resolution.

Reopen child cases when the parent case is reopened.

Why it fails: This setting reopens child cases if the parent is reopened. While related, it does not fulfill the stated requirements. The supervisor wants to resolve children when the parent is resolved and prevent parent resolution while children are active. Reopening children is a different behavior that may be useful but is not requested in this scenario, so it should not be enabled.

Merge child cases into the parent case upon resolution.

Why it fails: Merging child cases into the parent is not a standard setting in parent-child case configuration. This option is not a valid configuration and would not achieve the desired outcomes. The supervisor needs specific resolution behaviors, not merging, which would combine records and potentially lose data. Therefore, this option is incorrect.

Configure a capacity profile and assign it to the workstream.

Why it fails: Capacity profiles control how many concurrent cases an agent can handle, which supports capacity-based routing. While useful for managing workload, a capacity profile is not required to enable skill-based routing specifically. The scenario asks for skill-based routing, so the essential components are skill definitions and the workstream with routing rules, not the capacity profile.

Enable the 'Unified Routing' setting in the Customer Service admin center.

Why it fails: Unified routing is enabled at the environment level as a prerequisite, but it is not a component you configure specifically for skill-based routing. The question asks for the components needed to route by skills, which are the skills themselves and the workstream with routing rules. Enabling unified routing is a general setup step and does not by itself implement skill-based routing logic.

Create an assignment rule that assigns cases to the default queue.

Why it fails: An assignment rule that sends cases to a default queue does not evaluate skills and would route cases without regard to agent expertise. It may be part of a fallback strategy, but it is not a required component for skill-based routing. The scenario requires routing based on skills and capacity, so a generic assignment rule does not fulfill the skill-matching requirement.

Queue assignment rules based on case priority.

Why it fails: Queue assignment rules based on case priority determine which queue a case goes to, not which agent. The requirement is about matching agent skills to case needs, so priority-based queue rules are not relevant. Skill-based routing focuses on agent capabilities, not case priority.

Capacity profiles for each agent.

Why it fails: Capacity profiles define how many concurrent cases an agent can handle, which is important for workload management but not for skill matching. The scenario specifically requires routing based on skill level, so capacity profiles alone do not fulfill the requirement. They are used in conjunction with skill-based routing but are not the primary component.

Presence status synchronization with Microsoft Teams.

Why it fails: Presence status synchronization ensures that agent availability is reflected in Dynamics 365, which is important for routing but does not address skill-based matching. The requirement is to route based on technical skill level, so presence status is not directly relevant. It is a supporting feature for agent availability.

Add the web resource to the Case form.

Why it fails: Adding the web resource to the Case form would make it available on the form, but the requirement is to include it in the session template as a productivity tool. The session template is the correct place for session-level tools. Thus, this action does not meet the requirement.

Register the web resource in the Unified Interface configuration.

Why it fails: Registering a web resource in the Unified Interface configuration is not a specific action for session templates. Web resources are registered in the solution and then referenced where needed. This step is not required to include a productivity tool in a session template; you simply reference the web resource when configuring the tool.

Add a custom control to the session template.

Why it fails: A custom control is a UI component that can be added to forms, but session templates do not directly support adding custom controls. Session templates are used to define the layout of sessions, including tabs and productivity tools. Custom controls are typically added to forms, not session templates. Therefore, this action is not correct.

Automatic article translation into all languages.

Why it fails: While multi-language support is possible, it is not a requirement for an article to be professional or searchable. Forcing automatic translation without review can lead to poor quality, confusing content that hurts the customer experience rather than helping it, making this an optional feature rather than a requirement.

Enable 'Anonymous Browsing' for all articles.

Why it fails: Anonymous browsing is a security configuration choice, not a requirement for article quality or searchability. Some organizations may choose to keep certain articles internal to agents only, and forcing anonymous access would potentially expose confidential or internal support procedures to the public.

Custom C# code to generate article IDs.

Why it fails: Generating article IDs is handled natively by the platform using built-in auto-numbering features. Writing custom code for this is not only unnecessary but also introduces risk, as it bypasses the standard, stable ID generation logic that the system uses to manage article records and links.

Entitlement templates

Why it fails: Entitlement templates define support terms, such as service limits and allocated hours, for specific customers and products. While crucial for contract tracking and SLA enforcement, they are not structural components required to ingest and route work items.

Duplicate detection rules

Why it fails: Duplicate detection rules identify and prevent the creation of redundant records across customer service databases. They operate independently of the unified routing engine and do not contribute to distributing work items to queues or agents.

Subject trees

Why it fails: Subject trees categorize cases by topics to facilitate reporting and trend analysis across the customer service organization. Although helpful for organization, they are not mandatory components for initializing and executing unified routing logic.

Power Automate Flow

Why it fails: While Power Automate can be triggered from within Dynamics 365, it cannot be added as a direct, native step type inside the Agent Script designer. To run a flow from a script, an agent would typically need to trigger a Macro that then initiates the specific cloud flow.

Knowledge Article

Why it fails: Knowledge articles are displayed in the Productivity Pane but are not valid 'step types' within the Agent Script designer. A script can guide an agent to search for an article, but the article itself is a separate entity and cannot be embedded as a functional script step.

Quick Reply

Why it fails: Quick Replies are pre-defined text snippets used in chat or messaging channels to speed up communication. While they are a productivity tool, they are managed separately and are not configured as steps within an Agent Script. They are accessed directly from the conversation control during an active session.

Presence-based capacity

Why it fails: Presence-based logic determines if an agent is online or away, but it does not define the volume of work they can handle. It acts as a gatekeeper for assignment rather than a measurement of the agent's total capacity or workload limits within the workstream.

Skill-based capacity

Why it fails: Skill-based routing matches agents to work items based on their expertise and proficiency levels. Although it is a critical component of the routing process, it does not define the physical or logical limit of concurrent items an agent can handle at one time.

Role-based capacity

Why it fails: Role-based settings typically manage permissions and access levels rather than workload throughput. While a security role might determine who can receive work, it does not define the technical capacity limits used by the Unified Routing engine to distribute individual work items.