Microsoft PL-400 Practice Test - Questions Answers, Page 19

Box 1: Hides the control in the body of the form.

The Client API form context (formContext) provides a reference to the form or to an item on the form, such as, a quick view control or a row in an editable grid, against which the current code is executed. setVisible sets a value that indicates whether the control is visible.

Box 2: Add an event handler to enable a function named TestFunction to run when the business process flow stage changes.

addOnStageChange adds a function as an event handler for the OnStageChange event so that it will be called when the business process flow stage changes.

Reference: https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/clientapi-form-context

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/formcontext-dataprocess/eventhandlers/addonstagechange

Box 1: SortByColums

The SortByColumns function can be used to sort a table based on one or more columns.

The parameter list for SortByColumns provides the names of the columns to sort by and the sort direction per column.

Sorting is performed in the order of the parameters (sorted first by the first column, then the second, and so on).

Box 2: Filter

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.

Incorrect Answers:

Lookup: 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. Search: Search function uses a single string to match instead of a formula.

Reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-sort

Box 1: Conditional access

You can limit access to users with block access by location to reduce unauthorized access. By using Conditional Access policies, you can apply the right access controls when needed to help keep your organization secure and stay out of your user's way when not needed. Conditional Access analyses signals such as user, device, and location to automate decisions and enforce organizational access policies for resources.

Box 2: DLP policy

DLP policies enforce rules for which connectors can be used together by classifying connectors as either Business or Non-

Business. If you put a connector in the Business group, it can only be used with other connectors from that group in any given app or flow. Sometimes you might want to block the usage of certain connectors altogether by classifying them as

Blocked.

Box 3: Exfiltration blocking

Email exfiltration controls for connectors

Microsoft Exchange enables admins to disable email autoforwards and autoreplies to remote domains for external recipients.

Exchange does this by using message-type headers, such as Auto Forward received from Outlook and Outlook on web clients.

Reference:

https://docs.microsoft.com/en-us/power-platform/admin/restrict-access-online-trusted-ip-rules https://docs.microsoft.com/en- us/power-platform/admin/wp-data-loss-prevention https://docs.microsoft.com/en-us/power-platform/admin/block-forwardedemail-from-power-automate

Box 1: IsBlank

The IsBlank function tests for a blank value or an empty string. The test includes empty strings to ease app creation since some data sources and controls use an empty string when there is no value present.

Box 2: IsType

The IsType function tests whether a record reference refers to a specific table type.

Box 3: AsType

The AsType function treats a record reference as a specific table type, sometimes referred to as casting. You can use the result as if it were a record of the table and again use the Record.Field notation to access all of the fields of that record. An error occurs if the reference isn't of the specific type. Box 4: AsType

Reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-isblank-isempty

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-astype-istype

Box 1: Number per user over a sliding window of time

Service protection API limits are enforced based on three facets:

The number of requests sent by a user.

The combined execution time required to process requests sent by a user. The number of concurrent requests sent by a user.

The following table describes the default service protection API limits enforced per web server:

Box 2: Combined time per user over a sliding window of time

Box 3: Fixed number per user

Reference:

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/api-limits

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

Reference: https://docs.microsoft.com/en-us/power-platform/admin/data-integrator

Box 1: IsOptimisticConcurrencyEnabled

On a multi-threaded and multi-user system like Power Apps, operations and data changes often happen in parallel. A problem arises when two or more update or delete operations on the same piece of data happen at the same time. This situation could potentially result in data loss. The optimistic concurrency feature provides the ability for your applications to detect whether a table record has changed on the server in the time between when your application retrieved the record and when it tries to update or delete that record.

Box 2: If-Match: Etag

Use If-Match and If-None-Match headers with ETag values to check whether the current version of a resource matches the one last retrieved, matches any previous version or matches no version. These comparisons form the basis of conditional operation support. Dataverse provides ETags to support conditional retrievals, optimistic concurrency, and limited upsert operations.

Reference: https://docs.microsoft.com/en-us/powerapps/developer/data-platform/optimistic-concurrency

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/webapi/perform-conditional-operations-using-web-api

https://docs.microsoft.com/en-us/power-apps/developer/data-platform/webapi/query-metadataweb-api