Drag and Drop Question A company plans to implement Dynamics 365 Finance and purchase licenses through an Enterprise Agreement (EA). Development environments must be licensed for the duration of the…

This question tests knowledge of Dynamics 365 Finance development environment licensing options and when to apply pay-as-you-go versus subscription-based models to optimize cost management during an implementation.

Architect solutions

Question

Drag and Drop Question A company plans to implement Dynamics 365 Finance and purchase licenses through an Enterprise Agreement (EA). Development environments must be licensed for the duration of the implementation. You need to recommend solutions for activating development environments that allows the company to manage costs based on usage. What should you recommend? To answer, drag the appropriate solutions to the correct requirements. Each requirement 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:

Explanation

Approach. Requirement 1 (activate without paying upfront / manage costs based on usage) maps to Pay-as-you-go (Box 1): this model bills only for actual consumption hours via an Azure subscription, so there is no upfront commitment and costs scale directly with usage - ideal when dev environments may sit idle. Requirement 2 (activate for a fixed, known duration) maps to Subscription (Box 2): a subscription license covers a defined term at a predictable flat rate, which suits scenarios where the implementation timeline is set and the environment will be used continuously. Visual Studio Enterprise subscription (Box 3) is a valid supplemental option for individual developer access rights in Microsoft cloud environments, but it does not directly address the 'manage costs based on usage' or 'fixed duration' framing in this scenario. Microsoft 365 license (Box 4) is unrelated to Dynamics 365 Finance development environment activation.

Concept tested. Dynamics 365 Finance development environment licensing strategies - specifically the difference between pay-as-you-go (consumption-based, no upfront cost) and subscription-based (fixed-term, predictable cost) activation models within the context of a Lifecycle Services (LCS)-managed implementation under an Enterprise Agreement.

Reference. Microsoft Learn: 'Licensing guide for Dynamics 365' and 'Deploy and use environments' in Dynamics 365 Finance Lifecycle Services documentation.

Topics

#Dynamics 365 Licensing#Development Environments#Cost Management#Enterprise Agreement

Community Discussion

No community discussion yet for this question.

Full MB-700 Practice