Free Microsoft PL-400 Practice Exam with Questions & Answers | Set: 4

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.

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.

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.

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.

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

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.

Scenario: A text alert must be sent to employees scheduled to assist in the repair area of the retail store if the number of repair check-ins exceeds eight.

Box 1: action

Box 2: condition

Box 3: data operation

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.

< policies >

< inbound >

< base / >

< rate-limit-by-key calls= " 10 "

renewal-period= " 60 "

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

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

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

< /inbound >

< outbound >

< base / >

< /outbound >

< /policies >

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.

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.