Q:

You are customizing the Microsoft Dynamics 365 finance and operations apps. The customization involves adding new business logic that will be triggered upon certain events in the application.

You need to ensure that the new business logic can be easily maintained and does not interfere with future updates to the core application.

What should you do? Each correct answer presents part of the solution. Choose three.

 

Wrong: Create a new table in the database to handle the business logic separately.

Wrong:Modify the base class directly to include the new business logic.

Wrong:Copy the existing method into a new class and add the custom business logic.

Creating a new class extension (E) allows for adding custom business logic without modifying the original base class, which aligns with best practices for maintainability and upgradeability. Using the Chain of Command (D) is a recommended approach to extend the functionality of existing methods without altering the original code. Implementing event handlers (C) is a non-intrusive way to add custom logic that responds to specific application events. Modifying the base class directly (B) is not recommended as it can lead to issues during updates. Copying an existing method into a new class (F) is not a best practice as it can create redundant code and maintenance challenges. Creating a new table in the database (A) is not related to adding business logic within the application code and could lead to unnecessary complexity.

Elements, models, and packages - Training | Microsoft Learn

Development tools in Visual Studio - Finance & Operations | Dynamics 365 | Microsoft Learn