MB-500 Online Practice Questions and Answers

Correct Answer:

Reference: https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/branching-strategies-with-tfvc?view=azure-devops

Correct Answer:

Correct Answer:

Reference: https://community.dynamics.com/365/financeandoperations/b/daxology/posts/runnable-class

Correct Answer:

Correct Answer:

Correct Answer:

Correct Answer:

Box 1: Yes Class extension - Method wrapping and Chain of Command. The functionality for class extension, or class augmentation, has been improved. You can now wrap logic around methods that are defined in the base class that you're augmenting. You can extend the logic of public and protected methods without having to use event handlers. When you wrap a method, you can also access public and protected methods, and variables of the base class. In this way, you can start transactions and easily manage state variables that are associated with your class.

Box 2: Yes In the following example, the wrapper around doSomething and the required use of the next keyword create a Chain of Command (CoC) for the method. CoC is a design pattern where a request is handled by a series of receivers. The pattern supports loose coupling of the sender and the receivers [ExtensionOf(classStr(BusinessLogic1))] final class BusinessLogic1_Extension {

str doSomething(int arg)

{

// Part 1

var s = next doSomething(arg + 4);

// Part 2

return s;

} }

Box 3: Yes

Instance and static methods can be wrapped by extension classes. If a static method is the target that will be wrapped, the method in the extension must be qualified by using the static keyword.

Box 4: No

Wrapper methods must always call next.

Note: Wrapper methods in an extension class must always call next, so that the next method in the chain and, finally, the original implementation are always called. This restriction helps guarantee that every method in the chain contributes to

the result.

In the current implementation of this restriction, the call to next must be in the first-level statements in the method body.

Here are some important rules:

Calls to next can't be done conditionally inside an if statement.

Calls to next can't be done in while, do-while, or for loop statements.

A next statement can't be preceded by a return statement.

Because logical expressions are optimized, calls to next can't occur in logical expressions. At runtime, the execution of the complete expression isn't guaranteed.

Reference:

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc

Correct Answer:

Box 1: Data contract class

A data contract class defines the parameters for a report that is bound to a report data provider (RDP) class. You can specify one or more groups of report parameters, the order of the groups, and the order in which the report parameters

appear in a print dialog box.

Box 2: Report data provider class

Report data provider class processes business logic based on parameters and a query, and then returns the tables as a dataset for the report.

Box 3: 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 4: 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 5: 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

Correct Answer:

Box 1: Export

Select the Import or Export (in this case) tile to create a new data project.

Box 2: Data source

Enter a valid job name, data source, and entity name.

Box 3: Data project page

O the Data project page, select Create recurring data job.

Box 4: Setup authorization policy

In the Set up authorization policy tab, enter the application ID that was generated for your application, and mark it as enabled.

Reference:

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/recurring-integrations

Correct Answer: CD

C: Customization and Extension

D: Example: Navigate to FMRental.Extension in the Tree Designer

1. In the Visual Studio, in Solution Explorer, in the FleetManagement Discounts project, expand User Interface > Form Extensions.

The FMRental.Extension element is an extension element that extends the functionality of the FMRental form by adding two new data sources and a new tab control.

2.

In Solution Explorer, double-click FMRental.Extension to open the designer.

3.

In the designer's search box, type 'e:' as shown in the image below. This filters the current designer to only show nodes that belong to the current extension.

Reference: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/customize-model-elements-extensions

Correct Answer: BCE

ER (electronic reporting) currently supports the TEXT, XML, JSON, PDF, Microsoft Word, Microsoft Excel, and OPENXML worksheet formats.

Reference: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/analytics/general-electronic-reporting

Correct Answer: B

Instead Solution: Create an extension for CalendarID.

We should extend CalendarID.

Note: There are several properties that can be customized on existing extended data types (EDTs) through extension:

You can only set the new String size to a value equal to or larger than the base EDT value. Label Help text Form help Country region codes String size

Reference: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/modify-edt

Correct Answer: A

The Query class embodies the structure of a query.

Note 1: Query class Objects of this kind are not used to fetch records from the database. Instead, use a QueryRun object that can be assigned a query object. The dynamic behavior of a query is defined by the QueryRun class. The static behavior is defined by the Query class. Queries contain one or more data sources that correspond to tables in the database. The data sources are specified by using QueryBuildDataSource objects. This class lets you create, read, update, and delete X++ code and metadata.

The following example creates a query object that is used to create a QueryRun object.

X++

{ Query q = new Query (QueryStr(Cust)); // Use the query to build a queryRun object. QueryRun qr = new QueryRun (q); // Traverse some records. while (qr.next()) {

// ... } }

Note 2:

You can create a cross-company query by using X++ code. There are two ways to do this:

crossCompany keyword on the select statement

Query class methods

Reference:

https://learn.microsoft.com/en-us/dynamicsax-2012/developer/cross-company-x-code-basics

https://learn.microsoft.com/en-us/dotnet/api/dynamics.ax.application.query

Correct Answer: A

The data entities in Dynamics 365 for Finance and Operations has 'IsPublic' property which when enabled, makes the data entity available to be consumed via OData. List of data entities exposed to Odata can be viewed using the URL [baseURL]/data, where baseURL is the URL to access Dynamics 365 Finance and Operations.

Some of the data entities do not have this 'IsPublic' property enabled out-of-the-box and therefore not exposed for OData.

Reference: https://community.dynamics.com/365/b/ocp/posts/consume-dynamics-365-finance-and-operations-data-entities-with-ispublic-no-using-odata

Correct Answer: B

Note: A sales manager suspects a data-related issue in the vendor exclusion list. User1 must identify the user who created the referenced exclusion records.

On each form in Microsoft Dynamics AX, there is a menu item Record info on the OPTIONS menu tab page.

Click on the Record info button to get the next dialog presented.

The dialog gives you also the option to show all fields or view database log records related to a certain record.

Reference: https://kaya-consulting.com/en/how-to-rename-records-in-ax7/