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: o Data set 1 - Active airplanes - Planes that actively transport customers o Data set 2 - Queued flights - Completed flights but not yet invoiced will be migrated o Data set 3 - Flight consumption measurement - Units of measurement of gasoline consumed per flight o 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.
You need to determine which development environments to deploy.
Which environments do you use?
AbhiN1106
1 week, 2 days ago