Free PL-400 Exam Braindumps (page: 13)

Page 12 of 89

HOTSPOT (Drag and Drop is not supported)
You are designing an integration between Dataverse and an external application. The external application processes thousands of records per day.
Record processing volumes vary throughout the day. Extremely high processing volumes may occur and may exceed the Dataverse service protection API limits.
You need to implement each service protection limit that is enforced.
Which implementations should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



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



You are deploying a Power Apps app that uses the custom connector for ServiceNow.
The app loads very slowly for some users. You determine that all records from ServiceNow are being retrieved for every user.
The app must load only incidents that are assigned to each user.
You need to limit the number of records that the connector returns.
What should you do?

  1. Apply a Lifecycle Services asset scope
  2. Apply a business process flow
  3. Apply the Azure APIM parameter
  4. Apply a connector policy template

Answer(s): D

Explanation:

You can configure policy templates for custom connectors. Policies allow you to modify the behavior of a custom connector at runtime. You can use policies to perform data conversion, route requests, set parameter values, and more. You can configure policies directly in the custom connector API properties file before import, or you can do it from the maker portal in the custom connector designer by applying policy templates.
Common policy use cases are:
* Set query parameter - Use for handling default values, if necessary, but the maker doesn't configure one. For example, if an API required a top parameter for how many records to return by using a policy, you could set a default value to be used if the maker doesn't configure one.
Note: ServiceNow Action: GetRecords

Summary: List Records -
Description: Gets records of a certain ServiceNow object type like 'Incidents'
Syntax:ServiceNow.GetRecords (string tableType, [advanced][Optional]boolean sysparm_display_value, [advanced][Optional]boolean sysparm_exclude_reference_link, [advanced][Optional]string sysparm_query, [advanced][Optional]integer sysparm_limit, [advanced][Optional]integer sysparm_offset)


Reference:

https://docs.microsoft.com/en-us/learn/modules/policy-templates-custom-connectors/ https://www.carlosag.net/PowerApps/Connectors/ServiceNow



You are deploying a Power Apps app that uses the custom connector for ServiceNow.
The app loads very slowly for some users. You determine that all records from ServiceNow are being retrieved for every user.

The app must load only incidents that are assigned to each user. You need to limit the number of records that the connector returns. What should you do?

  1. Apply a Lifecycle Services asset scope
  2. Apply a business process flow
  3. Apply the Azure APIM parameter
  4. Apply a connector policy template

Answer(s): D

Explanation:

You can configure policy templates for custom connectors. Policies allow you to modify the behavior of a custom connector at runtime. You can use policies to perform data conversion, route requests, set parameter values, and more. You can configure policies directly in the custom connector API properties file before import, or you can do it from the maker portal in the custom connector designer by applying policy templates.

Note: ServiceNow Action: GetRecords Summary: List Records
Description: Gets records of a certain ServiceNow object type like 'Incidents' Syntax:ServiceNow.GetRecords (string tableType, [advanced][Optional]boolean sysparm_display_value, [advanced][Optional]boolean sysparm_exclude_reference_link, [advanced][Optional]string sysparm_query, [advanced][Optional]integer sysparm_limit, [advanced][Optional]integer sysparm_offset)


Reference:

https://docs.microsoft.com/en-us/learn/modules/policy-templates-custom-connectors/
https://www.carlosag.net/PowerApps/Connectors/ServiceNow



A company is developing multiple plug-ins. One of the plug-ins keeps failing.
You need to debug the plug-in.

Which three actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.

  1. Highlight the plug-in step and select Debug in the Plug-in Registration tool
  2. Copy the .pdb file into the server/bin/assembly folder
  3. Select Start Profiling in the Plug-in Registration tool
  4. Attach the debugger to the w3wp.exe process
  5. Install the plug-in profiler

Answer(s): A,C,E

Explanation:

Step 1: Install plug-in profiler
Because the plug-in executes on a remote server, you cannot attach a debugger to the process. The plug-in profiler captures a profile of an executing plug-in and allows you to re-play the execution of the plug-in using Visual Studio on your local computer.

Step 2: Start profiling
1. In the Plug-in Registration tool, select the (Step) BasicPlugin.FollowupPlugin: Create of account step, and click Start Profiling.
2. In the Profiler Settings dialog accept the default settings and click OK to close the dialog.

Step 3: Debug your plug-in


Reference:

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/tutorial-debug-plug-in






Post your Comments and Discuss Microsoft PL-400 exam with other Community members:

PL-400 Discussions & Posts