PL-400 Online Practice Questions and Answers

Correct Answer: B

Instead, in the JavaScript library, add Building code with Code date and Work item with Elapsed time in the dependencies tab.

Reference: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/web-resource-dependencies

Correct Answer: A

Within a solution you can define dependencies within solution components. Up until Dynamics 365 for Customer Engagement apps version 9.0 the main purpose of these dependencies was to prevent the deletion of a solution component when another solution component depended on it.

The following image shows the dependencies tab within the web resource form. Dependencies between web resources are set in the top list.

Reference: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/web-resource-dependencies

Correct Answer: C

Plug-in profiler is a solution that you can install on your environment that enables you to capture the execution context of a plug-in and then use that data to re-play the event within Visual Studio while debugging.

There are two tools available from which to run the Plug-in Profiler:

the Plug-in Registration Tool and Power Platform Tools for Visual Studio.

Reference:

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/tutorial-debug-plug-in

Correct Answer: B

The body will contain string that represents the JSON value of an instance of the RemoteExecutionContext class.

Reference: https://docs.microsoft.com/en-us/powerapps/developer/data-platform/use-webhooks

Correct Answer: C

Setting: Debug published app If you want to view the source expressions in Monitor for the published app, you need to turn on the setting to publish the expressions with the app. This setting is similar to generating a debug file in traditional development. Publishing source expressions with your app is optional. Even when this setting is off, you'll be able to see the events happening in your app, but you won't be able to map these events to specific expressions or formulas.

To enable this setting, go to File > Settings, and then turn on Debug published app.

Reference: https://docs.microsoft.com/en-us/power-apps/maker/monitor-canvasapps

Correct Answer:

Box 1: PreValidation

For the initial operation, this stage will occur before the main system operation.

This provides an opportunity to include logic to cancel the operation before the database transaction.

Box 2: PreOperation

PreOperation occurs before the main system operation and within the database transaction.

If you want to change any values for an entity included in the message, you should do it here.

Box 3: PostOperation

Occurs after the main system operation and within the database transaction.

Use this stage to modify any properties of the message before it is returned to the caller.

Incorrect Answers:

MainOperation: For internal use only except for Custom API and Custom virtual table data providers.

Reference:

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/event-framework

Correct Answer:

Correct Answer:

Box 1: one-to-many relationship

Only one (1:N) self-referential relationship per table can be set as hierarchical. In a self-referential relationship the primary table and the related table must be of the same type.

Box 2: connection

There are other less formal kinds of relationships between records that are called connections. For example, it may be useful to know if two contacts are married, or perhaps they are friends outside of work, or perhaps a contact used to work

for another account. Most businesses won't generate reports using this kind of information or require that it is entered, so it's probably not worthwhile to create entity relationships.

Box 3: one-to-many relationship

1:N (One-to-Many) - A table relationship where one table row for the Primary table can be associated to many other Related table rows because of a lookup column on the related table.

Note: The N:1 (many-to-one) relationship type exists in the user interface because the designer shows you a view grouped by tables. 1:N relationships actually exist between tables and refer to each table as either a Primary/Current table or Related table. The related table, sometimes called the child table, has a lookup column that allows storing a reference to a row from the primary table, sometimes called the parent table. A N:1 relationship is just a 1:N relationship viewed from the related table.

Box 4: many-to-many relationship

N:N (Many-to-Many) - A table relationship that depends on a special Relationship table, sometimes called an Intersect table, so that many rows of one table can be related to many rows of another table.

When viewing rows of either table in a N:N relationship you can see a list of any rows of the other table that are related to it.

Reference: https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/create-edit-entity-relationships https://docs.microsoft.com/en-us/power-apps/maker/data-platform/visualize-hierarchical-data

Correct Answer:

Step 1: In the Plug-in Registration tool, select Register New Assembly. You use the Plug-in Registration tool (PRT) to register your plug-in assemblies and steps.

Registering an assembly is the process of uploading the assembly to the Dataverse database.

Step 2: In the Plug-in Registration tool, Select Register New Step,..PreOperation PreOperation occurs before the main system operation and within the database transaction.

If you want to change any values for an entity included in the message, you should do it here.

Step 3: In the Plug-in Registration tool, Select Register New Image, change the Image type to be a PreImage, and..

If your plug-in step is registered in the PreValidation or PreOperation stages of the execution pipeline, you could use the Organization service to retrieve the current value of the property, but this is not a good practice for performance. A better

practice is to define a pre-entity image with your plug-in step registration.

Correct Answer:

Box 1: getClient

Code example:

var isCrmForMobile = (Xrm.Page.context.client.getClient() == "Mobile")

if (isCrmForMobile)

{

// Code for CRM for phones and tablets only goes here. } else {

// Code for web browser or CRM for Outlook only goes here. } if (Xrm.Page.context.client.getClient() == "Mobile" andand Xrm.Page.context.client.getFormFactor() == 3) {

// Add code that should only run in CRM for phones here } // Code for any client goes here.

Box 2: getFormFactor

Reference: https://stackoverflow.com/questions/47071328/navigating-in-the-dynamics-365-crm-app

Correct Answer:

Box 1: Yes

Problem patterns: Web-use-async

There are multiple ways to interact with the server or request resources. Common approaches that allow for synchronous communications include the following (These scenarios should be avoided.):

Usage of the XMLHttpRequest object passing in false for the value of the async parameter for the open function call

var requestXhr = new XMLHttpRequest();

// Explicitly setting the async parameter to false or supplying a variable with a value of false will force this as a synchronous call. requestXhr.open('GET', '/test/test.txt', false);

Box 2: No

=== - Strict Equality Comparison is already used in the code.

Box 3: No

No debugger statement in the code, so web-remove-debug-script (avoid including debug script in non-development environments) does not apply.

Correct Answer:

Box 1: Hides the control in the body of the form. The Client API form context (formContext) provides a reference to the form or to an item on the form, such as, a quick view control or a row in an editable grid, against which the current code is

executed.

setVisible sets a value that indicates whether the control is visible.

Box 2: Add an event handler to enable a function named TestFunction to run when the business process flow stage changes.

addOnStageChange adds a function as an event handler for the OnStageChange event so that it will be called when the business process flow stage changes.

Correct Answer:

Box 1: No

The operationID is PostMessageToConversation.

Post message in a chat or channel

Operation ID:

PostMessageToConversation

This operation posts a message to a chat or a channel.

Box 2: No

Status Code 404 is Resource Not Found.

Box 3: Yes

Reference:

https://docs.microsoft.com/en-us/connectors/teams/

Correct Answer:

Box 1: Lookup

Fields for the doctor's name and phone number must be displayed in the customer record.

Lookup: A field that allows setting a reference to a single record of a specific type of entity.

Box 2: Calculated

Refill dates for customer prescriptions should be automatically determined and a notification should be sent to the customer.

Calculated field: Contains calculations that use fields from the current entity or related parent entities.

Box 3: Text

Field data type: Single Line of Text:

This field can contain up to 4,000 text characters. You can set the maximum length to be less than this. This field has several format options that will change the presentation of the text. These options are Email, Text, Text Area, URL, Ticker

Symbol, and Phone.

Reference:

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/types-of-fields

Correct Answer:

Box 1: Field level security

Only supervisors must be able to view phone numbers in the Accounts form.

You use field security tables to apply field-level security, which restricts field access to specified users and teams. The scope of field-level security is global, which means that it applies to all records within the organization, regardless of the

business unit hierarchical level to which the record or the user belongs. Field security works in all Microsoft Dataverse clients, including the Web client, Dynamics 365 for Outlook, and Dynamics. It applies to all components, such as the

Dataverse web services, reports, search, offline, filtered views, auditing, and duplicate detection.

Box 2: Team Security

Sales users must only have access to their own records.

Owner team: An owner team owns records and has security roles assigned to the team. A user's privileges can come from their individual security roles, those of the teams that they're part of or the ones they inherit. A team has full access

rights on the records that the team owns. Team members are added manually to the owner team.

Box 3: Environment security

Developers must be able to create new apps for all users.

Environment maker: Can create new resources associated with an environment, including apps, connections, custom APIs, gateways, and flows using Microsoft Power Automate.

However, this role doesn't have any privileges to access data within an environment.