As a candidate for this exam, you’re a developer who works with finance and operations apps in Microsoft Dynamics 365 to implement and extend applications that meet the requirements of a business. You provide fully realized solutions by using:
◉ Standardized application coding patterns
◉ Extensible features
◉ External integrations
As a candidate for this exam, you do the following:
◉ Develop business logic by using X++.
◉ Create and modify finance and operations app reports and workspaces.
◉ Customize user interfaces.
◉ Provide endpoints and APIs to support Microsoft Power Platform apps and external systems.
◉ Perform testing.
◉ Monitor performance.
◉ Analyze and manipulate data.
You also create technical designs and implementation details, and implement permission policies and security requirements.
You should have a deep knowledge and experience using the underlying framework, data structures, and objects associated with the finance and operations solutions.
You should have experience with products and services that include Microsoft Visual Studio, Power Apps, Power Automate, Azure DevOps, Lifecycle Services tools, Microsoft Azure, Postman, GitHub, Microsoft 365, reporting tools [for example, SQL Server Reporting Services (SSRS), Power BI], and SQL Server Management Studio.
Microsoft Dynamics 365 Finance and Operations Apps Developer Exam Summary:
| Exam Name | Microsoft Certified - Dynamics 365 - Finance and Operations Apps Developer Associate |
| Exam Code | MB-500 |
| Exam Price | $165 (USD) |
| Exam Price | 120 mins |
| Number of Questions | 40-60 |
| Passing Score | 700 / 1000 |
| Books / Training | MB-500T00-A: Microsoft Dynamics 365: Finance and Operations Apps Developer |
| Sample Questions | Microsoft Dynamics 365 Finance and Operations Apps Developer Sample Questions |
| Practice Exam | Microsoft MB-500 Certification Practice Exam |
Microsoft MB-500 Exam Syllabus Topics:
| Topic | Details |
| Plan the architecture and solution design (5-10%) | |
| Identify the major components of Dynamics 365 finance and operations apps | - Identify finance and operations app modules required for a solution based on business requirements - Identify architectural differences between the cloud and on-premises versions of finance and operations apps - Identify components of the application stack - Differentiate the purposes and interrelationships between packages, projects, models, and elements |
| Design and implement a UI | - Describe the finance and operations UI layouts and components - Design workspaces - Design and personalize UI elements including forms and saved views - Define navigation elements including menus and menu items - Configure filtering and sorting options |
| Implement Application Lifecycle Management (ALM) and Microsoft Dynamics 365 Lifecycle Services | - Describe the capabilities of the Environment Monitoring Tool within Lifecycle Services - Select the purpose and appropriate uses of Lifecycle Services tools and components - Research and resolve issues by using Issue Search - Identify activities that require asset libraries - Prepare deployment packages and deploy packages between environments |
| Apply developer tools (5-10%) | |
| Customize finance and operations apps by using Visual Studio | - Create extension models - Design and build projects - Manage metadata using Application Explorer - Synchronize data dictionary changes with the application database - Create elements by using element designers - Perform debugging activities |
| Manage source code and artifacts by using Microsoft Azure DevOps version control | - Create, check out, and check in code and artifacts - Branch and merge code - Compare code and resolve version conflicts |
| Design and develop AOT elements (15-20%) | |
| Create and extend UI elements | - Add a new form to a project and apply a pattern (template) - Configure a data source for the form - Add a grid and grid fields, groups, and other controls to a form - Create and extend menu and menu items - Test form functionality and data connections - Add a form extension to a project for selected standard forms - Create and use label files |
| Create and extend the data model | - Create and extend tables - Add table fields and field properties to a table - Add field groups, relations, delete actions, methods, and indices - Create and extend views, queries, and maps |
| Create Extended Data Types (EDT) and enumerations | - Add an EDT to a project and populate EDT properties - Add an enumeration to a project - Add or update enumeration elements and enumeration element properties - Add an extension of EDT and enumerations |
| Create classes and extend AOT elements | - Add a new class to a project - Create a new class extension and add new methods - Add event handler methods to a class - Add attributes to a class |
| Develop and test code (20-25%) | |
| Develop X++ code | - Identify and implement base types and operators - Implement common structured programming constructs of X++ - Create, read, update, and delete (CRUD) data - Identify and implement global functions in X++ - Implement table and form methods |
| Develop object-oriented code | - Implement X++ variable scoping - Implement inheritance and abstraction concept - Implement query objects and the QueryBuilder class - Implement attribute classes - Implement chain of command and wrapper classes - Implement event handler class and delegates |
| Implement finance and operations app framework functionality | - Implement the SysOperation framework - Implement the workflow framework - Implement the batch framework - Implement the SysExtensionSerializer |
| Perform testing | - Implement the Regression suite automation tool (RSAT) - Perform unit/component testing using SysTest framework and Task recorder - Perform testing using Acceptance Test Library (ATL) tool |
| Implement reporting (10-15%) | |
| Describe the capabilities and limitations of reporting tools in finance and operations apps | - Create and modify report data sources and supporting classes - Implement reporting security requirements - Describe the report publishing process - Describe the differences between using Entity store and Bring your own database (BYOD) or Azure Data Lake as reporting data stores |
| Design, create, and revise Dynamics 365 reports | - Create and modify reports in finance and operations apps that use SSRS - Create and modify finance and operations apps reports by using Power BI - Create and modify finance and operations apps reports by using Microsoft Excel - Implement Business document management |
| Design, create, and revise Dynamics 365 workspaces | - Design and implement key performance indicators (KPIs) - Create drill-through workspace elements - Implement built-in charts, Power BI embedded visualizations, aggregate measurements, aggregate dimensions, and other reporting components |
| Integrate and manage data solutions (15-20%) | |
| Identify data integration patterns and scenarios | - Identify data integration patterns - Select an appropriate data integration API - Identify differences between synchronous versus asynchronous patterns |
| Implement data integration concepts and solutions | - Develop a data entity by using Visual Studio - Develop, import, and export composite and aggregate data entities - Consume external web services by using RESTful APIs and Simple Object Access Protocol (SOAP) - Implement electronic reporting - Implement custom services and Batch OData API |
| Implement data management | - Import and export data using entities between finance and operations apps and other systems - Monitor the status and availability of entities - Enable change tracking for entities - Set up a data project and recurring data jobs - Design entity sequencing - Generate field mapping between source and target data structures - Develop data transformations |
| Integrate with Microsoft Power Platform, Microsoft 365, and Azure | - Integrate Power Automate and Power Apps with finance and operations apps - Integrate Microsoft Dataverse with finance and operations apps by using dual-write - Integrate Microsoft Dataverse with finance and operations apps by using virtual entities - Integrate finance and operations apps with Microsoft Excel by using OData - Implement business events |
| Implement security and optimize performance (5-10%) | |
| Implement security policies and requirements | - Create or modify duties, privileges, permissions, and roles - Enforce permissions policies - Implement Extensible Data Security (XDS) policies - Enforce Microsoft Entra ID authentication |
| Apply fundamental performance optimization techniques | - Identify and apply caching mechanisms for forms and tables - Implement the global cache and singleton - Create or modify temporary tables for optimization purposes - Determine when to use set-based queries and row-based queries - Modify queries to optimize performance - Modify variable scope to optimize performance - Analyze and optimize concurrency |
| Optimize performance | - Capture traces by using TraceParser and analyze traces - Diagnose and optimize client performance by using browser-based tools - Diagnose and optimize client performance by using Performance Timer - Optimize performance for data entities, data source queries, batch processes, and reports - Implement Async and Sandbox framework |
Posts
0 comments:
Post a Comment