Exam MB-500: Microsoft Dynamics 365: Finance and Operations Apps Developer - Quiz

  • ACreate a custom batch processing system using X++ code.
  • BImplement batch processing manually by creating a new class for each batch job.
  • CUse the SysOperation framework for batch processing.
  • DUse the BatchHeader and BatchJob classes to create and manage batch jobs.
  • AUse Azure Logic Apps to replace the legacy system's functionality.
  • BCreate a custom service that acts as a bridge between the SOAP web services and Dynamics 365.
  • CIgnore the legacy system and create new data entities from scratch in Dynamics 365.
  • DDirectly modify the legacy system to support RESTful API standards.
  • AConfigure the parallel import for an entity in the Framework parameters.
  • BConfigure the parallel import for an entity in the Data sources setup.
  • CConfigure the parallel import for an entity in the Entity settings.
  • DConfigure the parallel import for an entity in the Job history cleanup.
  • ADrag the Action Pane control from the Toolbox to the form.
  • BAdd an Action Pane from the Add Items dialog in Solution Explorer.
  • CRight-click the Design node and select New > Action Pane.
  • DInsert an Action Pane by modifying the form's XML definition.
  • AIncrease the batch size to the maximum allowed to process all entities in the shortest possible time.
  • BSchedule the import job to run during off-peak hours to avoid any potential system performance impacts.
  • CDisable all dependencies checks to speed up the import process and handle any issues post-import.
  • DUse resequencing options to optimize the execution time for the full job by representing modules with execution units and feature areas with levels.
  • AUse the Build and Sync option in the Dynamics 365 menu in Visual Studio.
  • BFrom the Dynamics 365 menu in Visual Studio, select Build models, select the packages that you want to build, and then select Synchronize database on the Options tab.
  • CUse the Synchronize Database option in the SQL Server Management Studio. Manually update the SQL database schema using SQL scripts.
  • DA and B only
  • AImplement a global cache for the entire application.
  • BImplement row versioning for the tables being accessed concurrently.
  • CDecrease the number of users allowed to access the application simultaneously.
  • DIncrease the number of database connections.