Do ATL Navigation and Creator Classes Meet the Goal?
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. A company is implementing Dynamics 365 finance and operations apps. The company must test the functionality of its native Dynamics 365 finance and operations apps by using the Acceptance test library (ATL). You need to implement ATL classes on test data within a development environment. Solution: Create a set of navigation objects and creator classes to access entities and test data. Does the solution meet the goal?
Community Insight
The question tests whether ATL's core building blocks — navigation objects and creator classes — are the right mechanism for testing native finance and operations functionality on known test data; the trap is assuming ATL requires a different harness such as unit test frameworks or data entities alone.
The Acceptance Test Library (ATL) for Dynamics 365 finance and operations apps is built around navigation objects and creator classes that reach application entities and supply test data. Building such a class set in a development environment does satisfy the stated goal, so the correct verdict is Yes (A).
Choosing B (No), because learners expect ATL to demand something more elaborate than navigation and creator classes, such as a full test project scaffold or a separate data-generation tool, when in fact those two constructs are precisely how ATL accesses entities and sets up test data.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The ATL architecture is explicitly organized around two concepts: navigation objects, which let a test drive or reach the application's forms, entities, and business logic, and creator classes, which produce or configure test data in a deterministic way (the documented fluent style, e.g., data.invent.items.default). Creating a set of both gives a developer in a development environment everything needed to write repeatable acceptance tests against native finance and operations functionality, so the stated solution does meet the goal and the answer is A. Because the tests run on controlled, known test data, the result is stable and reproducible, which is exactly the objective the company stated.Why the Other Options Are Wrong
Option B would only be right if ATL required some additional construct beyond navigation and creator classes — for example, if it mandated a separate test-runner framework or custom data entities before any test could execute. The ATL documentation makes clear that these classes are the library's primary entry points for interacting with the app and arranging data, so nothing is missing from the proposed solution. Rejecting the solution on the grounds that it is 'too simple' misreads ATL, whose whole purpose is to reduce the boilerplate normally needed for UI-driven testing in finance and operations apps.Community Comment Notes
Several learners converged on A, with AbhiN1106 noting that "creator classes (e.g., data.invent.items.default) and navigation objects provide access to test entities and records." globeearth reinforced this by quoting the official concepts page, explaining that navigation objects simulate user actions or access forms and entities while creator classes "generate or set up test data in a controlled manner." TrevStyleZ pointed readers to the Concepts section of the same Microsoft article as support for a Yes answer, and alinders emphasized that these classes enable "structured, repeatable testing using known data."Official Reference
Exam Strategy
When an ATL or testing question describes creating navigation objects, creator classes, or data builders, treat it as a strong signal that the solution is correct — those are ATL's documented building blocks. Read the goal statement literally and check only whether the named constructs actually deliver it, not whether some extra step could also be added.
Frequently Asked Questions
Why are navigation objects and creator classes enough to meet the ATL goal?
ATL is built on exactly these two concepts: navigation objects reach entities and business logic, while creator classes set up test data. Together they let you write repeatable acceptance tests against native finance and operations functionality.
Would choosing No be justified if more ATL infrastructure were needed?
No. The Microsoft ATL documentation describes navigation objects and creator classes as the library's core concepts, so no additional framework is required beyond creating that class set in a development environment.
Related Analysis
Practice All MB-500 Questions
Access 115 questions with complete answers and detailed explanations.
View Full MB-500 Practice Test →