Free Microsoft Dynamics MB-820 Actual Exam Questions - Question 4 Discussion

Question No. 4Drag & Drop

DRAG DROP You need to handle the removal of the Description field and the Clone procedure without breaking other extensions. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select. MB-820 practice exam questions

Options
AActions
BSet the Description field as ObsoleteState Removed: in version 2.0.0.1.
CRemove the Description field in version 2.0.0.0.
DSet the Clone procedure as ObsoleteState Removed; in version 2.0.0.1.
ERemove the Clone procedure in version 2.0.0.0.
FSet the Clone procedure as ObsoleteState Pending and ObsoleteReason = 'Not in use in version 2.0.0.0.
GSet the Description field as ObsoleteState = Pending and ObsoleteReason = "Not in use in version 2.0.0.0.
HRemove the Description field from the Issue table in version 2.0.0.1.
IAdd the [Obsolete('xxx')] attribute to the Clone procedure in version 2.0.0.0.
Drag an item to a target. Click × to remove.
Answer Area
Target 1
Drop item here
Target 2
Drop item here
Target 3
Drop item here
US
IS
Imran S.
2026-02-15

I figured you want to avoid breaking extensions by first dealing with dependencies. So, a solid move is to identify which extensions rely on the Description field and Clone procedure before any removal. Next, update those extensions to work without them, making sure they won’t break once the field and procedure are gone. Only after that can you safely remove the Description field and the Clone procedure themselves. Doing it this way keeps things from suddenly breaking because dependent code has already been adjusted beforehand.

0
IS
Imran S.
2026-01-27

I think the key is to start by updating or notifying dependent extensions so they don’t break when you remove the Description field and Clone procedure. So first, you’d identify and update those dependencies. Then you remove or deprecate the field and procedure in your main extension. Finally, confirm that everything works by testing or publishing the updated extensions. That way, nothing breaks mid-process. If you just remove the Description field or Clone procedure first, dependent extensions might fail. So the sequence should focus on dependencies first, removal second, and validation last.

0
IS
Imran S.
2026-01-19

I’ve seen a question about safely removing fields and procedures without breaking extensions, but the drag-drop part here looks tricky. Gonna review proper deprecation steps before deciding the order.

0