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

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.

Permission sets control access to objects (such as pages, tables, reports) in Business Central. By creating a new permission set that specifically excludes the critical table (or page) and assigning this permission set to the users in Department A, you can prevent them from accessing the page.

Option A (creating a different role center page) is incorrect because role centers control the user interface, but do not directly restrict access to specific pages or tables.

Option B and Option C (extending the base application permission set) are not the best options because extending permission sets typically involves adding permissions, not removing access. The question requires restricting access to a critical page, so simply including or excluding permission sets won't solve the issue at the table or page level.

Option D (creating an entitlement object) is not relevant here, as entitlements are used in more complex licensing scenarios or environments.

Summary:

Creating a permission set object that specifically excludes access to the critical table or page and assigning it to the users will solve the problem effectively.

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.Answer:s: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.E . Check which server the instance is installed on and replace http://localhost with the correct IP address: Since the server is on the same machine as Visual Studio Code (as specified), localhost is correct.