考試 MB-700: Microsoft Dynamics 365:Finance and Operations 應用解決方案架構師

五月 13, 2022 by
Filed under: killtest 

考試 MB-700: Microsoft Dynamics 365:Finance and Operations 應用解決方案架構師
該考試的考生為 Microsoft Dynamics 365 專業人士,他們為利益幹系人提供建議,並將業務需求轉換成安全、可縮放和可靠的解決方案。

考生應瞭解所有的 Dynamics 365 應用以及 Power Platform。 他們必須對「財務和運營」應用程式有著深刻的理解。 此外,他們還在一個或多個垂直行業中擁有廣泛的專業知識。 該角色需要瞭解每個領域中的決策如何影響整個解決方案。

重要

此考試的英語版本將於 2022 年 4 月 22 日更新。 請下載下面的技能測試文檔,看看有何變化。

及格分數:700 分。
安排考試
考試 MB-700: Microsoft Dynamics 365:Finance and Operations 應用解決方案架構師
語言: 英語

截止日期: 無

該考試可測試你完成以下技術任務的能力:構建解決方案;定義解決方案策略;管理實施方案;以及管理測試。
$115 USD*
價格根據考試所在國家或地區而定。
測試的技能
此考試的英語版本將於 2022 年 4 月 22 日更新。 請下載下面的考試技能大綱,看看有何變化。
構建解決方案 (25-30%)
定義解決方案策略 (25-30%)
管理實施方案 (25-30%)
管理測試 (10-15%)
考試技能大綱:
Exam MB-700: Microsoft Dynamics 365 – Finance and
Operations Apps Solution Architect – Skills Measured
The English language version of this exam was updated on April 22, 2022.
Following the current exam guide, we have included a version of the exam guide
with Track Changes set to “On,” showing the changes that were made to the
exam on that date.
NOTE: Passing score: 700. Learn more about exam scores.
Audience Profile
Candidates for this exam are Microsoft Dynamics 365 professionals who advise stakeholders and
translate business requirements into secure, scalable, and reliable solutions.
Candidates should have knowledge of the Dynamics 365 ecosystem and Microsoft Power
Platform. They must have deep understanding of Dynamics 365 Finance, Dynamics 365 Supply
Chain Management, Dynamics 365 Commerce, and Dynamics 365 Project Operations. In
addition, they have extensive domain knowledge in one or more industry verticals. This role
requires understanding how decisions affect the overall solution.
Skills Measured
NOTE: The bullets that follow each of the skills measured are intended to illustrate how we are
assessing that skill. Related topics may be covered in the exam.
NOTE: Most questions cover features that are general availability (GA). The exam may contain
questions on Preview features if those features are commonly used.
Architect solutions (20-25%)
Gather requirements
• identify operational and organizational challenges that may affect a business
• identify existing business processes and opportunities to optimize business processes
• gather information about expected transaction volume
• categorize business requirements and perform gap fit analyses
• review and validate business requirements throughout the solution lifecycle
Define the solution architecture
• map business requirements to functional components
• evaluate whether to build versus buy for selected business requirements
• identify opportunities to integrate other Microsoft technologies
• select the appropriate implementation tools including LCS and Azure DevOps
• describe the Success by Design process
• create solution architecture diagrams
Describe and document the solution blueprint
• define an organization including company information, locations, and structure
• document the implementation timeline including roll-out strategies
• define the business process catalog and document solution gaps
• define instances, environments, and solution components
• develop a disaster recovery strategy
• identify required security roles
Define solution strategies (35-40%)
Select a deployment strategy
• develop a process to manage solution code and deployment
• select a deployment model and identify instances and environments required for the
selected deployment model
• describe the One Version strategy for Dynamics 365 and the effects of One Version on
solutions
• segment solution development and delivery into logical phases
• provide alternative methodologies and approaches for deploying modifications
• determine solution maintenance cadence and timelines
• identify upgrade scenarios and select appropriate tools
Define an application lifecycle management (ALM) strategy
• define a code management and data flow strategy
• define a Microsoft Power Platform solution management strategy
• determine which build automation capabilities to implement
• define a roll-back strategy for solution code and data
Determine a data management strategy
• differentiate between transactional and historical data
• define data quality and data validation process
• define data cleansing and transformation strategies
• define data dependencies
• develop a data migration strategy for master, transactional, reference, parameter, and
document data entities
• develop data cut-over and data retention plans
Define the security architecture
• differentiate between Azure, Dynamics 365, and infrastructure security
• describe Azure and infrastructure security-related elements
• describe use cases for and capabilities of record-level and role-based security in
Dynamics 365
Define the integration architecture
• select an integration pattern including OData, Microsoft Power Platform, Batch Data API,
Azure Data Lake, Business events, and Dual-write
• identify required integration and interface details
• design integrations
• define an integration testing strategy
Define the business intelligence and reporting architecture
• gather business intelligence and reporting requirements
• define data sources required to meet business intelligence and reporting requirements
• select appropriate business intelligence and reporting tools including Power BI,
organizational workspaces, financial reports, SQL Server Reporting Services (SSRS), and
the Electronic Reporting tool
• define printing requirements including Print management, Document Routing Agent
(DRA), modern report design layout templates, check printing, and label printing
Manage implementations (20-25%)
Describe Lifecycle Services (LCS) tools
• understand the use cases and capabilities of different LCS tools
• understand the use cases and capabilities of Business Process Modeler (BPM)
• understand the use cases and capabilities of LCS Methodologies
• create a usage profile to describe current or projected usage
Manage interactions with FastTrack
• identify the value proposition for FastTrack
• identify FastTrack engagement types and personnel roles
• describe typical types of FastTrack workshops and the inputs for each workshop
• describe go-live checklist elements
Determine support options
• develop a support plan and strategy
• define post-go-live support plans including response times and service-level agreements
(SLAs)
• describe use cases and capabilities for the LCS Support tool
Determine licensing requirements
• determine the types of licenses required
• estimate the number of licenses required by using the License Sizing estimator
• describe the process for estimating ongoing software licensing costs
Manage testing (10-15%)
Define a testing strategy
• define a testing strategy that includes all required types of testing
• define a regression testing strategy
• identify opportunities for automated testing
• review use cases and test coverage for business scenarios
• determine when to use RSAT, SysTest, Postman, ATL, Azure DevOps Test Plans, and other
tools
Define a performance testing strategy
• define performance goals and requirements
• identify performance monitoring and testing tools
• define performance benchmarks and success criteria
• design a performance and load testing strategy
• troubleshoot performance issues
The following exam guide shows the changes that were implemented on April,
2022 to the English language version of this exam.
Audience Profile
Candidates for this exam are Microsoft Dynamics 365 professionals who advise stakeholders and
translate business requirements into secure, scalable, and reliable solutions.
Candidates should have knowledge of all the Dynamics 365 apps ecosystem and Microsoft
Power Platform. They must have deep understanding of Finance and Operations appsDynamics
365 Finance, Dynamic 365 Supply Chain Management, Dynamics 365 Commerce, and Dynamics
365 Project Operations. In addition, they have extensive domain knowledge in one or more
industry verticals. This role requires understanding how decisions in each area affects the overall
solution.
Skills Measured
NOTE: The bullets that follow each of the skills measured are intended to illustrate how we are
assessing that skill. Related topics may be covered in the exam.
NOTE: Most questions cover features that are general availability (GA). The exam may contain
questions on Preview features if those features are commonly used.
Architect solutions (25-3020-25%)
Gather requirements
• identify operational and organizational challenges that may affect a business
• identify existing business processes and opportunities to optimize business processes
• gather information about expected transaction volume
• categorize business requirements and perform gap fit analyses
• review and validate business requirements throughout the solution lifecycle
Define the solution architecture
• map business requirements to functional components
• evaluate whether to build versus buy for selected business requirements
• identify opportunities to integrate other Microsoft technologies
• select solution design patterns
• select the appropriate tools to implementation tools including LCS and Azure DevOps
• describe the Success by Design process
• create solution architecture diagrams
Describe and document the solution blueprint
• define an organization and organization locations including intercompany information
• define an organization including company information, locations, and structure
• document the implementation timeline including roll-out strategies
• define the business process catalog and document solution gaps
• define instances, environments, and solution components
• develop a disaster recovery strategy
• identify required integration and interface details
• define required business intelligence and reporting components
• identify required security roles
Define solution strategies (25-3035-40%)
Select a deployment strategy
• develop a change management and adoption processprocess to manage solution code
and deployment
• select a deployment model and identify instances and environments required for the
selected deployment model
• describe the One Version strategy for Dynamics 365 One Version strategy and the
effects of One Version on solutions
• segment solution development and delivery into logical phases
• provide alternative methodologies and approaches for deploying modifications
• determine solution maintenance cadence and timelines
• identify upgrade scenarios and select appropriate tools
Define an application lifecycle management (ALM) strategy
• define a code management and data flow strategy
• define a Microsoft Power Platform solution management strategy
• determine which build automation capabilities to implement
• define a roll-back strategy for Finance and Operations apps and Power Platform
solutionssolution code and data
Determine a data management strategy
• differentiate between transactional and historical data
• define data quality and data validation process
• define data cleansing and transformation strategies
• define data dependencies
• develop a data migration strategy for master, transactional, reference, parameter, and
document data entities
• develop data cut-over and data retention plans
Define the security architecture
• differentiate between Azure, Dynamics 365, and infrastructure security
• describe Azure and infrastructure security-related elements
• describe use cases for and capabilities of record-level and role-based security in
Dynamics 365
Define the integration architecture
• select an integration pattern including OData, Microsoft Power Platform, Batch Data API,
Azure Data Lake, Business events, and Dual-write
• identify required integration and interface details
• design integrations
• define an integration testing strategy
Define the business intelligence and reporting architecture
• gather business intelligence and reporting requirements
• define data sources required to meet business intelligence and reporting requirements
• select appropriate business intelligence and reporting tools including Power BI,
organizational workspaces, financial reports, SQL Server Reporting Services (SSRS), and
the Electronic Reporting tool
• define printing requirements including Print management, Document Routing Agent
(DRA), modern report design layout templates, check printing, and label printing
Manage implementations (25-3020-25%)
Describe Lifecycle Services (LCS) tools
• understand the use cases and capabilities of different LCS tools
• understand the use cases and capabilities of Business Process Modeler (BPM)
• understand the use cases and capabilities of LCS Methodologies
• create a usage profile to describe current or projected usage
• describe uses cases and capabilities for LCS downloadable tools
Manage interactions with FastTrack
• identify the value proposition for FastTrack
• identify FastTrack engagement types and personnel roles
• describe typical types of FastTrack workshops scoping and the inputs for each workshop
• describe go-live checklist elements
Determine support options
• develop a support plan and strategy
• define post-go-live support plans including response times and service-level
agreements (SLAs)
• describe use cases and capabilities for the LCS Support tool
Determine licensing requirements
• determine the types of licenses required
• estimate the number of licenses required by using the License Sizing estimator
• describe the process for estimating ongoing software licensing costs
Manage testing (10-15%)
Define a testing strategy
• define a testing strategy that includes all required types of testing
• define a regression testing strategy
• identify opportunities for automated testing
• review use cases and test coverage for all business scenarios
• determine when to use RSAT versus SysTest framework versus Postman versus ATL and
other toolsDetermine when to use RSAT, SysTest, Postman, ATL, Azure DevOps Test
Plans, and other tools
Define a performance testing strategy
• define performance goals and requirements
• identify performance monitoring and testing tools
• define performance benchmarks and success criteria
• design a performance and load testing strategy
• troubleshoot performance issues

Comments

Tell me what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!





*