Free Microsoft MB-820 Practice Exam with Questions & Answers | Set: 3

When creating a test codeunit in Microsoft Dynamics 365 Business Central to write unit test functions, the SubType property (A) of the codeunit should be set to Test. This property is crucial for defining the codeunit's purpose and behavior within the application. By setting the SubType property to Test, you are indicating that the codeunit contains test functions intended to validate the functionality of other parts of the application, such as customizations or new developments. This distinction ensures that the testing framework within Business Central recognizes the codeunit as a container for test functions, allowing it to execute these functions in a testing context, which can include setting up test data, running the tests, and cleaning up after the tests have completed.

Handler methods are used in tests to simulate user interactions, such as responding to dialogs, confirmation messages, or option selections. Since you need to simulate the user interaction of selecting a posting option (Ship, Invoice, Ship & Invoice), a Handler method would be the appropriate choice for capturing this kind of user input.

Normal attribute and Test attribute are used for marking methods for test execution, but they do not simulate user interaction, making Handler method the correct answer.

For more details, see the Microsoft Docs on Test Codeunits and Handler Methods.

Based on the PowerShell script snippet you've provided and the scenario described, you need to configure Docker sandbox environments for a company with specific requirements for Test Toolkit installations.

For SandboxA, since it is configured without the Test Toolkit installed, you would typically use the PowerShell cmdlet Install-TestToolkitToBcContainer to install the Test Toolkit into the Business Central Docker container.

For SandboxB, which must be configured from scratch with the Test Toolkit installed during configuration, you would include the Test Toolkit as part of the New-BcContainer script block that creates the container.

The relevant cmdlets and parameters for SandboxB would include:

-includeTestToolkit: This parameter ensures that the Test Toolkit is included during the creation of the new container.

Given the limited context from the image, here's how you should complete the cmdlets for SandboxB:

Add -includeTestToolkit in the New-BcContainer script to ensure the Test Toolkit is installed when creating SandboxB.

Since you are setting up SandboxB from scratch, you don't need to run Install-TestToolkitToBcContainer separately as the toolkit will be included at the time of container creation with the -includeTestToolkit parameter.

For the New-BcContainer cmdlet, you would fill in the placeholders with the appropriate values for artifactUrl, imageName, and licenseFile if they are required for your specific setup.

The telemetry trace sends custom signals to an Application Insights resource specified in the extension's app.json file and on the tenant. = YES

Dictionary keys for the extension name and version must be specified to identify the extension during analysis. = YES

The telemetry trace sends events to Application Insights resources set up on the tenant. = YES

Telemetry in Business Central allows developers to collect custom telemetry for extensions using Application Insights. The telemetry trace is used to send custom signals to an Application Insights resource. This resource is typically specified in the app.json file of the extension and must be configured on the tenant where the extension is installed.

The use of dictionary keys for the extension name and version is a best practice to identify the extension during analysis in Application Insights. These keys can be added to the telemetry trace to ensure that when the data is collected, it's clear which extension the data is associated with.

Finally, it is correct that the telemetry trace sends events to Application Insights resources that are set up on the tenant, enabling the collection and analysis of telemetry at the tenant level.

var

TempBlob: Codeunit "Temp Blob";

IncidentOutStream: OutStream;

IncidentInStream: InStream;

ImageFilter, FileName: Text;

begin

// Initialize the TempBlob and streams

TempBlob.CreateOutStream(IncidentOutStream);

Rec.Image.ExportStream(IncidentOutStream); // 'Rec' refers to the current Room Incident record

TempBlob.CreateInStream(IncidentInStream);

// Set the filters and filename for the image

ImageFilter := 'Image Files (*.bmp,*.jpg,*.jpeg,*.gif)|*.bmp;*.jpg;*.jpeg;*.gif';

FileName := 'Customer Picture';

// Prompt the user to download the image

if not DownloadFromStream(IncidentInStream, '', 'Download Incident Picture', '', ImageFilter, FileName) then

Error('Unable to download the image.');

end;