AB-100 practice question 17 of 35

An incident review shows Copilot started using an unapproved definition of “eligible refund” in Dynamics 365 Customer Service after a glossary…

Full set: 708 questions
An incident review shows Copilot started using an unapproved definition of “eligible refund” in Dynamics 365 Customer Service after a glossary update. You must stop further term changes within 15 minutes without downtime for read-only assistance, and actions must be centrally enforced across environments. Audit evidence of what changed and who approved it must be preserved, and you can’t redeploy solutions today. Requirements • Prevent any further glossary changes immediately • Keep read-only Copilot assistance available • Preserve audit evidence for the change review Which immediate remediation best meets the requirements?
Answer options
A: Rollback solution to last approved glossary version in prod now
B: Lower model temperature to reduce term drift
C: Freeze glossary changes via managed solution Correct answer
D: Copy glossary to new environment and repoint agents
Correct Answer:
C. Freeze glossary changes via managed solution
Explanation

Freezing glossary changes via a managed solution is the best immediate action. This is a configuration change, not a full deployment, which can be done quickly (within 15 minutes) and without downtime. It directly prevents further modifications, preserving the current state and its audit evidence for review. The read-only Copilot functionality, which reads from the glossary, remains available. This approach meets all the specified constraints, particularly the "no redeployment" and "preserve audit evidence" requirements.

Why Incorrect

A. Rolling back a solution is a redeployment, which is explicitly forbidden by the constraint "can’t redeploy solutions today."
B. Model temperature controls the creativity or randomness of a generative AI's response, not its adherence to a specific glossary definition. This would not solve the problem.
D. Copying the glossary and repointing agents is a complex, time-consuming action that would cause downtime and not remediate the issue in the production environment itself.

References

1. Microsoft Power Platform. (2024). Solution layers. Microsoft Learn. This documentation explains how managed solutions create layers. An administrator could deploy a new

empty managed solution layer on top of the glossary entity or apply security roles to make it read-only

effectively "freezing" it without a full rollback.

2. Microsoft Power Platform. (2023). Microsoft Power Platform Well-Architected - Reliability. Microsoft Learn. This guide discusses incident response

emphasizing the need for rapid mitigation. A configuration change like freezing an entity is a standard mitigation technique that is faster and less risky than a full rollback. See the "Incident Response" section.

3. Microsoft Dataverse. (2024). Security concepts in Microsoft Dataverse. Microsoft Learn. This document details how security roles can be used to control access (Create

Read

Write

Delete) to specific data tables (entities). Modifying a security role to remove write access is a fast

central change that meets the requirements.

Scroll to Top