MB-700 Exam Dumps - Microsoft Dynamics 365: Finance and Operations Apps Solution Architect Expert Questions and Answers

Box 1: Developer

Developer

Developer environments are created by users who have the Developer Plan license. They're special environments intended only for use by the owner. Provisioning developer environments can be restricted to admins (see Block trial licenses commands). The developer environment will be available as long as you actively use the Power Apps Developer Plan.

Box 2: Sandbox

These are non-production environments, which offer features like copy and reset. Sandbox environments are used for development and testing, separate from production. Provisioning sandbox environments can be restricted to admins (because production environment creation can be blocked), but converting from a production to a sandbox environment can't be blocked.

Box 1: Solution Blueprint Review

A Solution Blueprint Review workshop serves as the starting point of Success by Design.

The Solution Blueprint Review workshop covers the following topics:

Program strategy

Application strategy

Data strategy

Integration strategy

Test strategy

*-> Business process strategy

Security strategy

Application lifecycle management strategy

Environment and capacity strategy

Intelligence strategy

Box 2: Go-live Readiness

The Go-live Readiness workshop is designed to help guarantee a successful go-live for Dynamics 365 projects.

Here are some of the topics the workshop is likely to cover:

Confirmation of the go-live date and scope

Solution acceptance and user training

Performance

*-> Integrations

Code management

Configuration management

Review of blocking issues

Cutover plan and final data migration

Risk and mitigation review

Customer go/no-go criteria

Support process and hyper-care plan

Box 3: Implementation

Cutover is part of Implemenation.

Note: Cutover strategy

Ensure that the cutover strategy provides a good approach and plan to deliver a well-defined, well-tested, reliable, and safe transition from current systems to the new production systems.

Agenda topics:

Cutover vision and strategy

Cutover project plan

Go-live cutover plan

Post go-live plan

Mandatory attendees are cutover lead, solution architect, data migration lead, and project manager roles. Recommended attendees include stakeholders from the customer and partner teams.

Box 1: Business process modeler

Business process modeler (BPM) in Microsoft Dynamics Lifecycle Services (LCS) is a tool that you can use to create, view, and modify repeatable implementations that are based on business process libraries. BPM helps you align your business processes with industry-standard processes that are described by the American Productivity & Quality Center (APQC). You can perform fit-gap analysis between your business requirements and the default processes in Finance and Operations apps. Additionally, you can add new business processes that aren't already defined.

BPM is compatible with the following products:

Microsoft Word – You can generate documentation for business processes.

Microsoft Visio – You can export business process maps to Visio files.

Note: Vendors and purchasing

As customers purchase packages, Margie’s Travel can claim rebates with the providing vendor for every package sold. The rebates are claimed quarterly, and internal workflows have been established for approval prior to vendor submission. The workflows for package offerings eligible for rebates can be complex. User2 has created Visio diagrams for the associated approval processes.

Box 2: Regression suite automation tool (RSAT

The Regression suite automation tool (RSAT) significantly reduces the time and cost of user acceptance testing (UAT) of Finance and Operations apps. UAT is typically required before you take a Microsoft application update, or before you apply custom code and configurations to your production environment. RSAT lets functional power users record business tasks by using Task recorder and then convert the recordings into a suite of automated tests, without having to write source code.

Note: The accounts receivable and accounts payable departments are unclear about the workflows associated with the rebate process. User2 must ensure that representatives from each department validate that they have tested their respective steps in the overall process. Testing feedback must be communicated to User2.

Box 1: Consolidation company

Eliminations can be reported in multiple ways:

* A separate company can be created and used to manually determine and post elimination transactions. This company can be used in the consolidation process or in financial reporting.

* Elimination rules can be set up in the system.

* The accounts and financial dimensions that are used to determine intercompany activity can be filtered on a row definition or column definition in Financial reporting, and full drill-down capabilities can be used.

Box 2: Financial reporting

There are multiple options for consolidating data:

* Financial reporting – This option enables consolidation of transactions and balances, and can be generated at any time. Multiple levels of hierarchies can be created, and multiple reporting currencies can be viewed.

* Consolidate online – This option consolidates daily balances by the selected accounts and dimensions, and stores them in a consolidation company.

* Consolidate with import – This option imports balances into a consolidation company.

Export company balances

Note: The CEO is considering the acquisition of additional companies in the same countries as the current companies. The consolidation structure may change within the first 90 days of go-live. Margie’s does not want to finalize the consolidation structure for a hard-close at month’s end until this has been finalized.

Data migration is a key success factor in almost every implementation. A primary concern of some customers is the speed that data can be migrated at, especially if there are vast amounts of data and a small cutover window. The Data migration framework is also used to move data as part of business requirements and operations.

A data package for a Dynamics 365 Finance and Operations app can consist of one or many data entities. A typical data package consists of a group of entities for a specific task, process, or function.

Note: A mock cutover was conducted. It was unsuccessful due to lack of coordination across the countries. The lack of success created timing issues with data uploads from centralized IT and validation at the country level. User1 must use a standard template to prevent the mock cutover issue happening at go-live.

Note:

* The CTO has learned that there are updates to globalization features in Dynamics 365 Finance. The IT staff has been tasked with ensuring that they are the first group to receive these updates.

* The IT department has decided not to code for globalization issues because they are in an upcoming service update. They are closing in on go-live and need to make sure that the updates are applied in time.

Service updates are continuous, touchless updates that provide new features and functionality. You are in control and manage how your organization receives these updates. For example, you can sign up for the First Release program so that your organization receives updates first. You can apply the updates to any of your environments manually (self-update) or remain on the default release schedule and receive the auto-updates when you schedule them using LCS.

Margie’s created a second company based in Jamaica, followed by the acquisition of a third company in the United Kingdom (UK).

All three countries must use Dynamics 365 Finance.

Margie’s Travel wants to enable customer self-service in the future for customers based in the US and UK.