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
Show Answer
Correct Answer: B, D
Explanation: For Azure Service Bus shared access policies used by a two-way listener integration, the app needs to receive messages (Listen) and send messages (Send). Read is not a Service Bus SAS permission, Manage is only required for administrative operations such as creating or deleting entities, and System customizer is unrelated.
Question 82
HOTSPOT
-
Case study
-
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
-
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
-
Northwind Traders uses Microsoft Dynamics 365 Sales to manage its sales process. To better understand its customers, Northwind Traders invests in a team of researchers who gather data from multiple sources. The company stores the data it collects in a Microsoft Azure SQL Database. The company plans to use the data to enrich account records and make the sales team more effective.
Current environment
-
Environment
-
• The company has three Microsoft Power Platform environments with Dynamics 365 Sales installed. The environments are named development, test, and production.
• Each environment has an application user that can be used for integrations.
• The company must use solutions to perform all customization and configuration deployment.
Data
-
• Researchers are responsible for creating account records.
• Researchers have permissions on the Account table to create records, read all records, and update records they own.
• A synchronous plug-in runs when an account record is created and could reassign the record to a different user.
• Users must access data as themselves to enforce security and audit changes.
• A column named new_dataid is added to the Account table. The column uniquely identifies which data it should receive.
• Researchers have researched only the top 20 percent of account records.
Web API
-
• The company creates an Azure Function to run a RESTful .NET Web API.
• Data can be retrieved by placing a GET request to the URL https://dataservice-[ENVIRONMENTNAME].azurewebsites.net/enrich/[DATAID].
• [ENVIRONMENTNAME] is the name of the Microsoft Power Platform environment that requests the data.
• [DATAID] is the new_dataid column in the Account table.
• The Web API response will return a 200 response plus data if the DataId is found. Otherwise, a 404 response is returned.
• Developers plan to create a custom connector from the Web API to make it accessible from Microsoft Power Platform.
Requirements
-
Custom connector
-
• The Web API definition used to create the custom connector must be generated based on a low-code technology.
• The URL used by the custom connector must incorporate the current environment name without hardcoding values.
• Errors generated by the custom connector must not cause downstream processes to fail.
• Text descriptions and field placeholder text that describe the use of the custom connector must appear for non-developers.
Process
-
• All account records must be updated with data from the Web API once automatically.
• Only account records that contain a DataId should be updated by the Web API.
• Researchers must create Power Automate flows to specify data analysis priority.
• The researchers require a process that repurposes a set of identical steps of parameterized Microsoft Dataverse queries from a Power Automate flow for use in other flows that have different parameters. The researchers want to avoid recreating the steps manually each time they create a flow to save time and avoid errors.
Issues
-
• A tester attempts to connect to the production instance of the Web API with a DataId that should return data. The tester receives an error stating that the remote name could not be resolved.
• A missing component causes an error to occur when importing the solution that contains the Power Automate flow to update account records in a test environment.
You need to configure a Dataverse trigger and action in a Power Automate flow so researchers can update account records with data from the Web API even if they do not have edit privileges on the record.
What should you configure for each trigger and action requirement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Change Type: Added
Update a row connection type: Service principal
Explanation: Trigger only on newly created account records because each record must be enriched automatically once. Use a service principal/application user connection for the Update a row action so the flow can update records even when the triggering researcher lacks edit permission, while the trigger can still run in the user's context.
Question 83
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.
A company develops a new custom connector for a Microsoft Entra ID-protected Azure Function that was created as a single tenant app.
The custom connector must be moved to a production environment. The connector must be visible and accessible only to users in the tenant.
You need to deploy the custom connector.
Solution: Publish the custom connector to AppSource.
Does the solution meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: B
Explanation: Publishing a custom connector to AppSource is intended for broad distribution, not for restricting visibility to a single Microsoft Entra tenant. To keep the connector visible and usable only within the organization's tenant, it should be deployed within the tenant's Power Platform environment rather than published to AppSource.
Question 84
You develop code that will perform an update to existing records in a table.
The update must occur based on the alternate key configured for the table.
You need to perform the update.
Which two requests should you use? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
A. UpdateRequest
B. UpsertRequest
C. CreateRequest
D. RetrieveRequest
Show Answer
Correct Answer: A, B
Explanation: To update records based on an alternate key in Microsoft Dataverse/Dynamics 365, both UpdateRequest and UpsertRequest support identifying the target row by an alternate key. UpdateRequest performs an update of an existing record, while UpsertRequest uses the alternate key to update if the record exists (or create it if it does not). CreateRequest only creates records, and RetrieveRequest only reads records.
Question 85
HOTSPOT -
You develop the following code as part of an OnSave event handler in a form.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Yes
No
No
Explanation: preventDefault() cancels the normal save. retrieveRecord() is asynchronous, so the if (isOnHold) check executes before the callback updates isOnHold, meaning the confirmation dialog is not displayed based on the retrieved value and the form will not save automatically when creditonhold is false because the original save was prevented.
Question 86
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 one 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.
A company requires custom validation when users save form records that use a synchronous plug-in.
If validation fails, a message that explains how to resolve the issue must be displayed on the form to the user.
You need to implement the custom validation.
Solution: Include the message in the output parameters of the plug-in.
Does the solution meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: B
Explanation: A synchronous Dataverse plug-in should signal validation failures by throwing an InvalidPluginExecutionException (typically in the PreValidation or PreOperation stage). The exception message is surfaced to the user in the model-driven app. Output parameters are for operation results (primarily post-operation) and are not the mechanism for displaying validation messages on the form.
Question 87
A company uses Microsoft Dataverse rollup fields to calculate insurance exposure and risk profiles for customers.
Users report that the system does not update values for the rollup fields when new insurance policies are written.
You need to recalculate the value of the rollup fields immediately after a policy is created.
What should you do?
A. Create new calculated fields on the customer entity for insurance exposure and risk. Create a formula to calculate the sum of values from policy records.
B. Change the frequency of the Calculate Rollup Field recurring job from every hour to every five minutes.
C. Create a plug-in that uses the update method for the rollup fields. Configure a step on the Create event for the policy entity for this plug-in.
D. Create a plug-in that uses the CalculateRollupFieldRequest method for the rollup field. Configure a step on the Create event for the policy entity for this plug-in.
Show Answer
Correct Answer: D
Explanation: Rollup fields are normally recalculated by asynchronous system jobs, so they are not updated immediately when related records are created. To force an immediate recalculation after a policy is created, register a plug-in on the Policy Create event and invoke CalculateRollupFieldRequest for the affected customer rollup fields. Simply updating the field will not trigger the rollup calculation, changing the recurring job frequency still does not guarantee immediate updates, and calculated fields cannot aggregate related records like rollup fields.
Sources:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/define-rollup-fields
https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/define-rollup-fields?view=op-9-1
Question 88
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.
A company develops a new custom connector for a Microsoft Entra ID-protected Azure Function that was created as a single tenant app.
The custom connector must be moved to a production environment. The connector must be visible and accessible only to users in the tenant.
You need to deploy the custom connector.
Solution: Use Postman to export the custom connector. Then use Postman to import the connector into the production environment.
Does the solution meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: B
Explanation: The solution does not meet the deployment goal. While custom connectors can be created from or exported as OpenAPI/Postman definitions, moving a custom connector to production in the Power Platform should be done through solutions (managed/unmanaged) as part of ALM. Using Postman exports/imports transfers the API definition, not the connector's deployment, configuration, and environment-specific metadata. Tenant-only visibility is achieved by keeping the connector within the tenant/environment rather than distributing it publicly.
Question 89
DRAG DROP
-
You manage a model-driven app.
The forms in the app do not work as expected. You must troubleshoot the form issues.
Code unrelated to an event must continue to run as you troubleshoot.
You need to disable form events to isolate the causes.
Which URL parameters should you use? To answer, move the appropriate URL parameters to the correct events. You may use each URL parameter once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Form OnLoad: DisableFormHandlers
Column OnChange: DisableFormHandlers
Explanation: The DisableFormHandlers URL parameter disables form event handlers including OnLoad, OnChange, OnSave, business rules, and TabStateChange, while allowing unrelated code to continue running.
Question 90
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.
A company develops a new custom connector for a Microsoft Entra ID-protected Azure Function that was created as a single tenant app.
The custom connector must be moved to a production environment. The connector must be visible and accessible only to users in the tenant.
You need to deploy the custom connector.
Solution: Add the custom connector to a managed solution, export the managed solution, and then import the managed solution into the production environment.
Does the solution meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: A
Explanation: Yes. The standard deployment approach for a custom connector is to include it in a solution, export the solution as a managed solution, and import it into the production environment. A managed solution is the appropriate format for production deployment. The wording 'add the custom connector to a managed solution' is imprecise because components are added to an unmanaged solution and then exported as managed, but the intended deployment process meets the stated goal. Tenant visibility is governed by the Microsoft Entra ID single-tenant app registration.
Sources:
https://www.certlibrary.com/exam/PL-400
$19
Get all 409 questions with detailed answers and explanations
Instant download HTML + PDF delivered the moment payment clears.
Secure Stripe checkout we never see or store your card details.
7-day refund if files are defective see our refund policy.