- AIssue Search within Lifecycle Services
- BAsset Library within Lifecycle Services
- CEnvironment Monitoring Tool within Lifecycle Services
- DDeployment packages within Lifecycle Services
The Environment Monitoring Tool within Lifecycle Services is designed to monitor and diagnose performance issues in Dynamics 365 applications. Asset Library is used for managing assets and not for diagnosing performance issues. Issue Search is used for researching and resolving issues but not specifically for performance monitoring. Deployment packages are used for deploying changes between environments and not for performance monitoring.
Perform support tasks - Training | Microsoft Learn
Best practices for ALM in Dynamics 365 applications - Dynamics 365 | Microsoft Learn
Correct: Create event handler classes and subscribe them to the appropriate delegates.
Option A is correct because event handler classes and delegates provide a decoupled way to respond to events. Option B is incorrect as global variables do not provide a mechanism for event handling and can lead to tightly coupled code. Option C is incorrect because embedding the logic within the methods leads to tight coupling and is not a best practice for event handling. Option D is incorrect as polling is not an efficient or recommended method for event handling in this context.
The BatchHeader and BatchJob classes are specifically designed for creating and managing batch jobs in Dynamics 365 finance and operations appsfinance and operations apps. Creating a custom batch processing system or implementing batch processing manually would be unnecessary and inefficient. The SysOperation framework is not designed for batch processing.
Implement the SysOperationSandbox framework - Training | Microsoft Learn
The Regression suite automation tool (RSAT) and Task recorder are the correct tools to use as they allow functional power users to record business tasks and then convert the recordings into a suite of automated tests, without having to write source code. The SysTest framework and Acceptance Test Library (ATL) tool are used for unit and component testing, not for reducing the time and cost of UAT. The Data management framework is used for data integration testing, not for UAT.
Regression suite automation tool (RSAT) - Finance & Operations | Dynamics 365 | Microsoft Learn
Configure the testing environment and prepare data - Training | Microsoft Learn
Database logging provides a way to track specific types of changes to the tables and fields in finance and operations apps. Role-based security is used to authorize access to individual elements of the apps. Extensible Data Security (XDS) policies are used to secure data in shared tables. Segregation of duties is used to reduce the risk of fraud, enforce internal control policies, and detect errors or irregularities.
Extensible data security framework - Training | Microsoft Learn
Security capabilities for finance and operations apps - Dynamics 365 | Microsoft Learn
Wrong:
Create a unique index on the AccountReferrer field.
Wrong:
Modify the existing indexes on the FMCustomer table to include the AccountReferrer field.
Wrong:
Create a view on the FMCustomer table that includes the AccountReferrer field.
Creating a new index on the extended table that includes the new field will optimize database searches. The index should not be unique as this is intrusive and not allowed in extensions. Modifying existing indexes or creating a view does not directly optimize searches on the new field.
Write extensible tables - Finance & Operations | Dynamics 365 | Microsoft Learn
Add a table extension to a project - Training | Microsoft Learn
The correct answer is to implement the Data Integrator service with custom mappings, as it allows for seamless data integration between cloud and on-premises environments. Configuring a direct database link (Option B) is not recommended due to security and complexity concerns. A file-based data synchronization approach (Option C) is not efficient and does not support real-time integration. Setting up virtual machines in the cloud to replicate the on-premises setup (Option D) does not address the integration requirement directly and can lead to increased costs and complexity.
Differentiate cloud and on-premises architecture - Training | Microsoft Learn
Security capabilities for finance and operations apps - Dynamics 365 | Microsoft Learn
Option B is correct because set-based caching is suitable for small tables where the entire table can be cached efficiently. Option A is incorrect as single-record caching is not optimal for all tables, especially if they are not frequently accessed. Option D is incorrect because increasing the server cache size may not be efficient for large tables and could lead to disk-based searches which are slower. Option C is incorrect as disabling all caching would result in poor performance due to repeated database queries.
Identify and apply caching mechanisms - Training | Microsoft Learn
Wrong:
Management Reporter
Wrong:
Embedded BI
Wrong:
Excel Integration
SSRS Report is the correct choice because it supports both transactional and aggregate data, can be accessed internally and externally, and allows for free form design. Power BI Integration also allows for internal and external access and supports aggregate data, but it does not support transactional data. Excel Integration, Embedded BI, and Management Reporter do not meet all the requirements.
Create reporting solutions - Finance & Operations | Dynamics 365 | Microsoft Learn
Implement built-in KPIs, charts, and other reporting components - Training | Microsoft Learn
To automate tests, you should use RSAT, which significantly reduces the time and cost of user acceptance testing and it provides options for investigating test failures.
Wrong:
To apply an update on any Dynamics 365 Commerce environment, you need to access Lifecycle Services, not RSAT.
Wrong:
For writing and maintaining code, you have the development environment, for instance Visual Studio, so it’s not RSAT that enables it.