MB-700 Practice Questions

Workspaces in Dynamics 365 Finance are designed to be role-specific landing pages that consolidate key tasks, data, and metrics into a single location. A workspace can include summary tiles, key performance indicators (KPIs), charts for graphical data visualization (like invoice aging), and multiple filtered lists (grids) showing specific records, such as past-due invoices grouped by aging period. Users can directly navigate to the underlying records from these lists, fulfilling all the requirements outlined in the scenario for streamlining a collections specialist's daily activities. The out-of-the-box "Customer credit and collections" workspace is a prime example of this functionality.

A. Forms: Forms are the standard pages for viewing or entering data for a single record type (e.g., all customers). They do not inherently combine dashboards, multiple filtered grids, and links into a consolidated activity hub.

B. Form personalization: This feature allows users to modify the layout of existing forms (e.g., hide/add fields). It does not create a new, consolidated page with dashboards and multiple distinct data grids as required.

C. Power BI dashboard: While Power BI provides powerful analytics and can be embedded in Dynamics 365, a Workspace is the native Dynamics 365 feature specifically designed to be the central hub for a user's daily activities, incorporating lists, links, and analytics.

E. Electronic reporting: This framework is used for configuring and generating electronic documents and reports (e.g., regulatory filings, payment files). It is not a user interface feature for daily task management.

---

1. Microsoft Learn. (2023). Workspaces. In Dynamics 365 Finance documentation. "Workspaces are activity-oriented pages that provide an overview of an activity... A workspace can include tiles that show key data, lists of data that require attention, and links to frequently used pages." This directly supports the use of workspaces for consolidating metrics, lists (grids), and navigation.

Reference: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/workspaces

2. Microsoft Learn. (2023). Customer credit and collections workspace. In Dynamics 365 Finance documentation. This document details the specific workspace for the role mentioned in the question, showing its components: "The Customer credit and collections workspace lists customer information... You can view aging information... You can also view specific lists of transactions that are focused on collections." This confirms a workspace is the correct feature for this scenario.

Reference: https://learn.microsoft.com/en-us/dynamics365/finance/accounts-receivable/customer-credit-collections-workspace

3. Microsoft Learn. (2023). Personalize the user experience. In Dynamics 365 Finance documentation. "Personalization is typically used to show or hide columns on a grid or fields on a page." This reference clarifies that personalization modifies existing forms rather than creating the multi-component hub described in the question.

Reference: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/personalize-user-experience

In Dynamics 365 Supply Chain Management, Security roles are the fundamental containers used to grant users the "ability" or permission to perform specific business tasks, such as processing receipts or shipments. To satisfy the requirement of preventing a single user from completing a full end-to-end process, Segregation of duties (SoD) rules are required. These rules allow administrators to define specific duties as "conflicting." When an administrator attempts to assign a role or permission that would grant a user access to both sides of a sensitive process (like issuing credits while also handling returns), the SoD rule identifies the conflict and prevents or flags the assignment.

Microsoft Learn: Security architecture – Defines how security roles, duties, and privileges grant functional access within the system.

Microsoft Learn: Identify and resolve conflicts in segregation of duties – Explains the use of SoD rules to prevent a single user from having permissions to perform conflicting business actions.

Microsoft Dynamics 365 Documentation: Set up segregation of duties – Detail on creating rules to validate user role assignments against internal control policies.

Standard ERP Control Frameworks (e.g., NIST SP 800-53): Access Control (AC-5) – Provides the theoretical basis for "Separation of Duties" implemented in enterprise software to mitigate risk.

To define a gap in a loyalty process (or any business process) within Dynamics 365, you first need a baseline. Global libraries in LCS contain the standard industry-standard business processes provided by Microsoft. By copying from a Global library to your project's "My libraries," you establish the "To-Be" or "As-Is" framework.

Once the library is copied, the act of identifying a functional deficiency (a gap) requires you to Create a business process entry or node within the Business Process Modeler that specifically represents the missing functionality. This allows for subsequent mapping to development requirements or manual workarounds.

Microsoft Learn: LCS Business Process Modeler (BPM) - Copying libraries. Section: "Standard and Global Libraries." [ID: d365-lcs-bpm-global-copy]

Microsoft Dynamics 365 Guidance: Implementation Guide - Process Gap Analysis. Chapter 4: Lifecycle Services, pp. 42-45.

Microsoft Tech Community: BPM Integration with Azure DevOps. Section: "Mapping Gaps to Work Items." [ID: ms-lcs-devops-integration]

To monitor deadlocks over time (per hour/day) in a production environment, Azure Data Explorer (via the LCS Environment Monitoring dashboard) is the correct tool. It allows users to run Kusto Query Language (KQL) queries against telemetry data to aggregate and visualize database lock/deadlock trends. To analyze the time to complete an X++ method, the Trace parser is required. It captures detailed execution traces, providing a granular breakdown of call stacks and execution times for specific X++ methods and SQL statements, which is essential for identifying bottlenecks in custom code.

Microsoft Learn: Performance monitoring and analysis using Lifecycle Services (LCS). Section: "Environment monitoring - Monitoring tools." (Describes using Azure Data Explorer/Kusto for telemetry analysis including deadlocks).

Microsoft Learn: Trace parser - Overview. (Identifies the tool's primary function to analyze performance traces and time consumption of X++ methods).

Microsoft Dynamics 365 Operations Guide: Database movement operations - Troubleshooting performance. (Outlines the use of LCS SQL Insights for real-time deadlocks and Azure Data Explorer for historical trends).

Microsoft Technical Documentation: X++ programming language - Performance profiling. (Specifies Trace Parser as the standard tool for method-level performance profiling).

Trace Parser is a performance analysis tool specifically designed for Dynamics 365 Finance and Operations. It allows a solution architect to analyze trace files captured from the environment. These files contain detailed information about X++ code execution, server calls, and SQL database queries. By examining this data, an architect can analyze system usage characteristics, identify performance bottlenecks, diagnose long-running operations, and understand how different processes consume system resources. This is a fundamental activity for optimizing and maintaining the health of a Dynamics 365 solution.

A. Microsoft Excel: While Excel can be used to view and manipulate data exported from Dynamics 365, it is not the primary tool for capturing and analyzing deep system usage or performance characteristics.

C. Business Process Modeler: The Business Process Modeler (BPM) in Lifecycle Services (LCS) is a tool for documenting, reviewing, and performing fit-gap analysis on business processes. It models how a system should be used, but does not analyze actual live usage data or performance.

D. Data Management Workspace: This workspace is used for managing data entities for import, export, and integration purposes. It is not designed for analyzing system performance or user activity patterns.

1. Microsoft Learn. (2023). Trace parser. In Dynamics 365 Finance and Operations documentation. "The Trace parser is a tool that is used to analyze performance issues for finance and operations apps... You can use the Trace parser to find the root causes of performance issues."

2. Microsoft Learn. (2023). Business process modeler (BPM) in Lifecycle Services (LCS). In Dynamics 365 Finance and Operations documentation. "You can use Business process modeler (BPM) to create, view, and modify business process libraries and their flowcharts... BPM helps you align your business processes with industry-standard processes."

3. Microsoft Learn. (2023). Data management overview. In Dynamics 365 Finance and Operations documentation. "The data management framework can be used for managing data entities and data entity packages in finance and operations." This section details its use for data migration and integration, not usage analysis.

The Success by Design framework utilizes four stages: Initiate, Implement, Prepare, and Operate.

1. Initiate Stage: This stage focuses on alignment and early risk assessment. Identifying whether the implementation partner has the necessary skills and resources is a core activity of the Solution Blueprint Review, which occurs here to ensure the project starts with a viable foundation.
2. Prepare Stage: This stage involves finalizing the solution for production. The Go-live Readiness Review is the primary milestone here, specifically designed to assess if both the technical system and the business operations (staff training, support processes) are ready for the transition to a live environment.

Microsoft Learn (Official Vendor Documentation): "Success by Design for Dynamics 365" - Section: Initiate Phase and Solution Blueprint Review. This section outlines the evaluation of project team and partner readiness.

Microsoft Learn (Official Vendor Documentation): "Success by Design for Dynamics 365" - Section: Prepare Phase and Go-live Readiness Review. This documentation specifies that the assessment of system and operational readiness occurs prior to cutover.

Microsoft Dynamics 365 Implementation Guide: Chapter 3: Success by Design, Page 54, Paragraph 2 (Milestones by Phase).

Microsoft FastTrack for Dynamics 365: Success by Design Framework Overview (Document ID: MS-FT-SBD-2023).

The Performance SDK (PerfSDK) is the official Microsoft toolset designed specifically for creating and executing multi-user performance and load tests for Dynamics 365 Finance and Operations. It allows developers and testers to convert single-user process recordings, such as the completed procure-to-pay scenario, into automated, multi-user test scripts. These scripts can then be run from a Visual Studio test project to simulate a realistic user load on the environment, which directly addresses the requirement to complete a multi-user load test to validate performance against stakeholder expectations.

A. Microsoft Azure DevOps: Azure DevOps is used to orchestrate and run the tests created by the PerfSDK via build/release pipelines, but it is not the tool used to create the test scripts themselves.

B. Microsoft Dynamics Lifecycle Services: LCS is the administration and management portal for Dynamics 365 environments. It is used for deployment and monitoring, not for creating or executing performance tests.

D. Visual Studio: While the PerfSDK requires Visual Studio to create and run the test projects, Visual Studio by itself is a general-purpose IDE. The PerfSDK is the specific toolkit that provides the necessary templates and libraries for Dynamics 365 load testing.

---

1. Microsoft Learn. (2023). Performance SDK and user acceptance testing. In Dynamics 365 Finance. "The Performance software development kit (SDK) for Microsoft Dynamics 365 Finance and Operations is a tool that is used to help you do performance testing. The Performance SDK lets you create, maintain, and run performance tests."

2. Microsoft Learn. (2023). Create and run performance tests. In Dynamics 365 Finance. This document outlines the process: "After you record a business process by using Task recorder and save the recording as a developer recording file, you can add the file to a performance test project in Microsoft Visual Studio and then run a multi-user performance test." This confirms the use of PerfSDK within Visual Studio.

3. Microsoft Learn. (2023). Test strategy. In Dynamics 365 Implementation Guide. Under the "Performance testing" section, it states, "The Performance SDK (PerfSDK) is the official tool for performance testing in finance and operations apps. It helps you simulate a realistic user load and measure the performance of your system."

Creating a formal Master Data Management (MDM) team (B) delivers the governance needed to define one authoritative item-creation process and to police it so that no other method is used after go-live.

Loading the item master during the cut-over migration but before the next scheduled annual update (C) ensures that the forthcoming update is performed inside Dynamics 365 with the newly enforced standards, eliminating duplicate work in the legacy system and preventing inconsistent item definitions from being carried over.

A – Migrating after the annual update forces the update to be performed twice (legacy and D365) and carries forward non-standard practices.

D – Semantic duplicate of B; only one MDM-team recommendation is required.

E – Migrating items “as-is” moves existing inconsistencies into the new system, violating the requirement to standardize and control future item creation.

1. Microsoft Learn, “Plan a data migration strategy and process” – section “Perform the cut-over migration,” paragraphs 2-3 (https://learn.microsoft.com/en-us/training/modules/plan-data-migration/).

2. Microsoft FastTrack for Dynamics 365, “Data Migration Guidance v3,” pp. 8-10 – recommends loading master data before business events to avoid re-work.

3. Microsoft Learn, “Master data management in Dynamics 365 Finance and Operations apps,” section “Governance and ownership,” para 1-2 (https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/master-data-management).

4. R. Bose, X. Luo, “Integrative framework for assessing MDM implementation,” Journal of Database Mgmt, 29(1):1-22, 2018, DOI:10.4018/JDM.2018010101 – details necessity of formal MDM team for data-creation control.

5. MIT OpenCourseWare, “Database Systems – Lecture 24: Data Governance,” slide 9 – outlines the role of MDM in standardizing key master data entities.

Microsoft Lifecycle Services (LCS) is the cloud-based collaboration portal that provides the tools and services to manage the application lifecycle of Dynamics 365 finance and operations apps, including upgrades from Dynamics AX 2012. The Performance Benchmark Software Development Toolkit (SDK) is an official tool provided by Microsoft specifically for performance testing. It is distributed through the Shared asset library within an LCS project. This allows customers and partners to download the toolkit to establish a performance baseline in their source AX 2012 environment before migrating to the cloud, ensuring performance targets are met post-upgrade.

B. Azure DevOps Services: This platform is for source code management, project tracking, and CI/CD pipelines, not for downloading official Microsoft application lifecycle tools like the Performance SDK.

C. Microsoft PartnerSource: This is a legacy portal for partners. While it historically contained downloads, the current and official distribution channel for lifecycle management tools is LCS.

D. Microsoft AppSource: This is a marketplace for third-party business applications and extensions for Microsoft cloud services, not a repository for development and benchmarking toolkits from Microsoft.

E. Microsoft Developer Network (MSDN): While a historical source for developer tools, MSDN has been largely superseded by other platforms. LCS is the specific, dedicated portal for Dynamics 365 tools.

1. Microsoft Learn. (2023). Performance SDK and benchmarking tools. "The Performance SDK is available for download from the Shared asset library in Microsoft Dynamics Lifecycle Services (LCS)." Link

2. Microsoft Learn. (2023). Lifecycle Services (LCS) for finance and operations apps customers. "Lifecycle Services (LCS) is a collaboration portal that provides an environment and a set of regularly updated services that can help you manage the application lifecycle of your finance and operations apps." Link

3. Microsoft Learn. (2023). Upgrade from AX 2012 - Pre-upgrade checklist for data upgrade. Section: "Performance". "Before you upgrade, you should use the Performance SDK to benchmark your AX 2012 environment." This confirms the tool's role in the upgrade process managed via LCS. Link

The most appropriate organizational structure for a holding company with independently managed and operated subsidiaries that require strict data segregation is separate legal entities. In Dynamics 365 Finance, a legal entity is the primary organizational unit that provides a security boundary. Data is partitioned by company, meaning transactions and master data for one legal entity are inherently isolated from others. This structure directly reflects the real-world legal and operational independence of the subsidiaries, ensuring data integrity and restricted access by default, which is the core requirement of the scenario.

A. A single legal entity with security policies is not the standard or recommended approach for legally distinct companies, as it introduces significant complexity and risk of misconfiguration.

C. A financial dimension is a tool for reporting and analysis, not a mechanism for enforcing data security or partitioning data between legally separate subsidiaries.

D. A consolidation entity is a specialized company used for aggregating financial results from multiple source legal entities; it is not the primary operational structure.

E. The default business unit financial dimension is used for operational reporting within a single legal entity and does not provide the required data isolation between companies.

1. Microsoft Learn. "Organizations and organizational hierarchies." Dynamics 365 Fin & Ops Core Docs. Accessed May 20, 2024. In the "Legal entities" section, it states, "A legal entity is an organization that has a registered or legislated legal structure... Data for legal entities is secured by company, and only people who are authorized to access a company can see the data for it." This directly supports the use of separate legal entities for data restriction.

2. Microsoft Learn. "Plan your organizational hierarchy." Dynamics 365 Fin & Ops Core Docs. Accessed May 20, 2024. Under the "Legal entities" section, the guidance is to "Create a legal entity for each organization in your business that is a registered legal company." This aligns with the scenario of three independent subsidiaries.

3. Microsoft Learn. "Financial dimensions." Dynamics 365 Finance Docs. Accessed May 20, 2024. This document explains that financial dimensions are used to "categorize transactions for reporting." It does not describe them as a tool for data security, which invalidates options C and E.

4. Microsoft Learn. "Extensible data security policies." Dynamics 365 Fin & Ops Core Docs. Accessed May 20, 2024. This documentation describes Extensible Data Security (XDS) as a framework for securing data within an organization. While powerful, it is not the primary or most efficient method for separating legally distinct companies, which is the intended purpose of the legal entity structure itself. This makes option A a less suitable choice than B.