You need to define the tables used for the non-conformity entity.
What should you use?
Answer : B
Table Structure in Business Central: When creating entities such as 'non-conformity' entities in Business Central, you use document tables to represent entities that have a header and line structure. In this case, the non-conformity entity has:
A header with common information (Non-conformity Number, Date, Vendor No., etc.).
One or more lines representing the detailed information for each non-conforming item.
Document Table Usage:
Document Table: A document table is the correct table type for scenarios where you have a header (with general information like vendor details) and lines (with detailed, item-specific information).
Document tables are typically used for entities such as Sales Orders, Purchase Orders, or any other transactional data where you have both header and line information.
Supplemental Table (Option C):
Supplemental tables are usually used to add supplementary information to existing data in Business Central. In this case, we need to store detailed line information, which is a core part of the entity rather than supplementary data, so a supplemental table would not be appropriate here.
Document History Table (Option A):
Document history tables are used to track changes and historical data for entities but are not suitable for the main introduction of the entity and its lines. This option is also not appropriate.
Reference Documentation:
Introduction to Business Central Tables
Document Tables in Business Central
You need to define the data types for the fields of the N on-conformity table.
Which two data types should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Answer : D, E
In Business Central, fields in tables are assigned specific data types that determine the kind of data they can store. For the Non-conformity table mentioned in the case study, the following data types should be used:
Date for the Non-Conformity Date field: This is because the Non-conformity Date field is required to store only the date when the non-conformity was recorded. The Date data type is appropriate for storing dates without times.
Code for the Non-Conformity Number field: The Non-conformity Number field is described to use alphanumeric values with a format that includes 'NC' and the year, like 'NC24-001'. In Business Central, the Code data type is used for fields that store alphanumeric keys. It is a text field with a limited length, which makes it suitable for number series that contain letters and numbers.
Other options are not suitable:
A . Integer for the Non-conformity Number field: This would not be appropriate because the Non-conformity Number includes alphanumeric characters and not just integers.
B . DateTime for the Non-Conformity Date field: This is not correct because there is no requirement to store the time alongside the date.
C . Char for the Non-Conformity Number field: Char data type is not typically used in Business Central for number series or identifiers. The Code data type is preferred for this purpose.
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result these questions will not appear in the review screen.
A company plans to optimize its permission sets.
The company has the following permission sets:
You need to provide the following implementation for a third permission set:
* Create a new Permission Set C that is a composite of Permission Set A and Permission Set B.
* Assign Permission Set C to a user.
You need to ensure that the user has only read access to the Job table.
Solution: Set the Included Permission Sets property to Permission Set B and the Excluded PermissionSets property to Permission Set A.
Does the solution meet the goal?
Answer : B
You are creating an entitlement object in Business Central to enable transactability for AppSource apps.
You must map the entitlement object to a plan in Partner Center.
You need to select the value of the Type property to use in the entitlement object.
Which value should you use?
Answer : A
In Business Central, when creating an entitlement object to enable transactability for AppSource apps and mapping it to a plan in Partner Center, the Type property of the entitlement object should be set to PerUserServicePlan (A). The PerUserServicePlan type is used to define an entitlement that is based on a service plan, which is typically how transactability features are managed for apps distributed through AppSource. This type of entitlement allows for the mapping of specific features or capabilities of the app to a service plan in Partner Center, enabling granular control over what users are entitled to use based on their subscription. The other values, such as Implicit (B), Unlicensed (C), and Role (D), are used in different contexts and do not apply to the scenario of mapping an entitlement object to a plan for AppSource apps.
A company plans to optimize its permission sets.
The company has the following permission sets:
You need to provide the following implementation for a third permission set:
* Create a new Permission Set C that is a composite of Permission Set A and Permission Set B.
* Assign Permission Set C to a user.
You need to ensure that the user has only read access to the Job table.
Solution: Set the IncludedPermissionSets property to Permission Set A and the ExcludedPermissionSets property to Permission Set B.
Does the solution meet the goal?
Answer : A
A company has an on-premises Business Central instance named TEST The instance uses Windows authorization and a developer services port of 7149 Visual Studio Code is installed on the same server.
You create a new AL project but cannot download the symbols.
The launch json file contains the following code:
You need to download the symbols.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Answer : A, B
You are working on an on-premises Business Central instance and unable to download symbols for a new AL project. The current configuration in launch.json does not allow you to download symbols, and you need to make corrections.
Key Points in the Scenario:
Instance name is TEST.
Developer services port is 7149.
Windows authentication is being used.
Correct Answers:
A . Change the server Instance parameter to TEST.
The serverInstance parameter must match the name of the Business Central instance, which is TEST in this scenario. You need to modify this to reflect the correct instance name.
B . Add the port: 7149 parameter.
Since the developer services are using port 7149, you need to specify this in the launch.json file by adding the port parameter with the value 7149.
Incorrect Options:
C . Change the name parameter to TEST: The name parameter is just a label and does not affect downloading symbols, so changing this won't help.
D . Change the authentication parameter to UserPassword: The authentication method is already set to Windows, which is valid for this scenario. Changing it to UserPassword is unnecessary unless specified by the system.
You are developing an app.
You plan to publish the app to Microsoft AppSource.
You need to assign an object range for the app.
Which object range should you use?
Answer : D
When developing an app for Microsoft AppSource, it is essential to use an object range that is specifically designated by Microsoft to avoid conflicts with other apps and the base application. The correct object range to use is:
An object range within the range of 70000000 to 74999999 that is requested from Microsoft (D): This range is reserved for AppSource apps. Developers need to request this range from Microsoft to ensure that the objects used in their extension do not conflict with those used by other extensions or by the base application. Using this reserved range helps maintain the integrity and compatibility of extensions published on AppSource.
It's important to note that the other ranges mentioned (A, B, C, and E) are not suitable for apps intended for AppSource. Ranges 50000 to 59999 and 50000 to 99999 are typically reserved for per-tenant customizations or partner solutions, not for distribution on AppSource. The standard range 1 to 49999 is reserved for the base application objects, and using an object range divided by countries (C) is not a standard practice for AppSource apps.