AB-100 practice question 2 of 35

A global support team uses Dynamics 365 Customer Service and wants Copilot to summarize cases and propose next-best actions directly in the agent…

Full set: 708 questions
A global support team uses Dynamics 365 Customer Service and wants Copilot to summarize cases and propose next-best actions directly in the agent workspace. Customer PII is regulated, tool actions that change case status must require approvals, and audit logs must be retained for seven years. You must avoid a new chat surface and can’t introduce a new external data store for grounding. Which architecture choices best satisfy the constraints while maximizing reuse of Dynamics 365 and Microsoft governance? (Select THREE.)
Answer options
A: Out-of-box Copilot only
B: Copilot Studio agent in Customer Service Correct answer
C: Custom Azure-hosted bot with separate audit data lake
D: Dataverse knowledge search with security roles Correct answer
E: External vector database for case transcripts
F: Power Automate approvals for high-risk actions Correct answer
Correct Answer:
B. Copilot Studio agent in Customer Service; D. Dataverse knowledge search with security roles; F. Power Automate approvals for high-risk actions
Explanation

This combination provides a secure, compliant, and integrated solution using the Microsoft stack.
(B) Copilot Studio agent in Customer Service allows for extending the native Copilot within the existing agent workspace, avoiding a new chat surface.
(D) Dataverse knowledge search with security roles leverages the built-in, secure data platform for grounding, respecting PII regulations and security boundaries without an external data store.
(F) Power Automate approvals for high-risk actions is the standard, low-code method to integrate approval workflows directly with Copilot Studio actions, ensuring that sensitive operations like changing a case status are properly controlled and auditable.

Why Incorrect

A. Out-of-box Copilot only: This lacks the required customizability for specific actions and approval workflows, failing to meet the high-risk action requirement.
C. Custom Azure-hosted bot with separate audit data lake: This introduces a new chat surface and an external data store, violating explicit constraints of the scenario.
E. External vector database for case transcripts: This violates the constraint of not introducing a new external data store for grounding.

References

1. Microsoft Learn. (2024). Overview of extending Copilot in Dynamics 365 Customer Service. This document states

"You can extend Copilot to use... actions through Power Automate flows... by creating custom topics in Microsoft Copilot Studio." This directly supports using Copilot Studio (B) and Power Automate (F).

2. Microsoft Learn. (2024). Use actions in Microsoft Copilot Studio. It details how to "call a Power Automate flow from a topic" to perform actions

including those requiring approvals.

3. Microsoft Learn. (2024). Security concepts in Microsoft Dataverse. This documentation explains how security roles and field-level security protect sensitive data (like PII) within Dataverse

supporting its use for secure grounding (D).

Scroll to Top