You create a model-driven app and a Dataverse plug-in. The plug-in monitors a company’s address change in the Accounts table. If the change happens, the plug-in emails the sales manager without affecting the app’s users. 
Please select the two steps you need to take to publish an event using the Dataverse Plug-in Registration Tool.

Answer options:

A.Register New Step on the account Update for Asynchronous execution on PreOperation stage
B.Register New Assembly in Sandbox isolation mode and store it in Database
C.Register New Step on the account Update for Synchronous execution on PostOperation stage
D.Register New Assembly in None isolation mode and store in Database
E.Register New Assembly in None isolation mode and store in GAC
F.Register New Step on the account Update for Asynchronous execution on PostOperation stage
G.Register New Assembly in Sandbox isolation mode and store in GAC
H.
Register New Step on the account Update for Synchronous execution on PreOperation stage

Correct Answers: B and F 
The Dataverse plug-in is a .Net assembly that can modify the platform behavior. You can create your .Net project using a development environment, like Visual Studio or Visual Studio Code. After compiling the project and creating an assembly, you need to register the assembly and map the classes to the Event Framework events as logic business steps. 
There are three stages in plug-in event pipeline execution: PreValidation — an initial stage before the main operation. You can include the logic for canceling the event before the data transaction.
PreOperation — the next stage before the main operation but within the data transaction. You can make changes to the data in operation.
PostOperation — the stage after the main operation and still within the data transaction. You can call other actions using the Organization service before the message returns to the caller.
To register the plug-in for the event, you need to register the plug-ins assembly and then attach the plug-in to the Dataverse event. After you establish a connection to the Dataverse environment in the Dataverse Plug-in Registration Tool, you open the Register New Assembly screen (Number 1). On this screen, you browse for the plug-in assembly (Number 2).You need to be sure that the Sandbox isolation mode (Number 3) and the Database (Number 4) are selected. The rest of the options in Steps 3 and 4 are for the on-premises Dynamics 365 deployments. Then you push the “Register Selected Plugins” button (Number 5). 

After successfully registering the assembly and plug-in, you need to attach the plug-in to the Dataverse event using the Register New Step screen (Number 1). On the screen, you provide a message (event name). In our case, it is an Update event (Number 2) for the account table (Number 3). You need to register the plug-in execution on the PostOperation stage (Number 4) in Asynchronous mode (Number 5) because you do not want the app to wait until the plug-in sends an email and possibly impacts the other users’ operations. And finally, you can push the Register New Step button (Number 6). 

Options A and H are incorrect because you can use the Organization service (plug-in) only on the PostOperation and not on the PreOperation event pipeline stage of execution.
Options C is incorrect because you need to execute the plug-in in Asynchronous, not in Synchronous mode.
Options D, E, and Gare incorrect because these options are for assembly registration for the on-premises Dynamics 365 deployments.
For more information about event registration using the Dataverse Plug-in Registration Tool, please visit the below URLs: 

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/tutorial-write-plug-in
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/register-plug-in
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/plug-ins