PL-400 Online Practice Questions and Answers

Correct Answer: B

The version number are ....

This is just a bug fix so we only update the revision number.

Note: When we create patches in Dynamics 365, the system will automatically increment the build version (you can overwrite the chosen number when you create the patch). For example, if our solution starts at 1.0.0.0, we export it to

become 1.0.0.1. We then create a patch, and the version of the patch is 1.0.1.1. If we export it now, it might become 1.0.1.2. In all cases, the build or version number has been incremented. Patches require the build or version number to

increment, but not the major or minor version.

Incorrect:

Not C: This is not a minor update.

Not D: This is not a major update.

Reference:

https://carldesouza.com/how-solution-version-numbers-work-in-the-microsoft-power-platform/

https://docs.microsoft.com/en-us/power-apps/maker/data-platform/update-solutions

Correct Answer: C

In Dynamics 365 Customer Engagement (on-premises), you use field-level security to restrict access to high business impact fields to specific users and teams. For example, you use this to enable only certain users to read or update the credit score for a customer.

Reference: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/security-dev/use-field-security-control-access-field-values

Correct Answer: A

Querying relationship metadata

Entity relationships can be queried using the RelationshipDefinitions entity set. You can use a query like the following to get the SchemaName property for every relationship.

GET [Organization URI]/api/data/v9.0/RelationshipDefinitions?$select=SchemaName

The properties available when querying this entity set are limited to those in the RelationshipMetadataBase EntityType.

Note: You can retrieve relationship metadata in the context of a given entity much in the same way that you can query attributes. The ManyToManyRelationships, ManyToOneRelationships, and OneToManyRelationships collection-valued

navigation properties can be queried just like the Attributes collection-valued navigation property.

However, entity relationships can also be queried using the RelationshipDefinitions entity set.

Reference:

https://docs.microsoft.com/en-us/power-apps/developer/data-platform/webapi/query-metadata-web-api

https://docs.microsoft.com/en-us/power-apps/developer/data-platform/webapi/reference/relationshipmetadatabase?view=dataverse-latest

Correct Answer: D

To enable Command Checker, pass ribbondebug=true as a URL parameter (ex: https://myorg.crm.dynamics.com/main.aspx?appid=c26d1c44-e7c0-4c72-9d6d-0e82768cb5bdandribbondebug=true). You’ll see two new UI features light up. The

first is a new button in the top right of the header which lets you inspect the global command bar

Next, each command bar contains a new “Command checker” button. Note that this shows up at the end of the ribbon, so you may have to click the overflow flyout.

Reference: https://powerapps.microsoft.com/en-us/blog/introducing-command-checker-for-model-app-ribbons/

Correct Answer: C

Scenario: When the account is entered into the system, extra fields must appear if the referral customer box is selected. If the box is not selected, the extra fields must not appear.

Correct Answer:

Box 1: Entity

Existing vehicle licensing data must be imported into Microsoft Dataverse and easily queried.

Virtual tables (also known as virtual entities) enable the integration of data residing in external systems by seamlessly representing that data as tables in Microsoft Dataverse, without replication of data and often without custom coding.

A virtual table is a definition of a table in the Dataverse platform without the associated physical tables for table instances created in the Dataverse database. Instead during runtime, when a table instance is required, its state is dynamically

retrieved from the associated external system.

The following data providers ship with Dataverse:

An OData v4 provider is included with the service and is installed by default. This provider supports create, read (retrieve, retrieve multiple), update and delete operations.

An Azure Cosmos DB

Box 2: Azure Storage Blob

Red light camera images must be stored in a repository for later analysis.

Use Azure Storage Blob for binary data.

Azure Blob storage stores massive amounts of unstructured object data, such as text or binary data.

Box 3: Azure Cosmos DB

Information about traffic violations must be stored and related to vehicle details.

Reference:

https://docs.microsoft.com/en-us/power-apps/developer/data-platform/virtual-entities/get-started-ve

https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction

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: Power Pages

Use a bot on the website.

Microsoft Power Pages is a secure, enterprise-grade, low-code software as a service (SaaS) platform for creating, hosting, and administering modern external-facing business websites. Whether you're a low-code maker or a professional

developer, Power Pages enables you to rapidly design, configure, and publish websites that seamlessly work across web browsers and devices.

Note: Before you can add a Power Virtual Agents bot to a Power Apps portals page, you must create a bot first.

The chatbot component is rendered using a web template called Power Virtual Agents.

Box 2: Power App

Create Bot Framework skills.

Box 3: Power Virtual Agents

Create a support request from the bot without human interaction.

When your customers need to speak with a human agent, your bot can seamlessly hand off the conversation.

Power Virtual Agents is used.

Example: Connect your bot to Omnichannel for Customer Service

1.

In Power Virtual Agents, edit your bot. In the left panel, select Manage, Agent transfers, and then select the Omnichannel tile.

2.

Select Enable.

3.

Under See the environment this bot is connected to, select the environment where you have omnichannel integration turned on.

4.

Select See how to register a new Application ID and follow the steps to find or create the app registration for Power Virtual Agents.

5.

Etc.

Reference:

https://learn.microsoft.com/en-us/power-pages/introduction https://learn.microsoft.com/en-us/power-apps/maker/portals/add-chatbot

https://learn.microsoft.com/en-us/power-virtual-agents/configuration-hand-off-omnichannel

Correct Answer:

Correct Answer:

Box 1: Yes

setNotification displays an error message for the control to indicate that data isn't valid. When this method is used, a red "X" icon appears next to the control. On Dynamics 365 mobile clients, tapping on the icon will display the message.

Syntax: formContext.getControl(arg).setNotification(message,uniqueId);

Box 2: No

Box 3: Yes

setFormNotification displays form level notifications. You can display any number of notifications and they will be displayed until they are removed using clearFormNotification.

Syntax: formContext.ui.setFormNotification(message, level, uniqueId);

Box 4: No

Reference:

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/formcontext-ui/setformnotification

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/controls/setnotification

Correct Answer:

Correct Answer:

Box 1: Yes

The CrmServiceClient.Retrieve(String, Guid, ColumnSet) method issues a retrieve request to CRM

Parameters

EntityName String

Entity name to request

Id Guid

ID of the entity to request

ColumnSet ColumnSet

ColumnSet to request

Box 2: No

The numberofemployees column is not updated.

The customersizecode is updated.

Box 3: No

The code is in C#.

In C#: When you perform comparisons with nullable types, if the value of one of the nullable types is null and the other is not, all comparisons evaluate to false except for != (not equal).

Reference:

https://learn.microsoft.com/en-us/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient.retrieve

https://stackoverflow.com/questions/15777745/how-does-comparison-operator-works-with-null-int

Correct Answer:

Box 1: Create a custom connector

A custom connector is a wrapper around a REST API (Logic Apps also supports SOAP APIs) that allows Logic Apps, Power Automate, or Power Apps to communicate with that REST or SOAP API.

Box 2: Use an AppSource connector

You can only retrieve the Customer, UnifiedActivity, and Segments entities through the Power Apps connector. Other entities are shown because the underlying connector supports them through triggers in Power Automate.

Scenario: Customer information is stored in the Accounts entity.

Box 3: Use a native application function

You must produce a report that details the number of registrations for a day and send the report as a PDF to the management team.

Reference:

https://docs.microsoft.com/en-us/connectors/custom-connectors/ https://docs.microsoft.com/en-us/dynamics365/customer-insights/audience-insights/export-power-apps

Correct Answer:

Box 1: Environment Maker

UserA must be able to create and publish Power Apps apps.

The Environment Maker role can create resources within an environment including apps,connections, custom connectors, gateways, and flows using Power Automate.

Box 2: System Administrator

UserB must be the owner of all the systems and be able to provide permissions and create all new environments.

The System Administrator has full permission to customize the system. Can view all data in the system.

Box 3: System Customizer

UserC must be able to create apps connected to the systems and update the security roles and entities.

The System Customizer has full permission to customize the system. Can only view rows for system tables that they create.

The difference between the System Administrator and System Customizer security roles is that a system administrator has read privileges on most rows in the system and can see everything. Assign the System Customizer role to someone

who needs to perform customization tasks but shouldn't see any data in the system tables.

Box 4: Common Data Service User

To stay consistent with our product rebranding effort, the security role Common Data Service User is being changed to Basic User.

The Basic User security role primarily contains Basic privileges for core entities where the user can write, update, and delete records that they created or owned.

Correct Answer:

Scenario: A text alert must be sent to employees scheduled to assist in the repair area of the retail store if the number of repair check-ins exceeds eight. Box 1: action Box 2: condition Box 3: data operation