PL-400 Online Practice Questions and Answers

Correct Answer: A

How to add JavaScript to existing button in Ribbon WorkBench.

Open Ribbon workbench and Right click on Assign button from Account form and click on Customize Button. Add Enable rule and call Javascript function.

Note: An Entity Form is a way to show a form in your Dynamics 365 Portal to allow your users to enter data.

You can use the Ribbon workbench for Dynamics 365 to add a custom button on entity form in Account with JavaScript action.

Reference:

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/customize-commands-ribbon https://docs.microsoft.com/en-us/dynamics365/customer-service/configure-link-to-conversation-model-driven-app-form

Correct Answer: D

Work with alternate keys All Microsoft Dataverse table rows have unique identifiers defined as GUIDs. These are the primary key for each table. When you need to integrate with an external data store, you might be able to add a column to the external database tables to contain a reference to the unique identifier in Dataverse. This allows you to have a local reference to link to the Dataverse row. However, sometimes you can't modify the external database. With alternate keys you can now define a column in a Dataverse table to correspond to a unique identifier (or unique combination of columns) used by the external data store. This alternate key can be used to uniquely identify a row in Dataverse in place of the primary key. You must be able to define which columns represent a unique identity for your rows. Once you identify the columns that are unique to the table, you can declare them as alternate keys through the customization user interface (UI) or in the code.

Reference: https://docs.microsoft.com/en-us/power-apps/developer/data-platform/define-alternate-keys-entity

Correct Answer: D

Configure Security Role In Dynamics 365 Business Process Flow

Here are the steps to configuring security roles for a business process flow in Dynamics 365:

Go to Setting > Security > Security Roles

Choose the security role you want to add to the business process flow of your choice;

Go to the Business Process Flows tab;

You can view the existing security roles, if any, and their associated data privileges like create, read, delete and more. From this information, you can get to know which business process flows can be used for the particular security role you

have chosen;

You can add the security privileges to the selected security role by checking on the corresponding privileges;

Then click on save and close.

Reference:

https://www.gestisoft.com/blog/configure-security-role-in-dynamics-365-business-process-flow

Correct Answer: A

Microsoft Azure solution For the Dataverse and Azure connection to work, there must be at least one solution in an Azure Service Bus solution account, where the solution contains one or more service endpoints. For a relay endpoint contract, a listener application that is “Dataverse-aware” must be actively listening on the endpoint for the Dataverse request on the Service Bus. For a queue endpoint contract, a listener doesn't have to be actively listening. A listener is made Dataverse-aware by linking it to the Microsoft.Xrm.Sdk assembly so that type RemoteExecutionContext is defined

Note Data Context The data context contains the business data that is being processed as part of the current Dataverse operation. This processing was initiated when a request to perform a certain operation was made by a user, workflow, or application, to the Dynamics 365 platform. The data context is passed to any plug-ins or custom workflow activities that are registered with the event pipeline to execute on the specific request and table combination that is currently being processed. The data context is of type IPluginExecutionContext when it is being passed along the event execution pipeline and RemoteExecutionContext when it is posted to the Service Bus.

Reference: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/azure-integration

Correct Answer: BC

Requirements. Driving record verification

1.

Driving record verification must only be performed once for each candidate.

2.

Information required for driving record verification must be sent to the driving record verification service automatically after the candidate's address is verified.

3.

The API must return a value of either Approved or Rejected to indicate whether the candidate has met the company's requirements.

Correct Answer:

Correct Answer:

Box 1: Security roles

A security role defines how different users, such as salespeople, access different types of records. To control access to data, you can modify existing security roles, create new security roles, or change which security roles are assigned to

each user. Each user can have multiple security roles.

Security role privileges are cumulative: having more than one security role gives a user every privilege available in every role.

Each security role consists of record-level privileges and task-based privileges.

Box 2: OAuth

Oauth 2.0 is the most frequently used type, which uses the Oauth 2 authentication framework to authenticate with the service. Before using this authentication type, you'll need to register your application with the service so that it can receive

access tokens for the users.

For example, Register the application in Azure AD shows how to register an application with the Azure Active Directory service.

During the connection creation process, the user will be asked to enter the credentials for login to the service. These credentials will be used by the application to get an authorization token. For every request, this authorization token will be

sent to your service through the Authorization header.

Box 3: Basic Authentication

Basic Authentication is the simplest type of authentication, where the user just has to provide the username and password to create the connection.

Note: Before using any connector in Azure Logic Apps, Microsoft Power Automate, or Microsoft Power Apps, the user needs to create a connection by authenticating to the backend service.

Authentication types

The different types of authentication that are currently supported are:

No authentication

Basic authentication

Api Key based authentication

Oauth 2.0

Reference: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/admin/security-roles-privileges https://docs.microsoft.com/en-us/connectors/custom-connectors/connection-parameters

Correct Answer:

Step 1: In the development environment, navigate to Solutions.

The only supported way of transferring customizations from one CRM organization to another has been through Solutions.

With Solution Management came the concept of Managed and Unmanaged Solutions.

Step 2: Export the solution as managed and import it in the production environment.

Managed is a way to protect your IP (Intellectual Property) with an easy concept of install and uninstall.

Step 3: Select the solution that has BusinessRule1, navigate to the appropriate entity, and delete the rule.

Reference:

https://www.inogic.com/blog/2016/01/solution-management-with-dynamics-crm-2016/

Correct Answer:

Box 1: Site Map validation

When you validate the app, the app designer canvas shows you details about the assets that are missing.

In the app designer, select Validate.

A notification bar appears and shows you whether the app has any errors or warnings. The notification bar shows warnings in cases where, for example, an entity has no forms or views, or the app doesn't contain any components. An error

might appear if a site map isn't configured for the app.

Correct Answer:

Box 1: Register the app in Azure Active Directory

Box 2: Use FetchXML queries The failure entries can be retrieved through the Get the failure details for a given Profile request. The response returns a URI to an Azure blob that contains the failure information. Each line has the following comma-separated fields (newlines added for clarity):

Entity: , RecordId: <"N/A" | guid>, NotificationTime: , ChangeType: , FailureReason:

Note: FetchXML is a proprietary XML based query language of Microsoft Dataverse used to query data using either the Web API or the Organization service. It's based on a schema that describes the capabilities of the language. The FetchXML language supports similar query capabilities as query expressions.