Microsoft MB-700 Practice Test - Questions Answers, Page 14

Box 1: Provision the vendor users

Box 2: Initiate a workflow

Set up workflows to process vendor collaboration user requests To help guarantee that all the relevant tasks are completed, and that the appropriate approvals are given, you must set up workflows to handle vendor collaboration user requests.

Vendor collaboration user requests are submitted either by external vendors that have the Vendor admin (external) security role or similar permissions, or by procurement professionals in your company. They can also be generated from prospective vendor registration requests during the vendor onboarding process.

There are three types of requests:

Requests to provision a new user

Requests to inactivate an existing user

Requests to modify the security roles of an existing user

You must create two or more workflows to process all three types of vendor collaboration user requests.

Reference: https://docs.microsoft.com/en-us/dynamics365/supply-chain/procurement/set-upmaintain-vendor-collaboration#set-up-workflows-to-process-vendor-collaboration-user-requests

Box 1: Two

Customers will be able to take up to 7 service updates per year and are required to take a minimum of 2 service updates per year.

Box 2: Three Customers can choose to pause up to 3 consecutive updates at a time. Pausing a service update can apply to the designated user acceptance testing (UAT) sandbox, production, or both environments.

After the pause window has ended and if the customer has not self-updated to a supported service update, Microsoft will auto-apply the latest update based on the configuration selection made available in Lifecycle Services (LCS).

Reference: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/publicpreview-releases

Box 1: Electronic reporting You can use Electronic reporting (ER) to format vendor checks. Many bank-specific and check provider–specific check formats are available on the market. Sample check formats have been included in the Payment check model in the ER tool repository. These sample checks are labeled Check in the middle (US) and Check on top stub below (US).

Box 2: Document management Business document management is built on top of the ER framework and enables business users to edit business document templates by using Microsoft 365 service or appropriate Microsoft Office desktop application. Edits to the documents might include changing business document designs and adding placeholders for additional data without source code changes and new deployments. No knowledge of the ER framework is required to update templates of business documents.

Reference: https://docs.microsoft.com/en-us/dynamics365/finance/accounts-payable/electronicreporting-sample-vendor-checks

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/analytics/er-businessdocument-management

Box 1: Onboard

Phase two: Onboard Work with your key stakeholders to build and launch your adoption plan. Prepare your environment and test your adoption approach with Early Adopters. Use feedback to make adjustments before scaling to the business. In this phase, you will:

Build your adoption plan.

Launch to Early Adopters.

Adjust your plan.

Box 2: Drive value

Phase three: Drive value Full-scale deployment and business success depend on usage and satisfaction. This requires planning through the Envision and Onboard phases plus ongoing operational excellence. In this phase, you will:

Monitor end-user adoption.

Measure and report usage.

Encourage ongoing engagement.

Reference: https://docs.microsoft.com/en-us/dynamics365/adoption/adoption-guide

Box 1: Positive Pay Positive Pay within Dynamics AX is one of the easiest systems to put into place to help prevent check fraud and protect your business. Positive Pay generates an electronic file that you can submit to your bank with a list of your approved checks, reducing the chance of processing any fraudulent checks.

Box 2: Electronic reporting

Electronic reporting (ER) is a configurable tool that helps you create and maintain regulatory electronic reporting and payments.

You can use ER to configure formats for both incoming and outgoing electronic documents in accordance with the legal requirements of various countries and regions. ER lets you manage these formats during their lifecycle. For example, you can adopt new regulatory requirements and generate business documents in the required format to electronically exchange information with government bodies, banks, and other parties.

The ER engine is targeted at business users instead of developers. Because you configure formats instead of code, the processes for creating and adjusting formats for electronic documents are faster and easier.

Reference: https://stoneridgesoftware.com/how-to-generate-positive-pay-text-files-in-dynamics-ax/

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/analytics/general-electronicreporting

Box 1: Server and Cloud Enrollment (SCE) The Server and Cloud Enrollment (SCE) is a licensing vehicle under the Microsoft Enterprise Agreement that enables organizations to standardize on one or more Microsoft Server and Cloud technologies.

To enroll, an installed base-wide commitment, or monetary commitment in the case of Azure, is required to one or more of the following four SCE components:

• Core Infrastructure

• Application Platform

• Developer Platform

• Microsoft Azure

Enrolling in SCE requires the following:

• Enterprise Agreement: Although you need to sign an Enterprise Agreement, an Enterprise Enrollment for Desktop is not needed to qualify.

• Annuity coverage: 100 percent Software Assurance or Subscription coverage is required on your install base for each product family that you commit to. This includes those licenses that were not covered by Software Assurance when you entered the program.

Box 2: Azure Subscription Environment

Reference: https://www.microsoft.com/licensing/docs/view/Enterprise-Agreement-EA-EAS-SCE

Box 1: Export database

Export a database

Dynamics Lifecycle Services (LCS) to export a database from a sandbox user acceptance testing (UAT) environment to the Asset library.

After the export operation completes successfully, sign out of the servicing operation on your Environment details page. You can then see the asset in your Asset Library in the Database backups section.

The .bacpac files are stored here and can be manually downloaded to your Tier 1 developer environments for import.

Box 2: Refresh database

Refresh database You can use Microsoft Dynamics Lifecycle Services (LCS) to perform a refresh of the database to a sandbox user acceptance testing (UAT) environment. A database refresh lets you copy the transactional and financial reporting databases of your production environment into the target, sandbox UAT environment. If you have another sandbox environment, you can also copy the databases from that environment to your target, sandbox UAT environment.

Reference: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/database/exportdatabase

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/database/database-refresh

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, welltested, 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.

Reference: https://docs.microsoft.com/en-us/dynamics365/fasttrack/solution-workshops

https://docs.microsoft.com/en-us/dynamics365/fasttrack/go-live-workshops

https://docs.microsoft.com/en-us/dynamics365/fasttrack/implementation-workshops#cutoverstrategy

Box 1: Implementation

Implementation workshops provide timely guidance across the functional, technical, and implementation aspects of the solution. This includes:

Data migration strategy

Security model design

Etc.

Box 2: Solution Blueprint Review

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 Note: A Solution Blueprint Review workshop serves as the starting point of Success by Design. It is a mandatory workshop that sets the stage for the FastTrack engagement and provides a baseline to plan other Success by Design activities and workshops. The primary purpose of this workshop is to ensure that the fundamentals for project success are in place and the overall solution design approach is sound and aligned to the product best practices and direction.

Reference: https://docs.microsoft.com/en-us/dynamics365/fasttrack/implementation-workshops

https://docs.microsoft.com/en-us/dynamics365/fasttrack/solution-workshops