PL-400 Microsoft Power Platform Developer Question and Answers

OAuth requires an identity provider for authentication. For Dataverse, the identity provider is Azure Active Directory (AAD). To authenticate with AAD using a Microsoft work or school account, use the Azure Active Directory Authentication Libraries (ADAL) or Microsoft Authentication Library (MSAL).

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/authenticate-oauth

Box 1: Set the test environment security group to TestSG and assign test users the app security role.

PowerApps apps use role-based security for sharing. The fundamental concept in role-based security is that a security role contains privileges that define a set of actions that can be performed within the app. All app users must be assigned to one or more predefined or custom roles.

Box 2: Assign the manager the app security role.

Box 3: Set the production environment security group to TestSG

Box 4: Add all users in the department to the TestSG security group.

Box 1: No

There is a read error.

Box 2: No

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

Box 3: Yes

The System Customizer role is similar to the System Administrator role which enables non-system administrators to customize Dynamics 365. A Customizer is a user who customizes entities, attributes and relationships.

Box 4: Yes

The LookUp function finds the first record in a table that satisfies a formula. Use LookUp to find a single record that matches one or more criteria.

When you export a managed solution, it contains all the changes that have been applied for that solution into a file that you can then import into a different Dataverse environment.

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.

Box 1: Power Automate

Ensure that notifications are sent to the sales team when a lead is added by using Slack

Power Automate is a service that helps you create automated workflows between your favorite apps and services to synchronize files, get notifications, collect data, and more.

Box 2: Business rule

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

A field named Priority_Trigger must be created to trigger the Priority field.

Business rules provide a simple interface to implement and maintain fast-changing and commonly used rules.

Box 3: Business process flow

Ensure that leads have a review stage added to the sales process.

Use business process flows to define a set of steps for people to follow to take them to a desired outcome. These steps provide a visual indicator that tells people where they are in the business process.

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.

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.

Note: By combining conditions and actions, you can do any of the following with business rules:

Set column values

Clear column values

Set column requirement levels

Show or hide columns

Enable or disable columns

Validate data and show error messages

Create business recommendations based on business intelligence.

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.

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.

Answer: D QUESTION NO: 54

You need to configure that the mobile app meets the requirements for phone entries.

Which expression should you use?

A. PlainText

B. IsMatch

C. IsType

D. IsNumeric

Answer: D

When a pharmacy is added by using the mobile app, the phone number must be validated to be all digits.

Note: The IsNumeric function tests whether a value is numeric. Other kinds of values include Boolean, string, table, and record.

The return value is a Boolean true or false.

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

DIFFINDAYS (date and time, date and time): Returns the difference in days between two Date and Time fields. If both dates and times fall on the same day, the difference is zero.

Note: Whenever we talk about history, the bone of contention are the below four fields:

CreatedOn

ModifiedOn

CreatedBy

ModifiedBy

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.

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

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.

Scenario: CustomerC requested additional information from the parts department through the customer survey and has not received a response one week later.

Imagine having a process where you want to give someone a couple of days to reply to an approval. If that someone doesn't respond in time, you want to assign a new approval to another person or group of people. To achieve this you can set the timeout in the action settings.

Scenario: Warehouse counting is performed manually by using a counting journal. All warehouse boxes and items are barcoded.

Box 1: Common Data Service User

UserA must be able to create and publish PowerApps apps.

Common Data Service directly against your core business data already used within Dynamics 365 without the need for integration.

Build Apps against your Dynamics 365 Data

Manage reusable Business logic and rules

Reusable skills across Dynamics 365 and Power Apps

Box 2: Environment Maker

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

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

Box 3: System Administrator

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

System Administrator is the highest level role which encompasses all the privileges and has over-riding rights. The System Administrator has the authority to allow and remove access of other users and define the extent of their rights. For example, the System Administrator and the System Customizer are given access to custom entities by default while all other users need to be given access. This is the only role that cannot be edited.

Box 4: System Customizer

End users must have minimum access to the required systems.

Sales users must only have access to their own records.

The System Customizer role is similar to the System Administrator role which enables non-system administrators to customize Dynamics 365. A Customizer is a user who customizes entities, attributes and relationships.

Scenario: The Adventure Works Cycles retail location performs bicycle inspections and performance tune-ups. Technicians use paper forms to document the bicycle inspection performed before a tune-up and any additional work performed on the bicycle.

Scenario:

Qualified leads must be collected from local bike fairs.

Adventure Works Cycles uses a Power Apps app for local bike fairs to attract new customers.

By using a Dynamics 365 connector, you can create flows that initiate when an event occurs in Dynamics 365,

or some other service, which then performs an action in Dynamics 365, or some other service.

In Power Automate, you can set up automated workflows between your favorite apps and services to

synchronize files, get notifications, collect data, and more.

User5 receives the error message: ‘Endpoint unavailable’ during a test of the technician dispatch ISV solution.

When you choose to use a synchronous execution mode any failure will be reported back to the user of the application with an Endpoint unavailable error dialog informing the user that the webhook service endpoint may be configured incorrectly or is not available.

Scenario: CustomerC requested additional information from the parts department through the customer survey and has not received a response one week later.

Scenario: Warehouse counting is performed manually by using a counting journal. All warehouse boxes and items are barcoded.

Barcode scanner control for canvas apps: Scans barcodes, QR codes, and data-matrix codes on an Android or iOS device.

Description

The control opens a native scanner on an Android or iOS device. The scanner automatically detects a barcode, a QR code, or a data-matrix code when in view.

Scenario: Customer satisfaction surveys are recorded with Microsoft Forms Pro.

Box 1: Flip switch

The flip switch is like an on/off switch, providing a choice between two values.

Box 2: Linear gauge

The linear gauge lets your users input numerical values by dragging a slider instead of typing in the exact quantity. The slider provides whole number input and display only. Use this control for any numerical and money columns.

Box 3: Option set

The choice control presents a set of options for your users to choose from when entering data.

You can customize forms (main, quick create, and quick view) and email templates by adding multi-select columns that are called Choices. When you add a choices column, you can specify multiple values that will be available for users to select. When users fill out the form they can select one, multiple, or all the values displayed in a drop-down list.

Scenario: User2 reports that Azure consumption for API calls has increased significantly to 100 calls per minute in the last month.

Example:

In the following example, the rate limit of 10 calls per 60 seconds is keyed by the caller IP address. After each

policy execution, the remaining calls allowed in the time period are stored in the variable remainingCallsPerIP.

renewal-period="60"

increment-condition="@(context.Response.StatusCode == 200)"

counter-key="@(context.Request.IpAddress)"

remaining-calls-variable-name="remainingCallsPerIP"/>

Note: The rate-limit-by-key policy prevents API usage spikes on a per key basis by limiting the call rate to a

specified number per a specified time period. The key can have an arbitrary string value and is typically

provided using a policy expression. Optional increment condition can be added to specify which requests

should be counted towards the limit. When this call rate is exceeded, the caller receives a 429 Too Many

Requests response status code.

Scenario:

Customers report that the response time from the information email listed on the Adventure Works Cycles website is greater than five days.

Microsoft Teams is used for all collaboration.

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.

Box 1: Flip switch

The Field Type to use Flip Switch would be ‘Two options’.

If you go by UI perspective, Flip switch control- Yes/No (Boolean) options would give the nice field look in the web, mobile app and Tablet. Instead of using check boxes and radio buttons, this control adds a visual effect like the On/Off switch way.

Box 2: Linear gauge

Box 3: Option Set

Option sets are the ideal choice for offering users a list of defined options for a field selection.

Scenario: User1 reports that performance is slow when viewing total billed customer time.

A plug-in for Dynamics 365 Sales automatically calculates the total billed time from all activities on a particular customer account, including sales representatives' visits, phone calls, email correspondence, and repair time compared with hours spent.

CustomerB reports that the check-in app returned only one search result for their last name, which is not the correct name.

The Filter function finds records in a table that satisfy a formula. Use Filter to find a set of records that match one or more criteria and to discard those that don't.

The LookUp function finds the first record in a table that satisfies a formula. Use LookUp to find a single record that matches one or more criteria.

The Search function finds records in a table that contain a string in one of their columns.

By using a Dynamics 365 connector, you can create flows that initiate when an event occurs in Dynamics 365, or some other service, which then performs an action in Dynamics 365, or some other service.

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/xrm-webapi/updaterecord

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.

Scenario:

Weight: Set visibility action to No.

Age: Set Business Required action to Business required

Height: Set visibility action to No.