Free MB-700 Exam Braindumps (page: 31)

Case study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.

To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.

At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.

To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background

Blue Yonder Airlines is a private airline company established in 1963 in Boston. The company completes over 2,000 flights a day with flights operating exclusively in North AmericA. Blue Yonder Airlines is in the planning phase for replacing its current enterprise resource planning (ERP) with Dynamics 365 Finance, Supply Chain Management, and Commerce and is making solution architecture decisions prior to engaging the remainder of the implementation team.

Current environment

Technology
-Blue Yonder Airlines operates on a custom-built ERP solution.
-Blue Yonder Airlines uses a proprietary reporting and analytics platform that reports on data between multiple systems, including the ERP solution.
-The ERP solution automatically pushes transactional data every five minutes to a separate database that the reporting and analytics platform uses for sales and operations planning (S&OP) activities.
-SQL Server Reporting Services (SSRS) reports are used for several financial reports that are sent to vendors in the existing ERP solution.
-Users utilize a third-party tool that selects alternate layouts of the reports depending on the users' requirements.
-Blue Yonder Airlines currently uses Microsoft 365 and Office 365.

Implementation

-The implementation of new solutions and features follows an Agile implementation strategy.
-Blue Yonder Airlines has several highly skilled project managers.
-Blue Yonder Airlines has a live Microsoft Dataverse instance that runs several model driven Microsoft Power Apps apps. Several initiatives using Microsoft Power Automate and Power Virtual Agents are in the middle of implementations.

Development
-There are five different functional groups, called pods, which fully own their development cycles for different functionality in their ERP.
-All code is deployed and managed by using Microsoft Visual Studio projects.
-All development environments are currently hosted by a third-party company. The current costs are very expensive.
-Blue Yonder Airlines plans to use the new ERP implementation to address performance and integration issues.

Licensing
-Blue Yonder Airlines does not require licensing on its ERP solution because the system is custom.
-Most users have more access within the ERP solution than requireD.

Requirements

Technology
-The previous custom ERP data will be replaced with Dynamics 365 Finance and Operations apps in the current reporting and analytics platform.
-Only native Dynamics 365 capabilities should be useD.
-The level of effort required from IT staff must remain the same.
-Standard SSRS reports will be useD.
-The current third-party financial reporting tool does not integrate with Dynamics 365.
-Blue Yonder Airlines has a highly experienced in-house team of implementation experts. It will implement Dynamic by using only internal employees. No Microsoft partner will be engaged in the implementation.

Data
-Historical data will remain in the current system for reporting purposes.
-Some sample data that needs to be migrated to Dynamics 365 includes:
- Data set 1 - Active airplanes - Planes that actively transport customers
- Data set 2 - Queued flights - Completed flights but not yet invoiced will be migrated
- Data set 3 - Flight consumption measurement - Units of measurement of gasoline consumed per flight
- Data set 4 - VIP customers - Customers that average $3,000 USD per flight

Development
-Each of the pods' development teams must be able to deploy all of its code independently from one another.
-Overlayering of base Microsoft or third-party code must be preventeD.
-Each developer must have their own environment.
-Development environment costs should be as low as possible.
-Developers should be able to access their development environments 24 hours a day.
-The development team must create a performance strategy that involves the functional implementation team and the different development teams by using Microsoft recommendations.

User configuration
-To save on implementation costs. Blue Yonder Airlines will determine which base security roles to assign to which users to conduct their day-to-day operations. Only base security roles will be used without modification.

Issues

Development
-The development and functional teams are not taking ownership of the performance benchmark testing. There are no functional designs, benchmark scenarios, or expectations setting created to date.

Security
-Blue Yonder Airlines does not know how to configure the security of the users to enable access to complete its day-to-day operations.

Licensing
-A licensing compliance audit has determined that the correct number of employees are added to the system but too many base and attach licenses are being useD.
-Some users will likely have to consolidate duties to maintain compliance.
-

Case study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.

To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.

At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.

To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background

Blue Yonder Airlines is a private airline company established in 1963 in Boston. The company completes over 2,000 flights a day with flights operating exclusively in North AmericA. Blue Yonder Airlines is in the planning phase for replacing its current enterprise resource planning (ERP) with Dynamics 365 Finance, Supply Chain Management, and Commerce and is making solution architecture decisions prior to engaging the remainder of the implementation team.

Current environment

Technology
-Blue Yonder Airlines operates on a custom-built ERP solution.
-Blue Yonder Airlines uses a proprietary reporting and analytics platform that reports on data between multiple systems, including the ERP solution.
-The ERP solution automatically pushes transactional data every five minutes to a separate database that the reporting and analytics platform uses for sales and operations planning (S&OP) activities.
-SQL Server Reporting Services (SSRS) reports are used for several financial reports that are sent to vendors in the existing ERP solution.
-Users utilize a third-party tool that selects alternate layouts of the reports depending on the users' requirements.
-Blue Yonder Airlines currently uses Microsoft 365 and Office 365.

Implementation

-The implementation of new solutions and features follows an Agile implementation strategy.
-Blue Yonder Airlines has several highly skilled project managers.
-Blue Yonder Airlines has a live Microsoft Dataverse instance that runs several model driven Microsoft Power Apps apps. Several initiatives using Microsoft Power Automate and Power Virtual Agents are in the middle of implementations.

Development
-There are five different functional groups, called pods, which fully own their development cycles for different functionality in their ERP.
-All code is deployed and managed by using Microsoft Visual Studio projects.
-All development environments are currently hosted by a third-party company. The current costs are very expensive.
-Blue Yonder Airlines plans to use the new ERP implementation to address performance and integration issues.

Licensing
-Blue Yonder Airlines does not require licensing on its ERP solution because the system is custom.
-Most users have more access within the ERP solution than requireD.

Requirements

Technology
-The previous custom ERP data will be replaced with Dynamics 365 Finance and Operations apps in the current reporting and analytics platform.
-Only native Dynamics 365 capabilities should be useD.
-The level of effort required from IT staff must remain the same.
-Standard SSRS reports will be useD.
-The current third-party financial reporting tool does not integrate with Dynamics 365.
-Blue Yonder Airlines has a highly experienced in-house team of implementation experts. It will implement Dynamic by using only internal employees. No Microsoft partner will be engaged in the implementation.

Data
-Historical data will remain in the current system for reporting purposes.
-Some sample data that needs to be migrated to Dynamics 365 includes:
- Data set 1 - Active airplanes - Planes that actively transport customers
- Data set 2 - Queued flights - Completed flights but not yet invoiced will be migrated
- Data set 3 - Flight consumption measurement - Units of measurement of gasoline consumed per flight
- Data set 4 - VIP customers - Customers that average $3,000 USD per flight

Development
-Each of the pods' development teams must be able to deploy all of its code independently from one another.
-Overlayering of base Microsoft or third-party code must be preventeD.
-Each developer must have their own environment.
-Development environment costs should be as low as possible.
-Developers should be able to access their development environments 24 hours a day.
-The development team must create a performance strategy that involves the functional implementation team and the different development teams by using Microsoft recommendations.

User configuration
-To save on implementation costs. Blue Yonder Airlines will determine which base security roles to assign to which users to conduct their day-to-day operations. Only base security roles will be used without modification.

Issues

Development
-The development and functional teams are not taking ownership of the performance benchmark testing. There are no functional designs, benchmark scenarios, or expectations setting created to date.

Security
-Blue Yonder Airlines does not know how to configure the security of the users to enable access to complete its day-to-day operations.

Licensing
-A licensing compliance audit has determined that the correct number of employees are added to the system but too many base and attach licenses are being useD.
-Some users will likely have to consolidate duties to maintain compliance.
-

Case study

This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provideD.

To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.

At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.

To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background
VanArsdel, LtD. is a company that uses Microsoft Dynamics AX 2012 R3 in the United States, Canada, Mexico, and Brazil in an on-premises environment. The company implemented the solution by using Sure Step 2012. VanArsdel, LtD. plans to upgrade to Dynamics 365 Finance, Dynamics 365 Supply Chain Management, and Dynamics 365 Commerce using Proseware, InC. as the implementation partner.

VanArsdel, LtD. has implemented 13 other software systems for customer management and sales.

Current Environment

Methodology
VanArsdel, LtD. deploys a proprietary methodology named VanPMP. The company plans to use VanPMP for all software implementations. The company uses a standard project template for all new implementations.

Solution
Microsoft Power Apps is used by the sales team to enter sales orders. The orders are then integrated with the current Dynamics AX 2012 R3 instance asynchronously once every hour. All sales orders are invoiced through the invoicing batch process at the end of the day. Sales are used for all business-critical scenarios.

The external systems include 12 integrations, such as Microsoft Power Platform, Office 365, Azure, and third-party systems.

One of the automated accounts receivable import integrations, named integration 1, generates revenue in a business-to-business (B2B) scenario that is supported by sales orders. The integration runs every night and is always the first integration to be testeD.

All regression testing is completed manually.

Security
The company uses Dynamics AX 2012 R3 in all the countries/regions in which they operate.

Because VanArsdel, LtD. operates within the United States, the company must comply with government financial compliance standards. Government compliance requires that VanArsdel, LtD. manufacturing divisions must not be able to approve purchase orders. Manufacturing managers must not be able to access data in other manufacturing sites. The manufacturing divisions belong to a single legal entity with multiple sites.

Requirements

Licensing
The implementation requires the following Dynamics 365 licenses:

-120 Supply Chain Management licenses
-60 Finance licenses
-50 Commerce licenses

Methodology
The implementation must use the VanArsdel, LtD. proprietary methodology for the Dynamics 365 implementation. The methodology in the project template must use the Microsoft-recommended approach. Progress must be tracked in a central location for VanArsdel, Ltd,, Microsoft, and Proseware, InC. to view.

VanArsdel LtD. requires a sample methodology in Lifecycle Services (LCS).

The project must coordinate project dates in the methodology with any required Microsoft touchpoints to ensure that the project is on track and implemented according to best practices.

Solution
The sales order entry Power Apps integration must be configured by using out-of-the-box solutions.

Integrations
The company has the following integration requirements:

-Four integrations must run asynchronously.
-Eight integrations must run synchronously.
-The integrations must be able to run after applying updates to the system.

All items must have their own item pricing. Each item must have an MSRP and a selling price that is determined based on the date and location.

Testing
The user reporting test case needs to be reviewed by using the same process in the test environment.

The Regression suite automation tool (RSAT) must be used to automate every critical scenario. All other testing must be performed manually.

Integration 1 must be deployed first. All data must be created and tested in the correct sequence to ensure that pricing is applied correctly to the item.

Security
Dynamics 365 must be rolled out incrementally by country/region. The implementation must go live in the United States first, and then continue to the other countries/regions over the next 12 months.

VanArsdel, Ltd, must assign access to new users based on the site of the users.

VanArsdel, LtD. requires that Proseware, InC. perform the following:

-Objective 1. Determine the software licensing costs for the system based on the contracted costs determined during the start of the project.
-Objective 2. Audit the security roles for users in the manufacturing division.

Issues
Some users report that too many fields are displayed when the users create records in the Dynamics 365 AX 2012 R3 instance. These fields often prevent users from being productive.

Statement of work concerns
Before the project kickoff, several of the VanArsdel, LtD. IT team members had concerns after reviewing the statement of work. The primary concerns were raised by the following team members

An administrator named Admin1 reports a performance impact on multiple large integrations with the Dynamics 365 AX 2012 R3 implementation.
An administrator named Admin2 reports a concern with environment management with the global rollout.

All concerns must be reviewed and scheduled with all solution architects in workshops.

Testing
The Dynamics 365 AX 2012 R3 instance experiences frequent issues due to users running reports for an extended period of time on the same Application Object Server (AOS) service. A user named User1 reports a delay retrieving the same report in Dynamics 365.

Case study

This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provideD.

To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.

At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.

To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Background
VanArsdel, LtD. is a company that uses Microsoft Dynamics AX 2012 R3 in the United States, Canada, Mexico, and Brazil in an on-premises environment. The company implemented the solution by using Sure Step 2012. VanArsdel, LtD. plans to upgrade to Dynamics 365 Finance, Dynamics 365 Supply Chain Management, and Dynamics 365 Commerce using Proseware, InC. as the implementation partner.

VanArsdel, LtD. has implemented 13 other software systems for customer management and sales.

Current Environment

Methodology
VanArsdel, LtD. deploys a proprietary methodology named VanPMP. The company plans to use VanPMP for all software implementations. The company uses a standard project template for all new implementations.

Solution
Microsoft Power Apps is used by the sales team to enter sales orders. The orders are then integrated with the current Dynamics AX 2012 R3 instance asynchronously once every hour. All sales orders are invoiced through the invoicing batch process at the end of the day. Sales are used for all business-critical scenarios.

The external systems include 12 integrations, such as Microsoft Power Platform, Office 365, Azure, and third-party systems.

One of the automated accounts receivable import integrations, named integration 1, generates revenue in a business-to-business (B2B) scenario that is supported by sales orders. The integration runs every night and is always the first integration to be testeD.

All regression testing is completed manually.

Security
The company uses Dynamics AX 2012 R3 in all the countries/regions in which they operate.

Because VanArsdel, LtD. operates within the United States, the company must comply with government financial compliance standards. Government compliance requires that VanArsdel, LtD. manufacturing divisions must not be able to approve purchase orders. Manufacturing managers must not be able to access data in other manufacturing sites. The manufacturing divisions belong to a single legal entity with multiple sites.

Requirements

Licensing
The implementation requires the following Dynamics 365 licenses:

-120 Supply Chain Management licenses
-60 Finance licenses
-50 Commerce licenses

Methodology
The implementation must use the VanArsdel, LtD. proprietary methodology for the Dynamics 365 implementation. The methodology in the project template must use the Microsoft-recommended approach. Progress must be tracked in a central location for VanArsdel, Ltd,, Microsoft, and Proseware, InC. to view.

VanArsdel LtD. requires a sample methodology in Lifecycle Services (LCS).

The project must coordinate project dates in the methodology with any required Microsoft touchpoints to ensure that the project is on track and implemented according to best practices.

Solution
The sales order entry Power Apps integration must be configured by using out-of-the-box solutions.

Integrations
The company has the following integration requirements:

-Four integrations must run asynchronously.
-Eight integrations must run synchronously.
-The integrations must be able to run after applying updates to the system.

All items must have their own item pricing. Each item must have an MSRP and a selling price that is determined based on the date and location.

Testing
The user reporting test case needs to be reviewed by using the same process in the test environment.

The Regression suite automation tool (RSAT) must be used to automate every critical scenario. All other testing must be performed manually.

Integration 1 must be deployed first. All data must be created and tested in the correct sequence to ensure that pricing is applied correctly to the item.

Security
Dynamics 365 must be rolled out incrementally by country/region. The implementation must go live in the United States first, and then continue to the other countries/regions over the next 12 months.

VanArsdel, Ltd, must assign access to new users based on the site of the users.

VanArsdel, LtD. requires that Proseware, InC. perform the following:

-Objective 1. Determine the software licensing costs for the system based on the contracted costs determined during the start of the project.
-Objective 2. Audit the security roles for users in the manufacturing division.

Issues
Some users report that too many fields are displayed when the users create records in the Dynamics 365 AX 2012 R3 instance. These fields often prevent users from being productive.

Statement of work concerns
Before the project kickoff, several of the VanArsdel, LtD. IT team members had concerns after reviewing the statement of work. The primary concerns were raised by the following team members

An administrator named Admin1 reports a performance impact on multiple large integrations with the Dynamics 365 AX 2012 R3 implementation.
An administrator named Admin2 reports a concern with environment management with the global rollout.

All concerns must be reviewed and scheduled with all solution architects in workshops.

Testing
The Dynamics 365 AX 2012 R3 instance experiences frequent issues due to users running reports for an extended period of time on the same Application Object Server (AOS) service. A user named User1 reports a delay retrieving the same report in Dynamics 365.