PL-400 Practice Exam Questions and Answers

Box 1: Microsoft flow

Using Microsoft Flow, you can automatically post to Slack when an event happens in Dynamics 365, enabling similar functionality that is available with the Microsoft Yammer integration with third-party collaboration tools.

Box 2: Workflow

Box 3: Business process flow

A business process flow is composed of Stages, and within each stage there are Steps to complete which are fields. In the business process flow heading, a user can see which stage they are at in the process, and which steps they need to complete before they proceed in the process.

Business process flows enable you to require users to complete certain steps before completing the process and if needed you can also allow users to jump stages.

Box 1: Yes

LoadData and SaveData combine to form a simple mechanism to store small amounts of data on a local device. By using these functions, you can add simple offline capabilities to your app.

Box 2: No

Box 3: No

Box 4: Yes

The event pipeline allows you to configure when in the event the plug-in code will execute. The event pipeline is divided into the following events and stages:

Box 1: PreValidation

Pre-event/Pre-Validation

This stage executes before anything else, even before basic validation if the triggering action is even allowed based on security. Therefore, it would be possible to trigger the plug-in code even without actually having permission to do so and great consideration must be used when writing a pre-validation plug-in. Also, execution in this stage might not be part of the database transaction.

Examples:- security checks being performed to verify the calling or logged on user has the correct permissions to perform the intended operation.

Box 2: PreOperation

Pre-event/Pre-Operation

This stage executes after validation, but before the changes has been committed to database. This is one of the most commonly used stages.

Example uses:

If and “update” plug-in should update the same record, it is best practice to use the pre-operation stage and modify the properties. That way the plug-in update is done within same DB transaction without needing additional web service update call.

Box 3: PostOperation

Plug-ins which are to execute after the main operation. Plug-ins registered in this stage are executed within the database transaction.

This stage executed after changes have been committed to database. This is one of the most used stages.

Example uses:

Most of the “Create” plugins are post-event. This allows access to the created GUID and creation of relationships to newly created record.

https://docs.microsoft.com/en-us/dotnet/api/system.io.filesystemwatcher https://docs.microsoft.com/en-us/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.