PL-400 Practice Questions

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.

https://docs.microsoft.com/en-us/dotnet/api/system.io.filesystemwatcher https://docs.microsoft.com/en-us/power-automate/

Box 1: Add & ribbondebug=true to the end of the application URL.

Scenario: The captions for the New and Save buttons do not render properly on the form.

You can use the an in-app tool called the Command Checker to inspect the ribbon component definitions to help us determine why the button is not rendered correctly.

To enable the Command Checker, you must append a parameter & ribbondebug=true to your D365 application URL. For example: https://yourorgname.crm.dynamics.com/main.aspx?appid=9ab590fc-d25e-ea11-a81d-000d3ac2b3e6 & ribbondebug=true

Box 2: Use the Ribbon Workbench

Adding Buttons to Ribbons

Download and install Ribbon Workbench.

Select a suitable ICON for your button.

Create a solution.

Edit the button in Ribbon Workbench.

Publish and test.

Scenario: The query for all registered users must return the data categorized by division. Queries must return only the Name and Sport fields. Queries return all fields. The query is as follows:

Box 1: GET ..$select=name, sport

Use select to return only the Name and Sport fields.

Box 2: $apply(groupby(sport ne null)

Categorize by division, that is to sports.

Box 1: Logic Apps

Scenario: Ecommerce sales orders must be integrated into Dynamics 365 Finance and then exported to Azure every night.

For integration with Dynamics 365 Logic Apps can be used. It also supports scheduled actions.

For integration with Azure use Logic Apps, instead of Power Automate.

Scenario: The company identifies the following job roles:

You must grant users the minimum permissions required to perform their job tasks.

Intern: Environment Maker

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.

Manager: System Administrator:

System Administrator: Has full permission to customize or administer the environment, including creating, modifying, and assigning security roles. Can view all data in the environment.

Sales representative: Common Data Service User

Basic User/ Common Data Service User: Read (self), Create (self), Write (self), Delete (self)

Can run an app within the environment and perform common tasks for the records that they own.