Exam MB-300 topic 4 question 2 discussion

See link: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/errors-and-alerts: Alert notifications As an admin, you can create one or more alert settings to handle cases of planned or unplanned maintenance. For example, you can set up the dual-write system to notify you by email if a specific error threshold is reached because of, for example, network errors. The dual-write system can also take action on your behalf. For example, it can pause or stop dual-write.

Use catch-up errors: This is the correct option. Catch-up errors functionality allows you to reprocess errors and recover from a synchronization interruption. It helps to catch up on missed changes and ensures that the data is synchronized correctly. https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/dual-write-troubleshooting-live-sync

“Re-run execution” is a feature in Dynamics 365 dual-write that retries the entire execution, along with the records that failed or errored out in the last sync1. However, this feature is typically used when you encounter issues while copying pre-existing data between finance and operations apps and Dataverse1. In the scenario you described, the issue was due to an unplanned maintenance window, not a sync issue. Therefore, enabling alert conditions would be more effective in preventing data loss and errors during such interruptions1.

To prevent errors and data loss from recurring during an unplanned maintenance window for Dynamics 365 Finance, you should Enable an alert condition (Option A)1. Alert notifications can be created to handle cases of planned or unplanned maintenance1. This will ensure that you are notified of any issues in real-time, allowing you to take immediate action and prevent data loss1. “Re-run execution” is a feature in Dynamics 365 dual-write that retries the entire execution, along with the records that failed or errored out in the last sync1. However, this feature is typically used when you encounter issues while copying pre-existing data between finance and operations apps and Dataverse1. In the scenario you described, the issue was due to an unplanned maintenance window, not a sync issue. Therefore, enabling alert conditions would be more effective in preventing data loss and errors during such interruptions1.

Answer should be A. The question is about preventing loss of requests in future. Alert notifications can handle cases of planned or unplanned maintenance. Based on alert settings dual-write system can take action on your behalf. For example, it can pause or stop dual-write. If one of the apps becomes unavailable and, based on thresholds defined for alert, dual-write goes into a paused state, all new requests are queued (that is, they aren't lost). After both apps are running smoothly, you can resume from the paused state. The updates will then be read back from the queue and written to the recovered app.

whats the correct answer here?

As an admin, you can create one or more alert settings to handle cases of planned or unplanned maintenance. For example, you can set up the dual-write system to notify you by email if a specific error threshold is reached because of, for example, network errors. The dual-write system can also take action on your behalf. For example, it can pause or stop dual-write. https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/errors-and-alerts

B. Use catch-up errors. Explanation: "Catch-up errors" is a feature in Dual-Write that helps to handle errors and ensure data consistency during synchronization. When an interruption occurs, catch-up errors can be used to identify and reprocess the failed data synchronization. This helps in recovering from the interruption and bringing the systems back into sync without data loss.

The “re-run execution” option is not limited to the initial synchronization process only. It can be used for any failed synchronization requests or operations, regardless of whether they are part of the initial sync or subsequent sync attempts. When errors occur during synchronization, selecting the “re-run execution” option allows you to retry those specific failed requests or operations. This option is designed to address individual errors and ensure that the affected data is successfully synchronized. Therefore, if you encounter synchronization errors during the unplanned maintenance window, selecting the “re-run execution” option can help you retry and synchronize the missed data, reducing the chances of data loss and ensuring data consistency between Dynamics 365 Sales and Dynamics 365 Finance.

Also think A is correct Alert notifications As an admin, you can create one or more alert settings to handle cases of planned or unplanned maintenance. For example, you can set up the dual-write system to notify you by email if a specific error threshold is reached because of, for example, network errors. The dual-write system can also take action on your behalf. https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/errors-and-alerts

Should be A.

Re-run is for initial sync. Should be A.

D is correct

Should be A.