Microsoft MB6-894 Development, Extensions and Deployment for Microsoft Dynamics 365 for Finance and Operations Online Training
Microsoft MB6-894 Online Training
The questions for MB6-894 were last updated at Dec 20,2024.
- Exam Code: MB6-894
- Exam Name: Development, Extensions and Deployment for Microsoft Dynamics 365 for Finance and Operations
- Certification Provider: Microsoft
- Latest update: Dec 20,2024
You are a developer for an Independent Software Vendor (ISV).
You need to create new extended data types in Microsoft Dynamics 365 for Finance and Operations.
What are two best practices for extending a series of data types? Each correct answer presents a complete solution.
- A . An EDT should be created for each atomic entity being utilized.
- B . Subtypes are not required for EDTs that do not contain any property changes.
- C . You cannot extend the recID or tableID system data types.
- D . You cannot use EDTs if one of them is a member of the parent extended data.
AB
Explanation:
Whenever possible, you will want to use EDTs and EDTs should be created for each atomic entity in the situation that your application is modeling. You should only create subtypes when they are needed. In other words, when you are creating an EDT that extends another EDT, but you aren’t changing any of its properties, you probably do not need to create a new subtype.
You need to add indexes to a table.
Which two best practices should you follow? Each correct answer presents part of the solution.
- A . Determine how the table should be organized by specifying a clustered index.
- B . Specify a primary index to determine the unique key on the table.
- C . Maintain indexes by making changes directly in the database.
- D . Add as many indexes as possible, since more indexes will lead to better performance.
AB
Explanation:
You’ll always maintain indexes in a development environment using the table designer versus making changes directly in the database.
You’ll always specify a clustered index to determine how the table should be organized.
You should always specify a primary index to determine the unique key on the table.
You should only add the index if the speed improvements gained are greater than the cost to update the index.
To maintain efficiency of the index, you should limit the number of columns that you use in the index.
It’s important to not create duplicate indexes.
You are an Independent Software Vendor (ISV) developer working in the "ABCModule" module in an existing solution.
You create a new label in the XYZ-en-US.label.txt file with a Label ID of "LabelText", a Label of "Text for the Label", and a Description of "ABC".
How should you reference this new label in the Label property of an artifact?
- A . @ABCModule.XYZ.LabelText
- B . @XYZ:LabelText
- C . @ABCModule.XYZ[LabelText]
- D . @XYZ[LabelText]
You are an Independent Software Vendor (ISV) developer.
You are working on a new solution that will support multiple languages and regions, and you need to use labels.
Which two best practices should you follow when using the labels? Each correct answer presents a complete solution.
- A . Use descriptive text for the label file ID.
- B . Use labels for elements and artifacts.
- C . Use the name of the model for of the label file name.
- D . Use a new label ID for every element or artifact.
BC
Explanation:
You should use labels for every user-facing element or artifact in Dynamics 365 for Finance and
Operations.
For multi-language label files, you should ensure that labels contain appropriate translations of the activity or item that they describe.
You should also use labels when programming for all external strings.
You should create a label file with the same name as the associated model.
You are an Independent Software Vendor (ISV) developer working on a new solution, and you need to use a custom icon.
What should you create to add this icon to the solution?
- A . a reference to the icon in the project
- B . an Image folder, and then add the icon
- C . a tile item in the model
- D . a resource item in the model
D
Explanation:
Resources enable management of the pictures, icons, and other visual representations for elements that are used within the user interface.
You need to explain to a team member the difference between TempDB and InMemory table types.
In which three ways do TempDB table types differ from InMemory table types for reporting? Each correct answer presents part of the solution.
- A . TempDB tables have a persistent database schema, and the data is deleted when the table goes out of scope.
- B . TempDB tables are created and destroyed upon use, which not take any database schema space.
- C . TempDB tables are for the storage of large data sets and do not allow exchanging between RAM and
disk space. - D . TempDB tables are used for small data sets that are under 128 KB in size.
- E . TempDB tables are used when you are unsure of the size of the data set returned.
ACE
Explanation:
Temp DB tables have a persistent schema in the database, but they are configured to delete table data when references to the table go out of scope.
An important thing to remember about in-memory tables is that once the table size exceeds 128 kilobytes, the system begins to allocate additional space between the RAM and disk space, which can cause performance to suffer. Because of this, it is recommended to use temp DB tables to handle larger temporary datasets.
Temp DB tables are often used to store data from reports, as report data is usually temporary and that it is not needed after the report is closed.
You are a developer for an Independent Software Vendor (ISV) and will be working with the X++ programming language and Microsoft Dynamics 365 for Finance and Operations.
Which three primitive data types will you use in this situation? Each correct answer presents a complete solution.
- A . Float
- B . Real
- C . Short
- D . AnyType
- E . Boolean
BDE
Explanation:
Anytype C A placeholder for any data type.
Booleans C Can only contain the values false and true.
Dates C Contains day, month, and year.
Enums C An abbreviation for enumerated text C a set of literals.
GUIDs C A globally unique identifier.
Integers C A number without a decimal point. To declare an integer, use the keyword int.
Reals C Numbers with a decimal point; also called decimals.
Strings C A number of characters. To declare a string, use the keyword str.
TimeOfDay C Contains hours, minutes, and seconds. To declare a time, use the system type timeOfDay.
utcdatetime C Contains year, month, day, hour, minute and second.
You are adding a relationship to a table.
Which two best practices should you follow? Each correct answer presents part of the solution.
- A . Define a navigational relationship; the validate property on the relation should be set to "Yes" for easier
navigation. - B . Set the validate property to No when you are using navigational relationships so that the application is
easy to navigate. - C . Name the relationship with an "_rel" suffix in order to differentiate it from the index that is appended with "_idx".
- D . Define the relationship to a foreign key on the child table by setting the validate property on the relation
to Yes.
BD
Explanation:
Name
The name of a relation should be postfixed with the name of the table it relates to. For example,
CustBankAccounts could be a relation on the BankAccounts table.
If there is only one relation for a table, you can just use the table name for the relation instead.
Relations in the Data Model
A relation should be defined on the table that is holding the foreign key to the relating table. The Validate
property must be set to Yes.
The system guarantees that data entered in the database fulfills the specified relations.
The Self Relation
If a table has a key, the key must be defined by using relations. Such a relation is called the ‘self relation’.
The self relation should not be set up in situations where the fields in the key are all foreign keys (such as
relations to other tables) – or more specifically, where the last field in the self relation is a foreign key.
Navigational Relations
Navigational relations are definitions of relations that exist among data in tables where there are no integrity constraints.
Defining a navigational relation benefits the system’s Auto Join system when one form is opened from within another form.
Define navigational relations to make it easy to navigate in the application by using related information.
A navigational relation has the Validate property set to No.
The Auto Join system uses relations that are defined at both the involved tables, which means that you only have to define a navigational relation on the one table to the other to make the Auto Join system work both ways.
Configuration Keys
The configuration key that is specified for the field in a relation must be the same key, or in the same tree
of keys, as the key used for the related field. If the external field in a relationship can be removed, due to
configuration key settings, and the field on which the relation is set is not also removed, you will get a best practices warning.
You are extending primitive data types to make your code more readable, and you need to assign
Extended Data Types (EDT) properties.
Which best practice should you follow?
- A . Do not leave the display length and style an Auto.
- B . Ensure that the HelpText property is the same as the label.
- C . Do not use labels for user interface text.
- D . Ensure that you reference an EDT when creating table fields.
D
Explanation:
Wherever possible, you should avoid the creation of table fields which don’t reference an EDT, as this
makes potential future changes more difficult to implement.
A team member who is not familiar with IntelliMorph needs to understand what field groups are and the primary advantage of using them.
What should you tell the team member?
- A . They are groups of fields referenced directly on forms and reports; however, you need to update ans
refresh the filed groups on the forms or reports if there are additions or deletions from the table. - B . They are groupings of fields by data type; field groups allow for the update or data by using indexes to
quickly access key columns and rows. - C . They are groupings of fields on the table; they are used for speeding up the entity of information based
on the form for which they are designed. - D . They are groupings of physical database fields by logical choice; field groups can be referenced directly on forms and reports, and, upon modification, related references are automatically updated.
D
Explanation:
Field groups: These are logical groupings of physical database fields. So field groups can be referenced directly on forms and reports so that when a modification is made to a field group, related references are automatically updated to reference the new content of the group.