Financial Management (20%): Designing financial management workflows, advanced General Ledger setup, Accounts Payable, and Accounts Receivable architectures.

Operations Management (20%): Supply Chain Management alignment, Field Service, Project Management integration, and Product Lifecycle Management (PLM) execution.

Data Management (12%): Data modeling design, robust data migration strategies, and enterprise-level data performance optimization.

Infrastructure and Security (15%): Cloud infrastructure configuration, identity and access management (IAM), and advanced environment security features.

Development and Implementation (9%): Development tool selection, Application Lifecycle Management (ALM) pipelines, and rigorous testing/quality assurance frameworks.

B. Configure DMF execution parallel threshold settings and data import/export framework parameters for multi-threading.

C. Force an SSIS package execution directly against the underlying Azure SQL database.

D. Convert the data package format from XML to Excel before execution.

E. Implement a custom OData entity with change tracking enabled.

F. Disable the staging table bypass option in the data project.

B is correct: Configuring execution thresholds allows DMF to break down massive data entity exports into multiple parallel chunks (multi-threading). This distributes the workload across available AOS instances, significantly maximizing export throughput.

C is incorrect: Direct database access or custom SSIS packages bypass the application logic and are not supported or possible in standard D365 Cloud environments without tier-one tiering architectures.

D is incorrect: Converting files to Excel actually increases overhead and processing time compared to lightweight XML or CSV formats when dealing with millions of rows.

E is incorrect: OData is a synchronous protocol designed for lightweight, real-time CRUD operations. It is completely unsuitable for high-volume historical data migrations of this scale.

F is incorrect: Disabling the staging table bypass forces the system to write data to staging tables first. This introduces extra database I/O and overhead, which degrades export performance instead of optimizing it.

B. Apply an Extensible Data Security (XDS) policy restricted by a context string or query.

C. Utilize standard Microsoft Entra ID Conditional Access policies mapped to the legal entity.

D. Set up Azure Role-Based Access Control (RBAC) at the resource group level.

E. Configure organizational hierarchies and assign security roles directly to the specific retail operating units.

F. Implement a custom security duty that overrides table-level permissions via code.

B is correct: Extensible Data Security (XDS) allows architects to enforce complex, data-level filtering based on relational logic (such as legal entities or specific tables), ensuring users only see data matching the policy constraints.

C is incorrect: Entra ID Conditional Access controls authentication behavior (e.g., MFA, IP ranges) at the tenant or app level; it cannot filter transactional data records inside D365 application tables.

D is incorrect: Azure RBAC controls access to Azure cloud infrastructure components like VMs and Storage accounts, not application-level data records inside the Dynamics runtime environment.

E is incorrect: Standard security role assignments to organizational hierarchies limit access by legal entity, but they do not dynamically filter table-level conditional records like specific vendor bank details across shared roles.

F is incorrect: Overriding table-level permissions via custom duties controls access to the entire table (Read/Update/Create), but it cannot natively handle row-level conditional filtering based on data values.

B. Implement an organization-wide vendor invoice workflow using conditional branching evaluated against the invoice amount and currency conversion.

C. Develop a custom Power Automate flow that bypasses the internal D365 workflow engine entirely.

D. Utilize the Ledger Daily Journal workflow configured with a fixed user group allocation.

E. Configure an alert rule that sends an email to the CFO every time an invoice table record changes.

F. Set up signing limits within the human resources module without linking them to the workflow framework.

B is correct: Organization-wide workflows span multiple legal entities seamlessly. By combining conditional branches with automatic currency conversions, you can elegantly route global approvals from a single framework.

C is incorrect: Bypassing the built-in D365 workflow framework for core AP processing introduces unnecessary integration complexity and loses native tracking, audit trails, and state management.

D is incorrect: The Ledger Daily Journal workflow applies to general ledger entries, not vendor invoices, which require specific Accounts Payable invoice validation pipelines.

E is incorrect: Alert rules send notifications but lack the logical capability to halt transactions, enforce official approval states, or assign structured tasks to users.

F is incorrect: Signing limits defined in HR only function properly when explicitly bound to an active workflow configuration using the signing limit provider; unlinked configurations do nothing.

This is a huge original question bank

You get support from instructors if you have questions

Each question has a detailed explanation

Mobile-compatible with the Udemy app