MB-230 Extend Customer Service Practice Question

Answer analysis

Option-by-option breakdown

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

• ✓

  Add a custom web resource (HTML/JS) to the form and use the formContext to listen for the customer field change event.

  Why this is correct

  This is correct because a custom web resource can be embedded on the Case form and use formContext to subscribe to the OnChange event of the customer field. When the field changes, the script can call an external API and update the control's content dynamically without reloading the entire form. This is the standard extensibility approach for dynamic, in-form custom UI.

• ✗

  Create a Power Automate flow that triggers on case creation and writes order history into a note on the case.

  Why it's wrong here

  This is incorrect because a flow triggered on case creation runs only once and does not respond to subsequent changes of the customer field. It also writes data as a note rather than providing an interactive control. The requirement is for a dynamic control that updates automatically when the customer field changes, which this approach cannot satisfy.

• ✗

  Use a Business Rule to call an external REST API and populate a field with order history.

  Why it's wrong here

  This is incorrect because Business Rules in Dynamics 365 cannot make external REST API calls. They are limited to client-side logic such as setting field values, showing/hiding fields, and validation. They cannot retrieve data from external systems, so this approach is not feasible for displaying external order history.

• ✗

  Configure a Virtual Entity that maps to the external order system and add it as a subgrid on the Case form.

  Why it's wrong here

  This is incorrect because Virtual Entities provide read-only integration and do not automatically refresh when a field on the parent form changes. They also require additional configuration and may not update in real time without a full form reload. The requirement is for a custom control that updates dynamically on field change, which virtual entities do not provide out of the box.