Q:
You are developing a custom module in Microsoft Dynamics 365 finance and operations apps that requires using object-oriented principles to manage financial transactions.

You need to ensure that the module supports different types of transactions while sharing common functionalities and adhering to the principle of inheritance.

You need to design the classes appropriately.

How should you do this?

A Create separate classes for each transaction type without a base class and replicate the common functionalities.
B Create a base class for common transaction functionalities and derive specialized classes for each transaction type.
C Use a standalone utility class that handles all types of transactions with conditional statements.
D Implement all transaction types within a single class to centralize the transaction management.
Share this MCQ