Microsoft PL-400 Practice Test - Questions Answers

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.

Incorrect Answers:

Workflow does not support run on schedule.

Power Automate does not support Azure integration. (For integration with Dynamics 365 Power Automate can be used. It also supports scheduled actions.)

Box 2: Power Automate

Scenario: Submitted customer surveys must generate an email to the correct department. Approval and follow-up must occur within a week.

Power Automate has approval flows.

Incorrect Answers:

Workflow does not support Approval workflows.

Reference:

https://docs.microsoft.com/en-us/microsoft-365/community/power-automate-vs-logic-apps

https://docs.microsoft.com/en-us/power-automate/replace-workflows-with-flows

Box 1: Lookup

Fields for the doctor's name and phone number must be displayed in the customer record.

Lookup: A field that allows setting a reference to a single record of a specific type of entity.

Box 2: Calculated

Refill dates for customer prescriptions should be automatically determined and a notification should be sent to the customer.

Calculated field: Contains calculations that use fields from the current entity or related parent entities.

Box 3: Text

Field data type: Single Line of Text:

This field can contain up to 4,000 text characters. You can set the maximum length to be less than this. This field has several format options that will change the presentation of the text. These options are Email, Text, Text Area, URL, Ticker

Symbol, and Phone.

Reference:

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/types-of-fields

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.

Reference: https://docs.microsoft.com/en-us/power-platform/admin/environments-overview https://docs.microsoft.com/enus/powerapps/maker/model-driven-apps/privileges-required-customization#system-administrator-and-system- customizersecurity-roles

https://docs.microsoft.com/en-us/power-platform-release-plan/2020wave2/data-platform/common-data-serviceuser-security-role-renamed-basic-user

Box 1: Field level security

Only supervisors must be able to view phone numbers in the Accounts form.

You use field security tables to apply field-level security, which restricts field access to specified users and teams. The scope of field-level security is global, which means that it applies to all records within the organization, regardless of the business unit hierarchical level to which the record or the user belongs. Field security works in all Microsoft Dataverse clients, including the Web client, Dynamics 365 for Outlook, and Dynamics. It applies to all components, such as the Dataverse web services, reports, search, offline, filtered views, auditing, and duplicate detection.

Box 2: Team Security

Sales users must only have access to their own records.

Owner team: An owner team owns records and has security roles assigned to the team. A user's privileges can come from their individual security roles, those of the teams that they're part of or the ones they inherit. A team has full access rights on the records that the team owns. Team members are added manually to the owner team.

Box 3: Environment security

Developers must be able to create new apps for all users.

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.

Reference: https://docs.microsoft.com/en-us/powerapps/developer/data-platform/field-security-entities

https://docs.microsoft.com/en-us/power-platform/admin/database-security https://docs.microsoft.com/en-us/powerplatform/admin/manage-teams#types-of-teams

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

Pharmacy orders must be displayed in four graphs as follows:

Annual revenue over $100,000

Annual revenues under $100,000

Research facilities

Hospitals

The graphs must be interactive, and users must be able to drill down on any dimension.

A trigger must be created that changes the Priority field to 1 in the Account record 10 days after an Account record is created.

Note:

Date.AddWeeks returns the date, datetime, or datetimezone result from adding numberOfWeeks weeks to the datetime value dateTime.

CreatedOn gets the value to store in the history table indicating when this entry was created.

Reference: https://docs.microsoft.com/en-us/powerquery-m/date-addweeks https://docs.microsoft.com/en- us/dotnet/api/system.data.entity.migrations.model.inserthistoryoperation.createdon?view=entity-framework-4.3.1