Question 1

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.

Accepted Answer

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.

Question 2

HOTSPOT - (Topic 1)
You need to define the properties of the comments field of the Non-conformity page.
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.

Accepted Answer

From SurePassExam
https://www.surepassexam.com/MB-820-exam-dumps.html (113 New Questions)

Question 3

HOTSPOT - (Topic 1)
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.

Accepted Answer

For the requirements provided, the appropriate page types should be selected as follows:
? Display relevant insights in the Housekeeping Role Center: HeadlinePart
? Display the additional information for the Room table: FactBox
? Configure the first installation: StandardDialog
Comprehensive Detailed ExplanationIn the context of Microsoft Dynamics 365 Business Central, page types are crucial for determining how information is
presented to the user.
? HeadlinePart: This page type is designed to display key data and insights in a
concise and visually appealing manner, often used in Role Centers to highlight important information. It is suitable for the Housekeeping Role Center to display
relevant insights.
? FactBox: This page type is used to display supplementary information related to a
selected record in the main part of the page. It's often used to show additional details about a record in a list, card, or document page. In this scenario, it is suitable
for showing additional information about a specific Room when viewing the Room table.

From SurePassExam
https://www.surepassexam.com/MB-820-exam-dumps.html (113 New Questions)
? StandardDialog: This is a page type that provides a modal dialog for user
interaction, commonly used for setup wizards, confirmations, and input forms that require user action before proceeding. This is appropriate for configuring the first
installation, where a step-by-step guided interaction is necessary.

Question 4

HOTSPOT - (Topic 1)
You need to define the properties for the Receipt No. field in the Non-conformity table when storing the information to the purchasing department
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.

Accepted Answer

field(3; "Receipt No."; Code[20])
{
DataClassification = CustomerContent;
TableRelation = "Purch. Rcpt. Header"."No." where ("Buy-from Vendor No." = field("Vendor No."));
}
? Field Declaration:
? DataClassification:
? TableRelation Property:
? Relation Filter:
? References to AL Language:
Reference Documentation:
? AL TableRelation Property
? AL Field Syntax

Question 5

You need to access the RoomsAPI API from the canvas app. What should you do?

Accepted Answer

? API Publishing for Extensions:
? Codeunit Type:
? Why Not Other Options?
Reference Documentation:
? Publishing APIs in Extensions
? Codeunit Types in Business Central

Question 6

DRAG DROP - (Topic 2)
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.

From SurePassExam
https://www.surepassexam.com/MB-820-exam-dumps.html (113 New Questions)

Accepted Answer

In Business Central, when you need to handle the removal of fields and procedures to ensure that other extensions are not affected by these changes, you
typically follow a two-step deprecation process. This allows other developers and users to adapt to the changes before they are fully enforced. Here are the steps
to handle the removal:
? Mark as Obsolete: In the first version where the decision to remove the field or procedure is made, you set the ObsoleteState to Pending and provide an
ObsoleteReason. This doesn't remove the feature but indicates to users and developers that it will be removed in the future. This step is crucial for backward
compatibility.
? Removal: In a subsequent version, after users have had time to adapt to the deprecation warning, you can then remove the field or procedure or set the
ObsoleteState to Removed.
Based on these guidelines, here are the three actions you should perform in sequence:
? Set the Description field as ObsoleteState = Pending and ObsoleteReason = 'Not in use' in version 2.0.0.0.
? Set the Clone procedure as ObsoleteState = Pending and ObsoleteReason = 'Not in use' in version 2.0.0.0.
? Remove the Description field from the Issue table in version 2.0.0.1.
These steps will ensure that anyone using the Description field or Clone procedure will receive a warning about the pending deprecation before it is actually
removed, thereby minimizing the impact on other extensions and providing a clear path for migration.
When handling the removal of fields and procedures in Microsoft Dynamics 365 Business Central, the process should be carried out in a way that allows other
extensions or dependent features to adapt to the changes without causing immediate failures.
? Set Obsolete State and Reason for Description Field (Version 2.0.0.0): The first step involves marking the Description field as obsolete by setting the
ObsoleteState to 'Pending'. This is a non-breaking change, signaling to other developers and users that the field is planned for removal in a future version. An
ObsoleteReason should also be provided to explain why the field is being deprecated.
? Set Obsolete State and Reason for Clone Procedure (Version 2.0.0.0): Similarly, the Clone procedure should be marked as obsolete with the ObsoleteState set
to 'Pending'. This indicates that the procedure is no longer in use and will be removed in the future. Providing an ObsoleteReason is best practice as it explains the
rationale behind the decision.
? Remove the Description Field (Version 2.0.0.1): In the subsequent version, after the developers and users have been given time to adapt to the deprecation
notice, the Description field can be safely removed from the Issue table. This is considered a breaking change, hence it is done after the field has been marked as
obsolete in a previous version.
The reason for not removing the Description field and Clone procedure immediately in version 2.0.0.0 is to avoid causing runtime errors for any extensions or
integrations that may depend on these components. By following this sequence, you provide a clear deprecation path that helps maintain the stability of the overall
system while evolving the schema.

Question 7

HOTSPOT - (Topic 2)
You need to log an error in telemetry when the business process defined in the custom application developed for Contoso, Ltd fails.
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.

From SurePassExam
https://www.surepassexam.com/MB-820-exam-dumps.html (113 New Questions)

Accepted Answer

Verbosity::Critical: This ensures that the telemetry logs the failure as a critical event. DataClassification::CustomerContent: This helps classify the error as related
to customer data.
TelemetryScope::All: This ensures that the error is visible across all relevant telemetry scopes, making it easier to monitor the issue in real-time.

Question 8

You need to create the access modifier for IssueTotal. Which variable declaration should you use?

Accepted Answer

In Business Central development using AL (the language for Business Central extensions), the use of access modifiers defines how variables and procedures are
accessed within and outside of an object or codeunit.
? Access Modifiers in AL:
? Scenario Justification:
Microsoft Dynamics 365 Business Central Developer References:
? Access Modifiers in AL: Microsoft's documentation on AL provides the details on access modifiers, where it is specified that internal variables can be accessed
within the extension, and the public variable is accessible across all extensions source: Microsoft Learn on AL Programming.
? Best Practices for AL Development: Business Central development best practices suggest keeping variables internal unless they need to be accessed outside of
the current extensionsource: Microsoft Learn on AL development guidelines.

Question 9

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.

Accepted Answer

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.

Question 10

HOTSPOT - (Topic 3)
You need to define the XML file properties for the accounting department.
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.

From SurePassExam
https://www.surepassexam.com/MB-820-exam-dumps.html (113 New Questions)

Accepted Answer

From SurePassExam
https://www.surepassexam.com/MB-820-exam-dumps.html (113 New Questions)