nerdexam
Microsoft

MB-500 · Question #286

Drag and Drop Question A company uses Dynamics 365 finance and operation apps. The company must create test cases by using the SysTest framework. The test cases must meet the following requirements…

The correct answer is LegacyRollback; Autorollback. SysTest Framework: TestTransactionMode Options Overview The TestTransactionMode enum in Dynamics 365 F&O's SysTest framework controls how test data is cleaned up after each test runs. Choosing the wrong mode leads to data leaking between tests. --- Requirement 1: All insert…

Develop and test code

Question

Drag and Drop Question A company uses Dynamics 365 finance and operation apps. The company must create test cases by using the SysTest framework. The test cases must meet the following requirements: - All insert statements must be tracked and deleted during cleanup. - Transactions must be rolled back using SQL save points. You need to select the TestTransactionMode options to use. Which options should you select for each requirement? To answer, drag the appropriate options to the correct requirements. Each option may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:

Exhibit

MB-500 question #286 exhibit

Answer Area

Drag items

NoneAutorollbackLegacyRollbackLegacyRollbackWithUpdateTracking

Correct arrangement

  • LegacyRollback
  • Autorollback

Explanation

SysTest Framework: TestTransactionMode Options

Overview

The TestTransactionMode enum in Dynamics 365 F&O's SysTest framework controls how test data is cleaned up after each test runs. Choosing the wrong mode leads to data leaking between tests.

Requirement 1: All insert statements must be tracked and deleted during cleanup

Answer: LegacyRollback

Why: LegacyRollback works by recording every INSERT statement made during the test. On cleanup, it explicitly deletes those records. It does NOT use SQL savepoints - it maintains an internal list of inserted rows and removes them one by one. This is the legacy approach (pre-savepoint era).

Requirement 2: Transactions must be rolled back using SQL save points

Answer: Autorollback

Why: Autorollback uses SQL Server's native SAVE TRANSACTION / ROLLBACK TRANSACTION TO SAVEPOINT mechanism. A savepoint is created before the test body runs, and after the test completes, all changes (inserts, updates, deletes) are rolled back to that savepoint atomically. This is the modern, preferred approach.

Why the Other Options Are Wrong

OptionWhy Not Used Here
NoneNo cleanup at all - data persists after the test
LegacyRollbackWithUpdateTrackingTracks both inserts and updates - more than requirement 1 asks for, and still no savepoints

Common Misconceptions

  • Confusing LegacyRollback with Autorollback: Both isolate test data, but through fundamentally different mechanisms - row deletion vs. SQL savepoint.
  • Choosing LegacyRollbackWithUpdateTracking for requirement 1: It over-delivers (tracks updates too) and still doesn't match the savepoint requirement.
  • Assuming Autorollback only handles inserts: It rolls back all DML (inserts, updates, deletes) via the savepoint, making it more complete than the legacy options.

Topics

#SysTest framework#TestTransactionMode#Autorollback#LegacyRollback

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full MB-500 Practice