ExamGecko
Home Home / Microsoft / MB-820

Microsoft MB-820 Practice Test - Questions Answers

Question list
Search
Search

List of questions

Search

Related questions











You have a decimal variable named AmountlCY.

You need to round up the variable to four decimal places.

Which result value should you use?

A.

Result: = Round (AmountLCY,A. '>'}:

A.

Result: = Round (AmountLCY,A. '>'}:

Answers
B.

Result: = Round {AmountLCY. 0.0001. =');

B.

Result: = Round {AmountLCY. 0.0001. =');

Answers
C.

Result: = Round (AmountLCY. 0.0001. '<'):

C.

Result: = Round (AmountLCY. 0.0001. '<'):

Answers
D.

Result: = Round (AmountLCY, 0.0001, >');

D.

Result: = Round (AmountLCY, 0.0001, >');

Answers
Suggested answer: B

Explanation:

To round up a decimal variable to four decimal places in Microsoft Dynamics 365 Business Central, you should use the Round function with specific parameters. The correct formula is Result := Round(AmountLCY, 0.0001, '=') (B). This function rounds the AmountLCY variable to the nearest value based on the second parameter, which is 0.0001 in this case, representing four decimal places. The third parameter, '=', specifies that the function should round to the nearest value, which effectively rounds up the value when it's halfway between two possible rounded values. This approach ensures that the AmountLCY variable is accurately rounded to four decimal places, which is essential for financial calculations and reporting to maintain precision.

DRAG DROP

You are developing a test application to test the posting process of a sales order. You must provide the following implementation:

* Specify the value of post options (dialog: Ship, Invoice, Ship & Invoice) as Invoice.

* Perform calculations and values checking.

You need to complete the development of the test codeunit.

Which methods should you use? To answer, move the appropriate methods to the correct implementation. You may use each method once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.

NOTE: Each correct selection is worth one point.


Question 2
Correct answer: Question 2

HOTSPOT

A company plans to integrate tests with its build pipelines.

The company has two Docket sandbox environments: SandboxA and SandboxB.

You observe the following:

* SandboxA is configured without the Test Toolkit installed.

* SandboxB must be configured from scratch. The Test Toolkit must be installed in SandboxB during configuration.

You need to configure the sandbox environments.

How should you complete the cmdlets? To answer, select the appropriate options in the answer area.


Question 3
Correct answer: Question 3

HOTSPOT

You need to select the appropriate page types to solve the reporting requirements.

Which page types should you use? To answer, select the appropriate options in the answer area.

NOTE; Each correct selection is worth one point.


Question 4
Correct answer: Question 4

DRAG DROP

You need to handle the removal of the Description field and the Clone procedure without breaking other extensions.

Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.


Question 5
Correct answer: Question 5

You need to determine If you have unwanted incoming web service calls in your tenant during the last seven days.

Which two KQL queries should you use? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

A.


A.


Answers
B.


B.


Answers
C.


C.


Answers
D.


D.


Answers
E.


E.


Answers
Suggested answer: A, C

Explanation:

The task is to identify unwanted incoming web service calls during the last seven days. To do this, we need to look at KQL (Kusto Query Language) queries that would filter out web service calls based on the timestamp (to ensure the calls are within the last seven days) and by certain characteristics that would indicate they are unwanted, such as the wrong type of protocol (SOAP in this case, as Contoso Ltd. plans to dismiss using it).

Looking at the options:

Option A: This query selects all traces where the timestamp is within the last 7 days and where the custom dimension has a value of 'RT0008', and where the category is either 'ODataV4', 'ODataV3', or 'Api'. This query would show all API calls except SOAP, so it does not directly answer the question about unwanted calls.

Option B: This query filters for traces with a timestamp within the last 7 days, where 'RT0008' is present, and specifically looks for the category 'SOAP'. This query is correct because it directly targets SOAP calls, which are the unwanted calls according to Contoso Ltd.'s plans.

Option C: Similar to option B, this query filters for traces within the last 7 days and looks for 'RT0008' but uses the equality operator for the category 'SOAP'. This would also correctly return the unwanted SOAP calls.

Option D: This query also filters for traces within the last 7 days, but it excludes the 'ODataV4' category, which doesn't necessarily target the unwanted SOAP calls.

Option E: This query selects traces where the timestamp is within the last 7 days and the custom dimension has 'RT0008'. However, it filters out categories 'ODataV4' and 'Api', which does not directly help in identifying the unwanted SOAP calls.

Therefore, the queries that should be used to determine if there are unwanted incoming web service calls (SOAP calls) in the tenant during the last seven days are Options B and C. These queries are specific to identifying SOAP protocol usage, which is what Contoso Ltd. considers unwanted.

You need to call the Issue API action from the mobile application.

Which action should you use?

A.

POST/issues (88122e0e-5796-ec11-bb87-000d3a392eb5yMicrosoit.NAV.copy

A.

POST/issues (88122e0e-5796-ec11-bb87-000d3a392eb5yMicrosoit.NAV.copy

Answers
B.

PATCH /issues {88122 eOe-5796-ed 1 -bb87-000d3a392eb5)/Mkrosotl.NAV.Copy

B.

PATCH /issues {88122 eOe-5796-ed 1 -bb87-000d3a392eb5)/Mkrosotl.NAV.Copy

Answers
C.

POST /issues (88122e0e-5796-ec11 -bb87-000d3a392eb5)/Copy

C.

POST /issues (88122e0e-5796-ec11 -bb87-000d3a392eb5)/Copy

Answers
D.

POST /issues (88122e0e-5796-ec11 -bb87-000d3a392eb5)/copy

D.

POST /issues (88122e0e-5796-ec11 -bb87-000d3a392eb5)/copy

Answers
E.

POST/issues(88122e0e-5796-ec11-bb87-000d3a392eb5)/MicrosoftNAV.Copy

E.

POST/issues(88122e0e-5796-ec11-bb87-000d3a392eb5)/MicrosoftNAV.Copy

Answers
Suggested answer: C

Explanation:

In the context provided by the case study, when calling an API action from a mobile application, the correct format for a POST request to an action in Business Central typically involves specifying the entity (/issues), the ID of the entity (88122e0e-5796-ec11-bb87-000d3a392eb5), and the action to be called (/Copy). The action name should match the exact name as defined in the AL code, which is case-sensitive.

Option A is incorrect because it uses a non-standard format for the action call.

Option B uses the PATCH method, which is generally used for update operations, not for calling actions.

Option C is correct as it uses the POST method, which is appropriate for calling actions, and correctly specifies the entity, ID, and action name.

Option D is incorrect because the action name /copy is in lowercase, while AL is case-sensitive, and it should match the case exactly as defined in the code.

Option E incorrectly adds 'MicrosoftNAV' before the action name, which is not standard for calling actions in Business Central APIs.

Hence, the correct action to use when calling the Issue API action from the mobile application is given in Option C.

You need to determine why the extension does not appear in the tenant.

What are two possible reasons for the disappearance? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

A.

The extension was published as a DEV extension.

A.

The extension was published as a DEV extension.

Answers
B.

The extension was not compatible with the new version within 60 days of the first notification.

B.

The extension was not compatible with the new version within 60 days of the first notification.

Answers
C.

The extension was published as PTE. and the Platform parameter was not updated in the application file.

C.

The extension was published as PTE. and the Platform parameter was not updated in the application file.

Answers
D.

The extension was published as PTE. and the Platform and Runtime parameters were not updated in the application file.

D.

The extension was published as PTE. and the Platform and Runtime parameters were not updated in the application file.

Answers
E.

The extension was not compatible with the new version within 90 days of the first notification.

E.

The extension was not compatible with the new version within 90 days of the first notification.

Answers
Suggested answer: B, D

Explanation:

In the context of Microsoft Dynamics 365 Business Central, an extension may not appear in the tenant for several reasons, particularly after an upgrade to a new major version.

Option A suggests that the extension was published as a DEV extension, which typically would not cause it to disappear after an upgrade because DEV extensions are intended for development and testing within sandbox environments.

Option B indicates that the extension was not compatible with the new version within 60 days of the first notification. This is a likely reason because Microsoft enforces compatibility rules, and extensions that are not made compatible within the specified timeframe might be removed or disabled.

Option C refers to the extension being published as a PTE (Per-Tenant Extension) and mentions the Platform parameter not being updated. This could cause issues, but not specifically the disappearance of the extension after an upgrade.

Option D expands on Option C by adding that both the Platform and Runtime parameters were not updated in the application file. This is a critical aspect because if these parameters are not correctly set to indicate compatibility with the new version of Business Central, the extension could be disabled or removed.

Option E is similar to Option B but mentions a 90-day period. This option does not align with standard Business Central practices for version compatibility requirements.

Therefore, the two possible reasons for the disappearance of the extension in the tenant after an upgrade are that the extension was not compatible with the new version within the required timeframe (Option B) and that the extension was published as a PTE without the Platform and Runtime parameters being updated (Option D).

DRAG DROP

You need to configure telemetry for the SaaS tenant and test whether the ingested signals are displayed.

Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.


Question 9
Correct answer: Question 9

HOTSPOT

You need to create the API page according to the requirements.

How should you complete the code segment? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.


Question 10
Correct answer: Question 10
Total 98 questions
Go to page: of 10