Microsoft MB-500 Practice Test - Questions Answers, Page 6

Box 1: Build the code in the DevOps pipeline.

Box 2: Asset library

Run the export to the Asset library in Microsoft Dynamics Lifecycle Services (LCS).

Box 3: Select Maintain and Apply updates.

eprovision the target environment If you copy a database between environments, the copied database won't be fully functional until you run the Environment reprovisioning tool to make sure that all Commerce components are up to date.

Follow these steps to run the Environment reprovisioning tool.

1. In your project's Asset Library, in the Software deployable packages section, click Import.

2. From the list of shared assets, select the Environment Reprovisioning Tool.

3. On the Environment details page for your target environment, select Maintain > Apply updates.

4. Select the Environment Reprovisioning tool that you uploaded earlier, and then select Apply to apply the package.

5. Monitor the progress of the package deployment.

Reference:

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/database/dbmovement-scenario-exportuat#back-up-to-the-asset-library

Reference:

https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/compare-files?view=azure-devops

Step 1: Add the OData v4 client code generator

Install OData Client Code Generator

Step 2: Add the custom OData service endpoints to the ODataClient list After you downloaded, installed the OData V4 Client Code Generator and restart the Visual Studio you will be able to find and add 'OData Client' item into our project.

Step 3: Generate proxy classes

Step 4: Point the MetaDataDocumentURI variable top the Dynamics 365 Finance instance

You need to set MetaDataDocumentURI, which is generated by the OData Code Generator.

Reference:

https://devblogs.microsoft.com/odata/tutorial-sample-how-to-use-odata-client-code-generator-to-generate-client-side-proxy-class/

https://www.netwoven.com/2018/05/29/how-to-create-client-side-odata-proxy-dll-for-microsoft-dynamics-365-for-finance-and-operations-ax/

Scenario: The Chief Financial Officer (CFO) requires the following reports:

A report that shows all outstanding invoices, their cash discount types including the new minimum threshold applicable, and the amount of the discount. The report must only be accessed by users who are members of the Accounts

Payable Manager role.

Box 1: DataContractAttribute DataContractAttribute – This attribute is applied to an X++ class and specifies that the class can be used as a data contract (that it should be serialized).

Box 2: DataMemberAttribute DataMemberAttribute – This attribute is applied to a parm (parameter) method on an X++ data contract class and specifies that the data member should be serialized.

Box 3: SRSReportParameterAttribute

You set the SRSReportParameterAttribute attribute to the data contract you created for the RDP class.

Reference:

https://docs.microsoft.com/en-us/dynamicsax-2012/appuser-itpro/how-to-use-a-report-data-provider-class-in-a-report

Classic data integration: Asynchronous, Classic data integration provides asynchronous and uni-directional data synchronization experience between model-driven applications in Dynamics 365 and Dynamics 365 Finance applications. It's an IT-administrator led experience and you must schedule the data sync jobs to run on a specific cadence. Classic data integration is suitable for business scenarios that involves bulk ingress/egress of data across Dynamics 365 applications.

Incorrect Answers:

B: Just-in-time inventory data required.

C: Real-time required. Not D: Bi-directional.

Note: Dual-write: Synchronous, Bi-directional.

Dual-write provides synchronous, bi-directional, near-real time experience between model-driven applications in Dynamics 365 and Finance applications. Data synchronization happens with little or no intervention and is triggered by create, update and delete actions on an entity. Dual-write is suitable for interactive business scenarios that span across Dynamics 365 applications.

Example:

In Team Explorer, right-click FMRental.xml, and select Compare with Latest Version.

Choose Compare with Latest Version to see how the changes you have made compare to the latest version of the file on your Team Foundation Server.

Choose Compare with Workspace Version to see what changes you have made to the version you checked out.

D: The diff tool of Visual Studio is very good to compare two files.

It compares, and if it is possible, displays differences between two files, files in two folders, or a shelveset and a local or a server file.

Syntax:

tf diff[erence] itemspec [/version:versionspec] [/type:filetype] [/format:format [/ignorespace] [/ignoreeol] [/ignorecase] [/recursive] [/options][/noprompt][/login:username,[password]]

Incorrect Answers:

E: vsdiffmerge is used for merging.

Reference:

https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/difference-command

This is Update and Update_RecordSet Code sample. Result of both will be same .

TestTable TestTable; //Update_Recordset update_recordset TestTable setting Name ="New Enterprises" where TestTable.Accountnum =="uS-027"; //Update ttsBegin; while select forupdate TestTable where TestTable.Accountnum =="uS-027" {

TestTable.Name ="New Enterprises";

TestTable.update(); } ttsCommit; info("OK");

Reference:

https://community.dynamics.com/ax/b/technicaltutorialsformsdynamicsax2012/posts/update-and-update-recordset-code-sample-in-ax-2012

Reference: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/integration-overview