All Braindump2go PDF Dumps and VCE Dumps

Braindump2go Latest and Hottest Dumps with PDF and VCE are free Shared Here!

MicrosoftPL-400 Exam DumpsPL-400 Exam QuestionsPL-400 PDF DumpsPL-400 VCE Dumps

[2026-January-New]Braindump2go PL-400 Dumps VCE Free Share[Q235-Q260]

admin

2026/January Latest Braindump2go PL-400 Exam Dumps with PDF and VCE Free Updated Today! Following are some new Braindump2go PL-400 Real Exam Questions!

QUESTION 235
You create a form in a model-driven app that uses data from the Lead table in a Microsoft Dataverse instance. You add a business rule to the Lead table. The business rule displays an error if the email address is null. You set the scope for the business rule to All Forms.
You configure a Power Apps portal by using the same Microsoft Dataverse instance. You create a web page by using the Lead form.
You need to ensure the same logic is applied on the Power Apps portal page.
What are two possible ways to achieve the goal? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.

A. Deactivate the business rule. Change the scope for the rule to Table and then reactivate the rule.
B. Replace the business rule logic with a Microsoft Power Automate cloud flow by using the Dataverse When a row is added, modified or deleted trigger.
C. Extend the webFormClientValidate JavaScript function to replace the business rule logic. Edit the code in Power Apps Studio. Add the function in a <script> block.
D. Create a JavaScript web resource and replace the business rule with a JavaScript function. Add an OnSave event handler to the Lead form.

Answer: AC
Explanation:
https://docs.microsoft.com/en-us/power-apps/maker/portals/configure/add-custom-javascript

QUESTION 236
You are developing a Power Apps app to manage records in the Account table in Microsoft Dataverse.
You must configure a Web API request to retrieve changes from the table.
You need to configure the preference header for the API request.
What should you include in the request header?

A. odata.context
B. odata.deltaLink
C. odata.track-changes
D. odata.nextLink

Answer: B
Explanation:
The odata.deltaLink header is used to retrieve changes from a table in Dataverse. It is a more efficient way to retrieve changes than using the odata.nextLink header.
To configure the odata.deltaLink header, you need to include the following in the request header:
odata.deltaLink=https://{server}/{organization}/api/data/v9.0/Accounts?$filter=Id eq guid'{AccountId}’

QUESTION 237
You are creating a Power Apps Component Framework (PCF) component.
You add the following markup to the component manifest. (Line numbers are included for reference only.)

You need to complete the component manifest.
Which XML markup segment should you insert at line 03?

A. <control DisplayNameKey=”PowerContoso” constructor=”CtlProducts” version=”0.0.10″ display-name-key=”CtlProducts” description-key=”CtlProducts” control-type=”standard”>
B. <control namespace=”PowerContoso” constructor=”CtlProducts” version=”0.0.10″ display-name-key=”CtlProducts” description-key=”CtlProducts” control- type=”standard”>
C. <control code=”PowerContoso” constructor=”CtlProducts” version=”0.0.10″ display-name-key=”CtlProducts” description-key=”CtlProducts” control- type=”standard”>
D. <control name=”PowerContoso” constructor=”CtlProducts” version=”0.0.10″ display-name-key=”CtlProducts” description-key=”CtlProducts” control- type=”standard”>
E. <control _value=”PowerContoso” constructor=”CtlProducts” version=”0.0.10″ display-name-key=”CtlProducts” description-key=”CtlProducts” control- type=”standard”>

Answer: B
Explanation:
The control element defines the component’s namespace, version and display information.
Example:
< ?xml version=”1.0″ encoding=”utf-8″ ?>
< manifest>
< control namespace=”MyNameSpace” constructor=”JSHelloWorldControl” version=”1.0.0″ display-name-key=”JS_HelloWorldControl_Display_Key” description- key=”JS_HelloWorldControl_Desc_Key” control-type=”standard”>
< property name=”myFirstProperty” display-name-key=”myFirstProperty_Display_Key” description-key=”myFirstProperty_Desc_Key” of-type=”SingleLine.Text” usage=”bound” required=”true” />
< resources>
< code path=”JS_HelloWorldControl.js” order=”1″ />
< css path=”css/JS_HelloWorldControl.css” order=”1″ />
< /resources>
< /control>
< /manifest>
Reference:
https://docs.microsoft.com/en-us/power-apps/developer/component-framework/manifest-schema-reference/manifest

QUESTION 238
Drag and Drop Question
You are designing new functionality for an existing model-driven app.
A field must display multiple selections to the user, enabling the user to select a value.
You need to determine which column type can support the required scenarios.
Which column type should you use? To answer, drag the appropriate column types to the correct scenarios. Each column type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

Answer:

Explanation:
Box 1: 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. Besides the normal formula operators, you can use the in and exactin operators for substring matches.
[!INCLUDE [record-scope]../../includes/record-scope.md)]
Example:
Filter(IceCream, OnOrder > 0) – Returns records where OnOrder is greater than zero.
Box 2: Global choice
Lookup wouldn’t be deployed with a solution because you also need to transfer data.
Box 3: Global choice and Lookup
You can reuse Global choice; and lookup same records multiple times.
Reference:
https://docs.microsoft.com/en-us/power-platform/power-fx/reference/function-filter-lookup
https://thepoweraddict.com/how-to-work-with-choice-columns-in-dataverse/

QUESTION 239
You create a plug-in to validate data.
Users report that validation is not working as expected.
You need to debug the plug-in.
Which tool should you use?

A. Plug-in profiler
B. Power Platform Tools for Visual Studio
C. Plug-in dashboard
D. Plug-in Registration Tool

Answer: A
Explanation:
Because the plug-in executes on a remote server, you cannot attach a debugger to the plug-in 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.
Install plug-in profiler
There are two tools available from which to run the Plug-in Profiler: the Plug-in Registration Tool and Power Platform Tools for Visual Studio.
Start profiling
Follow these steps to begin profiling a plug-in’s execution.
1. In the Plug-in Registration tool, select the (Step) BasicPlugin.FollowupPlugin: Create of account step you registered earlier, and click Start Profiling.
2. When presented with the Profiler Settings dialog, accept the default settings and click OK to close the dialog.
Reference:
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/tutorial-debug-plug-in

QUESTION 240
Drag and Drop Question
You are creating a Web API.
The API must be able to perform the following actions:
– Create a column in a Microsoft Dataverse table.
– Update a column for an existing row.
Which HTTP methods should you use? To answer, drag the appropriate HTTP methods to the correct requirements. Each HTTP method may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

Answer:

Explanation:
Box 1: POST
Create table definitions
To create a table definition, POST the JSON representation of the entity definition data to the EntityDefinitions entity set path. The entity must include the definition for the primary name attribute. You don’t need to set values for all the properties. The items on this list except for Description are required, although setting a description is a recommended best practice.
Box 2: PATCH
Basic update
Update operations use the HTTP PATCH verb. Pass a JSON object containing the properties you want to update to the URI that represents the record.
Reference:
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/webapi/create-update-entity-definitions-using-web-api
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/webapi/update-delete-entities-using-web-api

QUESTION 241
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than once correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You are designing a one-way integration from the Microsoft Dataverse to another system.
You must use an Azure Function to update the other system. The integration must send only newly created records to the other system. The solution must support scenarios where a component of the integration is unavailable for more than a few seconds to avoid data loss.
You need to design the integration solution.
Solution: Register a service endpoint in the Dataverse instance that connects to an Azure Service Bus queue.
Create and register an Azure-aware plug-in that uses the service endpoint.
Register a step on the plug-in that runs asynchronously on the record’s Create message and in the post-operation stage.
Configure the Azure Function to process records as they are added to the queue.
Does the solution meet the goal?

A. Yes
B. No

Answer: A
Explanation:
Plug-ins are one of two methods used to initiate posting the message containing the data context to the Azure Service Bus, the other method being a custom workflow activity.
Note: Microsoft Dataverse supports integration with Azure.
For the Dataverse and Azure connection to work, there must be at least one solution in an Azure Service Bus solution account, where the solution contains one or more service endpoints.
For a queue endpoint contract, a listener doesn’t have to be actively listening.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/azure-integration

QUESTION 242
Hotspot Question
You need to package and deploy a Power Apps code component to an environment.
Which commands should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Answer:

Explanation:
Box 1: pac solution init –publisher-name
Create a new solutions project using the following command. The solution project is used for bundling the code component into a solution zip file that is used for importing into Dataverse. pac solution init –publisher-name developer –publisher-prefix de
Box 2: pac auth create
Connecting to your environment.
Auth commands are used to authenticate to Dataverse.
Creates the authentication profile for your organization by passing the url parameter. Shows AAD dialog if sign in credentials are not specified.
Example: pac auth create –url https://Myorg.crm.dynamics.com
Box 3: pac pcf push –publisher-prefix
Deploying code components
After you have successfully created an authentication profile, you can start pushing the code components to the Dataverse instance with all the latest changes.
The push capability speeds up the inner-developer cycle development because it bypasses the code component versioning requirements and does not require that you build your solution (cdsproj) to import the code component.
To use the push capability, do the following:
1. Ensure that you have a valid authentication profile created.
2. Navigate to the directory where the sample component file is located.
3. Run the command.
pac pcf push –publisher-prefix <your publisher prefix>
Incorrect:
Commands for working with Dataverse solution projects include:
Parameter init
Initializes the solution project. It has the following parameters: publisher-name: Publisher name of the organization. publisher-prefix: Publisher prefix of the organization.
Reference:
https://docs.microsoft.com/en-us/power-apps/developer/component-framework/import-custom-controls

QUESTION 243
Drag and Drop Question
You need to develop a Power Apps Component Framework (PCF) component for a company.
You must follow Microsoft’s application lifecycle management (ALM) process for code components.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Answer:

Explanation:
Development and debugging ALM considerations
When developing code components, you would follow the steps below:
1. Create code component project (pcfproj) from a template using pac pcf init.
2. Implement code component logic.
3. Debug the code component using the local test harness.
4. Create a solution project (cdsproj) and add the code component project as a reference.
5. Build the code component in release mode for distribution and deployment.
Reference:
https://docs.microsoft.com/en-us/power-apps/developer/component-framework/code-components-alm#building-pcfproj-code-component-projects

QUESTION 244
Drag and Drop Question
You create a new canvas app.
You update a test case and must test the app in a separate browser.
You need to test the app by using Test Studio.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Answer:

Explanation:
Step 1: Select a test suite
Step 3: Publish the test
Step 3: Select Copy play link
Playing tests in a browser
You can copy a link to play a test in separate browser outside Test Studio. It helps integrate your tests in a continuous build and release pipeline such as Azure DevOps.
The play link for the selected test is persisted. It doesn’t change for the test suite or test case. You can update your tests without the need to modify build and release processes.
To play tests in your browser:
1. Select a test suite or test case in the right pane.
2. Select Copy play link.
3. You’re prompted to publish your tests if there are any unpublished changes.
4. You can select to skip the publish process and copy the play link. New test changes don’t play if you skip.
5. Open a browser and paste the URL into the address bar to play the test.
6. View your test playing back.
Step 4: Open a browser and paste the URL for the app inte the address bar
Reference:
https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/working-with-test-studio

QUESTION 245
Hotspot Question
You create a Power Apps component framework component.
You need to test the component.
Which option should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Answer:

Explanation:
Box 1: F12 and select component
Using browser developer tools to debug your code component
Modern browsers have a built-in set of developer tools that allow you to inspect the HTML, CSS, and JavaScript loaded on the current page. You can access these developer tools using the keyboard shortcut Ctrl+Shift+I. Using the F12 key is also a common keyboard shortcut to open the developer tools.
Box 2: Data Inputs
Data Inputs is an interactive UI that displays all the properties and their types or type-groups defined in the manifest file. The contents of this area are dependent on the properties and datasets defined in the ControlManifest.Input.xml and allows providing mock data for test purposes.
Box 3: Context Inputs
Context Inputs is shown for all code component types:
* Form Factor: Provides a way to specify the form factor and test the code component with each form factor (web, tablet, phone). This is helpful when the code component changes its layout depending on where the component is loaded. You can detect the form factor in the code using context.client.getFormFactor().
* etc.
Reference:
https://docs.microsoft.com/en-us/power-apps/developer/component-framework/debugging-custom-controls

QUESTION 246
You are implementing business logic for a model-driven app form by using multiple JavaScript web resources.
The business logic, number of JavaScript files, and the columns that the business logic requires are expected to change frequently. Some form fields will not be visible. Occasionally, non-developers will also make changes to the form.
You need to prevent columns referenced by the JavaScript from accidentally being removed from the form based.
What should you do?

A. Hide columns that should not be displayed.
B. Set all columns as business required.
C. Add all columns as non-event dependencies to the form.
D. Add columns in each JavaScript file as a dependency.

Answer: D
Explanation:
Column dependencies
Starting with model-driven apps, if your JavaScript web resource depends on a table column value that you don’t want to display in the form, you can set the column as a dependency for the JavaScript web resource. This means that the column will be available within the client API columns collection so you can get or set the value in your code. When you add a dependency this way, the controls collection of the column will be empty because there will be no control on the form.
Before this feature you would need to manually add the column to the form and then configure the control to be hidden. Now you can establish this dependency more directly and eliminate the possibility that someone will remove the hidden column from the form.
Reference:
https://docs.microsoft.com/en-us/power-apps/maker/model-driven-apps/visibility-options-legacy

QUESTION 247
You are creating a model-driven app for Contoso, Ltd. You add a button to the account page. The button must send a text message to the company’s account team when a user selects the button.
The account team reports that they are not receiving messages when users select the button. You are troubleshooting the app by using the following hyperlink: https://contoso.com.dynamics.com/main.aspx?appid=3b157789-5e5b-ec11-8f8f-002248087922&ribbondebug=true
What is the purpose of the hyperlink?

A. Run Command Checker for all buttons on the page.
B. Add the Power Apps Checker button to the page.
C. Run Power Apps Checker for all buttons on the page.
D. Add the Command Checker button to the page.

Answer: D
Explanation:
To enable Command Checker, pass ribbondebug=true as a URL parameter (ex: https://myorg.crm.dynamics.com/main.aspx?appid=c26d1c44-e7c0-4c72-9d6d-
0e82768cb5bd&ribbondebug=true). You’ll see two new UI features light up. The first is a new button in the top right of the header which lets you inspect the global command bar

Next, each command bar contains a new “Command checker” button. Note that this shows up at the end of the ribbon, so you may have to click the overflow flyout.

Reference:
https://powerapps.microsoft.com/en-us/blog/introducing-command-checker-for-model-app-ribbons/

QUESTION 248
You are developing a Power Platform app.
The app must implement a two-way listener to an on-premises system by using Microsoft Azure Service Bus. You create an Azure Service Bus namespace and messaging entity. You must add the shared access policies.
You need to select the permissions for the messaging entity.
Which two permissions should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.

A. System customizer
B. Listen
C. Read
D. Send
E. Manage

Answer: BD
Explanation:
The messaging entity must have the Send policy permission at a minimum. For a two-way relay, the policy must also have the Listen permission.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/walkthrough-configure-azure-sas-integration

QUESTION 249
Drag and Drop Question
You are creating a model-driven app for a company. Sales team members will use the app to manage leads. The app will interact with the Microsoft Dataverse Leads table.
You must configure the app to meet the following requirements:
1. If the estimated value for a lead is greater than $10,000 the app must:
– Send an email to a manager.
– Display a field named Sponsor on the lead form.
2. If the estimated value for a lead is greater than $100,000 the app must:
– Send an email to the company’s vice president.
– Display the following message as a notification while the lead record is open: High value customer, handle with care.
You need to configure the app. The solution must minimize the use of code.
Which options should you use? To answer, drag the appropriate options to the correct requirements. Each option may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

Answer:

Explanation:
Box 1: Power Automate flow
Here are the top how-to scenarios for email in Microsoft Power Automate, with examples of how to achieve them.
1. Send a beautifully formatted email.
2. Add an image to your email.
3. Send email to a distribution list.
4. Send automatic replies from a shared mailbox.
5. Change the date and time format of an email.
Box 2: Business rule
Business Rules in PowerApps
Set values of a field.
Clear values of a field.
Set field requirement levels.
Show or hide fields.
Enable or disable fields.
Validate data and show error messages.
Create business recommendations based on business intelligence.
Box 3: Onload script
Display the following message as a notification while the lead record is open: High value customer, handle with care.
Reference:
https://docs.microsoft.com/en-us/power-automate/email-customization
https://imperiumdynamics.com/blog/business-rules-in-powerapps.html

QUESTION 250
Hotspot Question
Contoso, Ltd. has a database that stores proprietary stock market information that the company has accumulated over many years.
You create a RESTful service for the company that exposes specific information about stocks. You must make the service available to the company’s brokers. The service must be certified by Microsoft.
You need to create a custom connector for the service APIs.
How should you configure the connector? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Answer:

Explanation:
Box 1:Contoso, Ltd.
publisher and stackOwner properties
“publisher” is the name of your company or organization. Provide the full company name (for example, “Contoso Corporation”). This must be in alphanumeric format.
“stackOwner” is the owning company or organization of the back-end service stack that the connector is connecting to. This must be in alphanumeric format
Box 2: apiProperties.json
The publisher and stackOwner properties exist as top-level properties within the apiProperties.json file.
Reference:
https://docs.microsoft.com/en-us/connectors/custom-connectors/certification-submission

QUESTION 251
You are troubleshooting a new canvas app.
Users report the app loads slowly. You use the Monitor tool to view various events being performed in the app. Events performed in the app do not have formula details.
You need to enable formulas to be included with the Monitor tool events.
What should you do?

A. Add the Microsoft Azure Application Insights data source to the canvas app
B. After each event, implement the trace function within the canvas app
C. Turn on the Debug published app setting in the canvas app
D. Validate the Application Insights instrumentation key has been populated in the app object’s properties within the canvas app

Answer: C
Explanation:
Setting: Debug published app
If you want to view the source expressions in Monitor for the published app, you need to turn on the setting to publish the expressions with the app. This setting is similar to generating a debug file in traditional development. Publishing source expressions with your app is optional. Even when this setting is off, you’ll be able to see the events happening in your app, but you won’t be able to map these events to specific expressions or formulas.
To enable this setting, go to File > Settings, and then turn on Debug published app.
Reference:
https://docs.microsoft.com/en-us/power-apps/maker/monitor-canvasapps

QUESTION 252
Drag and Drop Question
You have several model-driven apps.
You must ensure that app creators and system administrators can customize the apps.
You must follow the principle of least privilege.
You need to assign the permissions that are needed for app creators and system administrators.
Which security roles should you assign? To answer, drag the appropriate roles to the correct requirements. Each role may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point

Answer:

Explanation:
Box 1: System Customizer
System Customizer – Create (self), Read (self), Write (self), Delete (self), Customizations
Has full permission to customize the environment. However, can only view records for environment tables that they create.
Box 2: System Administrator only
System Administrator
Create, Read, Write, Delete, Customizations, Security Roles
Has full permission to customize or administer the environment, including creating, modifying, and assigning security roles. Can view all data in the environment.
Box 3: System Administrator only
Reference:
https://docs.microsoft.com/en-us/power-apps/maker/model-driven-apps/share-model-driven-app

QUESTION 253
Drag and Drop Question
You are creating a plug-in for a Power Apps app for the human resources department at the company. The app will be used to process new employees and help employees apply for an identification card.
You have the following requirements:
– Applications must not be marked as complete if the employee has not completed mandatory drug screening.
– Add logic that stores the name of the human resources team member that approves an application. This step must be completed before an ID card is created for the applicant.
– Successful validation and ID card printing.
You need to configure the event pipeline.
Which should you do? To answer, drag the appropriate roles to the correct requirements. Each role may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point

Answer:

Explanation:
Box 1: PreValidation
Applications must not be marked as complete if the employee has not completed mandatory drug screening.
If you want to change any values for an entity included in the message, you should do it here.
Pre-validation stage executes outside Database Transaction which will not rollback the entire operations written in the plugin if there is any runtime error occurs in one operation. This provides an opportunity to include logic to cancel the operation before the database transaction.
Box 2: PreOperation
Add logic that stores the name of the human resources team member that approves an application. This step must be completed before an ID card is created for the applicant.
Pre-Operation stage executes inside database transaction due to which any runtime error occurs in a single operation in the plugin will rollback entire operations which are part of the plugin.
Box 3: PostOperation
Successful validation and ID card printing.
Post Operation – Plug-ins registered in this stage are executed within the database transaction. Plugin will run after the values have been inserted/changed on the database
Reference:
https://softchief.com/2021/03/23/prevalidation-v-s-preopration-in-dynamics-365/
http://mscrmtechie.blogspot.com/2016/02/plugin-stages-pre-validation-pre.html

QUESTION 254
Drag and Drop Question
You are developing a Power Platform solution. You are modifying a business process flow.
You have created a new radial knob for the Total amount value and have added the radial knob to the form.
The Total amount value must be entered at initiation before moving to the next step.
You need to configure the business process flow.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Answer:

Explanation:
https://powerusers.microsoft.com/t5/Power-Automate-Community-Blog/Preview-Custom-Controls-in-Business-Process-Flows/ba-p/263237

QUESTION 255
Case Study 5 – Northwind Electric Cars
Background
Northwind Electric Cars’ ride sharing service is growing rapidly. The company is expanding to offer ride sharing in new cities. The company reports that their ability to perform background checks for potential employees is outpacing the capacity of the human resources (HR) department. The current background check process requires significant manual work.
Current Environment
The HR department uses a model-driven app to manage candidate information. Regional managers report that it is difficult to determine where a candidate is in the background check process without having to contact HR.
The IT department performs all system customizations.
Verification process

Service providers
Each of the third-party services has an API available. Northwind wants to automate the verification process by calling the APIs from a Microsoft Power Platform solution.
Each of the third-party services charge per result. Northwind wants to perform the background check processes only when necessary to minimize costs.
Cross-origin resource sharing (CORS) is disabled for all three APIs.

Requirements. General
This project is a top priority for the Northwind. The company has provided time for developers to write code as needed to support the project. Use of Microsoft Azure resources is approved for use if necessary.
Requirements. Address verification
The system must perform address validation any time an address is added or updated in the model-driven app user interface.
Validation must not be performed unless an address is changed.
Users must initiate address validation by selecting a button on the command bar.
The API must return a version of the address in a uniform format. The returned address must replace the address entered by the user.
The API must return an error if the address entered cannot be validated. If the API returns an error, the user must contact the candidate to resolve the issue.
The user must re-enter the address information to trigger validation.
Requirements. Driving record verification
Driving record verification must only be performed once for each candidate.
Information required for driving record verification must be sent to the driving record verification service automatically after the candidate’s address is verified.
The API must return a value of either Approved or Rejected to indicate whether the candidate has met the company’s requirements.
Requirements. Background check verification
Background check verification must be performed only once for each candidate.
The candidate’s information must be sent to the background check service automatically if the candidate’s driving record check is approved.
The API must return a submission identification number to the caller. The identification number can be used to return the latest stage information from the service.
The API also returns one of ten possible values. The value returned identifies the current stage of the verification process. The returned value may signify whether the candidate is automatically rejected, automatically passed, or calls for further manual investigation.
The content and number of stage values is subject to change. The HR department must be able to update the stage values.
In cases where further investigation is required, users must manually update the value to reflect the final result.
Regional managers must be able to use the model-driven app to identify the current stage of each of the verification processes for any candidate. The solution must include fields for the candidate’s record to represent each stage.
The solution must connect to the service and update the background check stage for candidates at least once per hour for incomplete background checks.
Requirements. Environments

Issues. Address verification
Users report that the address verification API returns the following error message: The Same Origin Policy disallows reading the remote resource.
Issues. Background check verification
While reviewing API information for the background check verification process you observe that the API uses an IP address and not a fully-qualified domain name.
Code
AddressVerificationAPI.js
You create a custom action to communicate with the address verification API by using the following code. (Line numbers are included for reference only.)

Question
You need to connect to the background check API.
Which mechanism should you use?

A. JavaScript
B. Flow with a custom connector
C. Azure Function
D. Plug-in

Answer: B
Explanation:
While Azure Logic Apps, Microsoft Power Automate, and Microsoft Power Apps offer over 325+ connectors to connect to Microsoft and verified services, you may want to communicate with services that aren’t available as prebuilt connectors. Custom connectors address this scenario by allowing you to create (and even share) a connector with its own triggers and actions.
Note:
Each of the third-party services charge per result. Northwind wants to perform the background check processes only when necessary to minimize costs.

Reference:
https://docs.microsoft.com/en-us/connectors/custom-connectors/

QUESTION 256
Case Study 5 – Northwind Electric Cars
Background
Northwind Electric Cars’ ride sharing service is growing rapidly. The company is expanding to offer ride sharing in new cities. The company reports that their ability to perform background checks for potential employees is outpacing the capacity of the human resources (HR) department. The current background check process requires significant manual work.
Current Environment
The HR department uses a model-driven app to manage candidate information. Regional managers report that it is difficult to determine where a candidate is in the background check process without having to contact HR.
The IT department performs all system customizations.
Verification process

Service providers
Each of the third-party services has an API available. Northwind wants to automate the verification process by calling the APIs from a Microsoft Power Platform solution.
Each of the third-party services charge per result. Northwind wants to perform the background check processes only when necessary to minimize costs.
Cross-origin resource sharing (CORS) is disabled for all three APIs.

Requirements. General
This project is a top priority for the Northwind. The company has provided time for developers to write code as needed to support the project. Use of Microsoft Azure resources is approved for use if necessary.
Requirements. Address verification
The system must perform address validation any time an address is added or updated in the model-driven app user interface.
Validation must not be performed unless an address is changed.
Users must initiate address validation by selecting a button on the command bar.
The API must return a version of the address in a uniform format. The returned address must replace the address entered by the user.
The API must return an error if the address entered cannot be validated. If the API returns an error, the user must contact the candidate to resolve the issue.
The user must re-enter the address information to trigger validation.
Requirements. Driving record verification
Driving record verification must only be performed once for each candidate.
Information required for driving record verification must be sent to the driving record verification service automatically after the candidate’s address is verified.
The API must return a value of either Approved or Rejected to indicate whether the candidate has met the company’s requirements.
Requirements. Background check verification
Background check verification must be performed only once for each candidate.
The candidate’s information must be sent to the background check service automatically if the candidate’s driving record check is approved.
The API must return a submission identification number to the caller. The identification number can be used to return the latest stage information from the service.
The API also returns one of ten possible values. The value returned identifies the current stage of the verification process. The returned value may signify whether the candidate is automatically rejected, automatically passed, or calls for further manual investigation.
The content and number of stage values is subject to change. The HR department must be able to update the stage values.
In cases where further investigation is required, users must manually update the value to reflect the final result.
Regional managers must be able to use the model-driven app to identify the current stage of each of the verification processes for any candidate. The solution must include fields for the candidate’s record to represent each stage.
The solution must connect to the service and update the background check stage for candidates at least once per hour for incomplete background checks.
Requirements. Environments

Issues. Address verification
Users report that the address verification API returns the following error message: The Same Origin Policy disallows reading the remote resource.
Issues. Background check verification
While reviewing API information for the background check verification process you observe that the API uses an IP address and not a fully-qualified domain name.
Code
AddressVerificationAPI.js
You create a custom action to communicate with the address verification API by using the following code. (Line numbers are included for reference only.)

Question
You need to configure the app to meet the address verification requirements.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.

A. Make the address fields read-only after they have been verified.
B. Open a confirmation dialog when the command bar button is selected.
C. Enable the command bar button only when the address shows as not verified.
D. Clear the field indicating the address is valid when an address field changes.

Answer: CD
Explanation:
Address requirement:
> The system must perform address validation any time an address is added or updated in the model-driven app user interface.
> Validation must not be performed unless an address is changed.
> Users must initiate address validation by selecting a button on the command bar.
> The user must re-enter the address information to trigger validation.
From those, we can get 2 points:
1.) Address can be changed after it’s verified.
2.) Ability to run validation can be disabled if there are no changes to the address.

QUESTION 257
Case Study 5 – Northwind Electric Cars
Background
Northwind Electric Cars’ ride sharing service is growing rapidly. The company is expanding to offer ride sharing in new cities. The company reports that their ability to perform background checks for potential employees is outpacing the capacity of the human resources (HR) department. The current background check process requires significant manual work.
Current Environment
The HR department uses a model-driven app to manage candidate information. Regional managers report that it is difficult to determine where a candidate is in the background check process without having to contact HR.
The IT department performs all system customizations.
Verification process

Service providers
Each of the third-party services has an API available. Northwind wants to automate the verification process by calling the APIs from a Microsoft Power Platform solution.
Each of the third-party services charge per result. Northwind wants to perform the background check processes only when necessary to minimize costs.
Cross-origin resource sharing (CORS) is disabled for all three APIs.

Requirements. General
This project is a top priority for the Northwind. The company has provided time for developers to write code as needed to support the project. Use of Microsoft Azure resources is approved for use if necessary.
Requirements. Address verification
The system must perform address validation any time an address is added or updated in the model-driven app user interface.
Validation must not be performed unless an address is changed.
Users must initiate address validation by selecting a button on the command bar.
The API must return a version of the address in a uniform format. The returned address must replace the address entered by the user.
The API must return an error if the address entered cannot be validated. If the API returns an error, the user must contact the candidate to resolve the issue.
The user must re-enter the address information to trigger validation.
Requirements. Driving record verification
Driving record verification must only be performed once for each candidate.
Information required for driving record verification must be sent to the driving record verification service automatically after the candidate’s address is verified.
The API must return a value of either Approved or Rejected to indicate whether the candidate has met the company’s requirements.
Requirements. Background check verification
Background check verification must be performed only once for each candidate.
The candidate’s information must be sent to the background check service automatically if the candidate’s driving record check is approved.
The API must return a submission identification number to the caller. The identification number can be used to return the latest stage information from the service.
The API also returns one of ten possible values. The value returned identifies the current stage of the verification process. The returned value may signify whether the candidate is automatically rejected, automatically passed, or calls for further manual investigation.
The content and number of stage values is subject to change. The HR department must be able to update the stage values.
In cases where further investigation is required, users must manually update the value to reflect the final result.
Regional managers must be able to use the model-driven app to identify the current stage of each of the verification processes for any candidate. The solution must include fields for the candidate’s record to represent each stage.
The solution must connect to the service and update the background check stage for candidates at least once per hour for incomplete background checks.
Requirements. Environments

Issues. Address verification
Users report that the address verification API returns the following error message: The Same Origin Policy disallows reading the remote resource.
Issues. Background check verification
While reviewing API information for the background check verification process you observe that the API uses an IP address and not a fully-qualified domain name.
Code
AddressVerificationAPI.js
You create a custom action to communicate with the address verification API by using the following code. (Line numbers are included for reference only.)

Question
You need to configure the solution to meet the requirements for driving record verifications.
What are two possible ways to achieve the goal? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.

A. Create an Azure Logic Apps connector.
B. Use a connector provided by the driving record verification service.
C. Share a custom connector for the driving record verification service with a member of the talent department.
D. Share the flow with a member of the talent department.

Answer: AC
Explanation:
The reason for A is the driving record verification service only provides OpenAPI definition, not the custom connector itself. We still have to create a custom connector by importing the OpenAPI definition into the custom connector.
The reason for C is because the HR department is the one responsible to renew the password once it’s expired. HR department need to have access to the connector so they can update the password in the security section.

QUESTION 258
Case Study 5 – Northwind Electric Cars
Background
Northwind Electric Cars’ ride sharing service is growing rapidly. The company is expanding to offer ride sharing in new cities. The company reports that their ability to perform background checks for potential employees is outpacing the capacity of the human resources (HR) department. The current background check process requires significant manual work.
Current Environment
The HR department uses a model-driven app to manage candidate information. Regional managers report that it is difficult to determine where a candidate is in the background check process without having to contact HR.
The IT department performs all system customizations.
Verification process

Service providers
Each of the third-party services has an API available. Northwind wants to automate the verification process by calling the APIs from a Microsoft Power Platform solution.
Each of the third-party services charge per result. Northwind wants to perform the background check processes only when necessary to minimize costs.
Cross-origin resource sharing (CORS) is disabled for all three APIs.

Requirements. General
This project is a top priority for the Northwind. The company has provided time for developers to write code as needed to support the project. Use of Microsoft Azure resources is approved for use if necessary.
Requirements. Address verification
The system must perform address validation any time an address is added or updated in the model-driven app user interface.
Validation must not be performed unless an address is changed.
Users must initiate address validation by selecting a button on the command bar.
The API must return a version of the address in a uniform format. The returned address must replace the address entered by the user.
The API must return an error if the address entered cannot be validated. If the API returns an error, the user must contact the candidate to resolve the issue.
The user must re-enter the address information to trigger validation.
Requirements. Driving record verification
Driving record verification must only be performed once for each candidate.
Information required for driving record verification must be sent to the driving record verification service automatically after the candidate’s address is verified.
The API must return a value of either Approved or Rejected to indicate whether the candidate has met the company’s requirements.
Requirements. Background check verification
Background check verification must be performed only once for each candidate.
The candidate’s information must be sent to the background check service automatically if the candidate’s driving record check is approved.
The API must return a submission identification number to the caller. The identification number can be used to return the latest stage information from the service.
The API also returns one of ten possible values. The value returned identifies the current stage of the verification process. The returned value may signify whether the candidate is automatically rejected, automatically passed, or calls for further manual investigation.
The content and number of stage values is subject to change. The HR department must be able to update the stage values.
In cases where further investigation is required, users must manually update the value to reflect the final result.
Regional managers must be able to use the model-driven app to identify the current stage of each of the verification processes for any candidate. The solution must include fields for the candidate’s record to represent each stage.
The solution must connect to the service and update the background check stage for candidates at least once per hour for incomplete background checks.
Requirements. Environments

Issues. Address verification
Users report that the address verification API returns the following error message: The Same Origin Policy disallows reading the remote resource.
Issues. Background check verification
While reviewing API information for the background check verification process you observe that the API uses an IP address and not a fully-qualified domain name.
Code
AddressVerificationAPI.js
You create a custom action to communicate with the address verification API by using the following code. (Line numbers are included for reference only.)

Question
Hotspot Question
You need to implement the driving record check functionality.
What should you implement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Answer:

Explanation:
Box 1: After the address validation field is saved to Dataverse
Trigger should happen once address is saved to Dataverse. Once its on screen, address can be re-entered and invalidated.
Box 2: Cloud Flow
Driving record verification
The company has provided an OpenAPI document to describe its RESTFUL Api.
Use Custom APIs to create your own APIs in Dataverse. You can consolidate one or more operations into a Custom API that you and other developers can call in their code or from Power Automate. The Microsoft Dataverse connector enables calling actions in Power Automate.
Reference:
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/custom-api

QUESTION 259
Case Study 5 – Northwind Electric Cars
Background
Northwind Electric Cars’ ride sharing service is growing rapidly. The company is expanding to offer ride sharing in new cities. The company reports that their ability to perform background checks for potential employees is outpacing the capacity of the human resources (HR) department. The current background check process requires significant manual work.
Current Environment
The HR department uses a model-driven app to manage candidate information. Regional managers report that it is difficult to determine where a candidate is in the background check process without having to contact HR.
The IT department performs all system customizations.
Verification process

Service providers
Each of the third-party services has an API available. Northwind wants to automate the verification process by calling the APIs from a Microsoft Power Platform solution.
Each of the third-party services charge per result. Northwind wants to perform the background check processes only when necessary to minimize costs.
Cross-origin resource sharing (CORS) is disabled for all three APIs.

Requirements. General
This project is a top priority for the Northwind. The company has provided time for developers to write code as needed to support the project. Use of Microsoft Azure resources is approved for use if necessary.
Requirements. Address verification
The system must perform address validation any time an address is added or updated in the model-driven app user interface.
Validation must not be performed unless an address is changed.
Users must initiate address validation by selecting a button on the command bar.
The API must return a version of the address in a uniform format. The returned address must replace the address entered by the user.
The API must return an error if the address entered cannot be validated. If the API returns an error, the user must contact the candidate to resolve the issue.
The user must re-enter the address information to trigger validation.
Requirements. Driving record verification
Driving record verification must only be performed once for each candidate.
Information required for driving record verification must be sent to the driving record verification service automatically after the candidate’s address is verified.
The API must return a value of either Approved or Rejected to indicate whether the candidate has met the company’s requirements.
Requirements. Background check verification
Background check verification must be performed only once for each candidate.
The candidate’s information must be sent to the background check service automatically if the candidate’s driving record check is approved.
The API must return a submission identification number to the caller. The identification number can be used to return the latest stage information from the service.
The API also returns one of ten possible values. The value returned identifies the current stage of the verification process. The returned value may signify whether the candidate is automatically rejected, automatically passed, or calls for further manual investigation.
The content and number of stage values is subject to change. The HR department must be able to update the stage values.
In cases where further investigation is required, users must manually update the value to reflect the final result.
Regional managers must be able to use the model-driven app to identify the current stage of each of the verification processes for any candidate. The solution must include fields for the candidate’s record to represent each stage.
The solution must connect to the service and update the background check stage for candidates at least once per hour for incomplete background checks.
Requirements. Environments

Issues. Address verification
Users report that the address verification API returns the following error message: The Same Origin Policy disallows reading the remote resource.
Issues. Background check verification
While reviewing API information for the background check verification process you observe that the API uses an IP address and not a fully-qualified domain name.
Code
AddressVerificationAPI.js
You create a custom action to communicate with the address verification API by using the following code. (Line numbers are included for reference only.)

Question
Hotspot Question
You need to configure the environments.
What should you do? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Answer:

Explanation:
Box 1: Install the plug-in profiler solution in the environment
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/tutorial-debug-plug-in
Box 2: Enable trace log in the environment
Production: You must be able to view tracing service logs.

QUESTION 260
Case Study 5 – Northwind Electric Cars
Background
Northwind Electric Cars’ ride sharing service is growing rapidly. The company is expanding to offer ride sharing in new cities. The company reports that their ability to perform background checks for potential employees is outpacing the capacity of the human resources (HR) department. The current background check process requires significant manual work.
Current Environment
The HR department uses a model-driven app to manage candidate information. Regional managers report that it is difficult to determine where a candidate is in the background check process without having to contact HR.
The IT department performs all system customizations.
Verification process

Service providers
Each of the third-party services has an API available. Northwind wants to automate the verification process by calling the APIs from a Microsoft Power Platform solution.
Each of the third-party services charge per result. Northwind wants to perform the background check processes only when necessary to minimize costs.
Cross-origin resource sharing (CORS) is disabled for all three APIs.

Requirements. General
This project is a top priority for the Northwind. The company has provided time for developers to write code as needed to support the project. Use of Microsoft Azure resources is approved for use if necessary.
Requirements. Address verification
The system must perform address validation any time an address is added or updated in the model-driven app user interface.
Validation must not be performed unless an address is changed.
Users must initiate address validation by selecting a button on the command bar.
The API must return a version of the address in a uniform format. The returned address must replace the address entered by the user.
The API must return an error if the address entered cannot be validated. If the API returns an error, the user must contact the candidate to resolve the issue.
The user must re-enter the address information to trigger validation.
Requirements. Driving record verification
Driving record verification must only be performed once for each candidate.
Information required for driving record verification must be sent to the driving record verification service automatically after the candidate’s address is verified.
The API must return a value of either Approved or Rejected to indicate whether the candidate has met the company’s requirements.
Requirements. Background check verification
Background check verification must be performed only once for each candidate.
The candidate’s information must be sent to the background check service automatically if the candidate’s driving record check is approved.
The API must return a submission identification number to the caller. The identification number can be used to return the latest stage information from the service.
The API also returns one of ten possible values. The value returned identifies the current stage of the verification process. The returned value may signify whether the candidate is automatically rejected, automatically passed, or calls for further manual investigation.
The content and number of stage values is subject to change. The HR department must be able to update the stage values.
In cases where further investigation is required, users must manually update the value to reflect the final result.
Regional managers must be able to use the model-driven app to identify the current stage of each of the verification processes for any candidate. The solution must include fields for the candidate’s record to represent each stage.
The solution must connect to the service and update the background check stage for candidates at least once per hour for incomplete background checks.
Requirements. Environments

Issues. Address verification
Users report that the address verification API returns the following error message: The Same Origin Policy disallows reading the remote resource.
Issues. Background check verification
While reviewing API information for the background check verification process you observe that the API uses an IP address and not a fully-qualified domain name.
Code
AddressVerificationAPI.js
You create a custom action to communicate with the address verification API by using the following code. (Line numbers are included for reference only.)

Question
Hotspot Question
You need to configure the address verification API.
Which values should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Answer:

Explanation:
Box 1: northwind_ValidateAddress
> Users must initiate address validation by selecting a button on the command bar.
This means JS will trigger custom action, and its message has to be northwind_ValidateAddress.
Box 2: Synchronous
The address verification process provides a response almost immediately on screen.

Resources From:

1.2026 Latest Braindump2go PL-400 Exam Dumps (PDF & VCE) Free Share:
https://www.braindump2go.com/pl-400.html

2.2026 Latest Braindump2go PL-400 PDF and PL-400 VCE Dumps Free Share:
https://drive.google.com/drive/folders/1NSQzfMucvTbS9I3sXHEidLQmYRPXR1p4?usp=sharing

3.2026 Free Braindump2go PL-400 Exam Questions Download:
https://www.braindump2go.com/free-online-pdf/PL-400-VCE-Dumps(235-260).pdf

Free Resources from Braindump2go,We Devoted to Helping You 100% Pass All Exams!