PL-400 Practice Questions

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.

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: Use a Data Integration template in Power Apps.

Ensure that the names of the pharmacies are synced between the accounting and the customer management systems.

Note: The Data Integrator (for Admins) is a point-to-point integration service used to integrate data into Dataverse. It supports integrating data between Finance and Operations apps and Dataverse. It also supports integrating data into Finance and Operations apps and Dynamics 365 Sales.

The Data Integrator (for Admins) consists of the Data Integration platform, out-of-the-box templates provided by our application teams (for example, Finance and Operations apps and Dynamics 365 Sales) and custom templates created by our customers and partners.

Box 2: Create a workflow in Dynamics 365 Sales.

Account numbers should be entered automatically into the pharmaceutical system that is in a Cerner database and kept in sync.

Note: Start When: Use the options in this section to specify when a workflow should start automatically. You can configure a real-time workflow to be run before certain events. This is a very powerful capability because the workflow can stop the action before it occurs. The options are:

Record is created

Record status changes

Record is assigned

Record fields change

Record is deleted